Loading
Not ready. The export questions are the ones to answer first — everything else is planning around data you have not confirmed you can get.
Weighted towards the things that block a migration rather than the things that make it tidy. A missing activity export is a different order of problem from a messy field list.
Eleven decisions that have to be made before a migration rather than during it: what to bring, what to leave, how to deduplicate, and what happens to the old system.
Most failed migrations are failed decisions rather than failed imports.
Work through it with whoever owns the data and whoever will use it. The disagreements are the point — they surface now rather than three weeks after go-live.
Pay particular attention to the custom fields question. Every field carried across is one somebody has to consider forever.
It will not migrate anything. It is a set of decisions, not a tool.
It also cannot tell you whether your data is worth keeping — that judgement needs somebody who knows the customers.
What to leave behind, and how long to run both systems in parallel. Importing everything is the most common mistake, and switching off the old system overnight is the second.
Deduplicate before importing. Doing it afterwards means merging records that already have new activity on them.
About a month, with the old one read-only.
Only if you actually analyse them.
No.
Half an hour on your own figures, and an honest answer about the parts Treepie does not improve.