4 ms·

This is solid advice. Particularly: Have a staging system where you can practice your migrations - ideally you should have a full migration into staging at some

This is solid advice. Particularly: Have a staging system where you can practice your migrations - ideally you should have a full migration into staging at some point and the users (whoever they are) look at the results and sign it off (or, more likely, they find 50 important fields they forgot to mention earlier - its only once people see tangible results of the migration that they really think about which bits are important). Lastly, avoid committing to a schedule if at all possible. Well thats just good advice for any situation, if only it were that simple

mooreds 3y ago
> Lastly, avoid committing to a schedule if at all possible. Well thats just good advice for any situation, if only it were that simple I wrote this over a decade ago. I agree it is almost impossible to not have a schedule. If I were to update it based on what I know today, I'd say: "break the migration up into pieces if at all possible, and build a schedule based on that. Always make it clear that a schedule is an estimate. Don't do a migration for a fixed price--there's too much uncertainty."