← Guides
Checks before a migration
The questions to answer before fixing the cut-over date for a new system.

Migrations rarely fail because of one isolated technical problem; more often because of a dependency nobody listed: a monthly report, an export to the accountant, a department habit.
Dependency inventory
List everything that reads from or writes to the system being replaced.
- Other connected systems
- Periodic reports and exports
- External users (advisors, customers, suppliers)
- Scheduled jobs and automations
Order and checkpoints
Decide what moves first (usually master data), what moves later (transactions) and what is checked at each step.

Rollback conditions
For each phase, write in advance which result sends you back to the previous system, who decides and by when. Deciding under pressure leads to pressing on when you should not.
Example
Sample plan phase
| Phase | Prerequisite | Exit criterion | Roll back if |
|---|---|---|---|
| 2 – Master data | Validated export of customers and items | Counts and 50 sample records identical | Differences > 0.5% or empty mandatory fields |
| 3 – Open orders | Phase 2 closed | Open orders with same total | Totals do not match by 12:00 |


