Services / 03
Service 03 · During the project
Migration planning
Prepare the replacement of a system: dependencies, cut-over order, rollback conditions.
Helps you decide in which order to move data and users, when to stop, and how to roll back if a step fails.


4deliverables
Typical situations
01
Your current ERP is no longer supported and must be replaced without stopping invoicing.
02
You need to merge two systems after an internal reorganisation.
03
The new system's vendor asks for a migration plan you do not have.
You
What you provide
- List of systems to replace and the chosen target system
- Data structures (record layouts, sample exports with dummy data)
- Periods of the year when downtime is not acceptable
- Contacts of the outgoing and incoming vendors
Us
What we do
- 1.Inventory of dependencies between systems, reports and processes
- 2.Definition of the cut-over sequence and checkpoints
- 3.Definition of rollback conditions for each phase
- 4.List of verification checks for migrated data
What you receive
- Dependency list with impact and owner
- Cut-over plan with sequence, prerequisites and time windows
- Rollback conditions and who triggers them
- Acceptance checks for migrated data
How the work is checked
- Every phase has a prerequisite, an exit criterion and a rollback condition
- Time windows are compatible with the critical periods you indicated
- Plan validated by the client and, where agreed, by the vendors
Not included
- Software development, configuration or go-live of the systems
- Hosting, ongoing operations or support with guaranteed response times
- Security certifications or compliance audits
- Actual execution of the migration or data transformation
Quote factors
Written quote on request, no list prices.
- Number of systems and data volumes
- Number of phases
- Time constraints
- Vendor involvement
Other services
Want a quote for this service?
The form pre-selects this service. Describe systems, goal and timing.



