Skip to content
← Guides

Checks before a migration

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

Inventory checklist beside an external drive and tags

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.

01

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
02

Order and checkpoints

Decide what moves first (usually master data), what moves later (transactions) and what is checked at each step.

Wall timeline with the cut-over point highlighted
03

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

Sample plan phase
PhasePrerequisiteExit criterionRoll back if
2 – Master dataValidated export of customers and itemsCounts and 50 sample records identicalDifferences > 0.5% or empty mandatory fields
3 – Open ordersPhase 2 closedOpen orders with same totalTotals do not match by 12:00

More guides

Want to apply this to your case?

The "Migration planning" service produces these documents tailored to your systems.

Request a quote