Migration is where most IT projects quietly go wrong. Data goes missing, someone works a full day in the old system after cutover, and a week later you discover March is incomplete.
None of that is inevitable. It happens when a migration is treated as an event instead of a rehearsed process. Here is the process we actually follow.
Step 1 — Inventory before anything moves
We list every company file, every user, every customisation, every printer, and every integration. The surprises always live here: a TDL customisation nobody documented, or a second company file on someone’s laptop.
Step 2 — A full dry run
We migrate a complete copy to the new environment while the old one keeps running untouched. Nothing is cut over. This rehearsal tells us exactly how long the real move takes and what breaks.
Step 3 — You verify the dry run
Your team logs into the rehearsal environment and checks the things only you would notice: opening balances, custom reports, the invoice format the client insists on. Sign-off happens here, before anything real changes.
Step 4 — The overnight cutover
The final sync runs after business hours. It only carries the delta — what changed since the dry run — so it is fast. Users log off from the old system at the end of day and log into the new one the next morning.
Step 5 — The old system stays alive
We do not decommission anything for at least two weeks. If something was missed, the source is still there, read-only, to compare against. This single habit prevents almost every migration horror story.
What we need from you
- An accurate list of who needs access, and at what level
- One person who can make decisions during cutover night
- Two hours of a senior person’s time to verify the dry run
That is genuinely it. Everything else is ours.
Planning a move? We will scope it and tell you honestly how long it takes — including whether it is worth doing at all right now.