Facing a system replacement?
In a conversation, our expert goes through the source systems, the schedule and the risks with you. We give you an exact quote after the assessment.
Data · Service
Data migration for ERP replacements and company mergers
How far can you trust the integrator to move the data on time and in good quality?
When systems are replaced or companies merge, we move the data: we plan the migration, carry out the cleansing, run trial migrations, reconcile the numbers and manage the cutover. Our job is to make sure the numbers in the old and the new system match after go-live, and that you are not the one called because of a wrong opening balance.
2-9 months, depending on the size of the project · a data team independent of the integrator · ISO 27001, ISO 9001 and ISO 14001
Does this sound familiar?
The ERP replacement has been announced, and the data lands on your desk
Migration usually gets on the agenda when the system replacement starts, for example when moving from SAP ECC to S/4HANA or from Baan to Infor LN. We hear the sentences below from IT and data leaders.
Before the last trial run
The migration slips before go-live
“I want to see where the data stands before go-live, not at the last trial run.”
CIO, large enterprise
After go-live
The opening data is wrong
“If the opening data is wrong, finance will come to me.”
CIO, large enterprise
Old errors, new system
The error comes to light too late
“I want to see the error when it occurs, not afterwards, from its consequences.”
Head of master data management, large enterprise
The group asks
There is no rollback plan
“I need to be able to present the method and the rollback plan to the group.”
CIO, large enterprise
Not sure yet whether this is what you need?
Our expert will tell you whether it fits your situation.
How it works
For us, migration is data work, not a one-off technical task
01
Assessment
We look at the source and target systems and draw up the migration plan.
02
Defining the rules
The data owner decides on the mapping and cleansing rules, and we record them.
03
Repeated trial migrations
Every trial run is followed by a reconciliation report, so you can see where the data stands well before go-live.
04
Cutover
We switch over according to a runbook, with the rollback plan already prepared.
05
Follow-up
After go-live we keep checking that the numbers match.
What you get
A method you can also present to the group
Every step is documented, including the rollback.
- 01Migration plan
- 02Mapping between the old and the new system
- 03Cleansing rules, so old errors are not carried over
- 04Trial migrations with reconciliation reports
- 05Cutover runbook
- 06Rollback plan
Before you decide
Worth knowing
Who it is for: IT directors, heads of data, and ERP and migration project managers. We work for banks, utilities and manufacturers, including on tendered projects.
What we need from you
Access to the source and target systems, and a data owner who can make decisions about the data.
Duration and pricing
2-9 months, depending on the size of the project. After the assessment we work for a fixed price or at an hourly rate.
What it builds on
Data cleansing, validation, ETL and master data management. The work is done by a data-specialised team that is independent of the integrator.
What it does not solve
We do not implement the target system, and we do not redesign the processes. We are responsible for the data; implementing the system is the integrator’s job.
The Data Migration Management product sheet
What we did not cover on this page: the steps from a small first step to the complete solution, why it pays to go this way, and how we work along the way. Feel free to forward it to your colleagues.
Frequently asked questions
What IT leaders usually ask
Why do we need a separate migration team next to the integrator?
The integrator implements the system, while we, independently of them, are responsible for the data: we cleanse it, run trial migrations and reconcile the numbers. That way you can see where the data stands well before go-live.
How do I know the numbers match?
Every trial migration comes with a reconciliation report that compares the data in the old and the new system. The cutover follows a runbook, and there is a rollback plan as well.
How long does it take?
2-9 months, depending on the size of the project.
How much does it cost?
After the assessment we give you a fixed price, or we work at an hourly rate. We give you an exact quote after the assessment or a conversation with one of our experts.
Also worth a look
Master Data Management
So the master data stays clean in the new system too, and old errors do not reappear.
Data Integration and ETL
Data flows between the new system and the other systems, without manual exports.
Data Governance
Who is responsible for the data, and who can decide about it, after the migration as well.
Further reading
What are you taking into the new system?
What makes data trustworthy after a system replacement, and what should happen to the duplicates?
Just looking around?
Read about data quality and system replacements on the blog, or subscribe to the Signal over Hype newsletter.
Data · Data Migration Management
Interested in data migration management? Let's talk.
Describe the situation in a sentence or two, and an expert in the field will get in touch with you.
Or call: +36 30 235 0100