Move the data, and account for every field
Most of a migration is mapping: what each field in the old system means and where it belongs in the new one. The engine does that work from the data itself, so the go-live date stops depending on how fast people can fill in a spreadsheet.
When you need it
- A core system is being replaced. An ERP, CRM or core platform is going, and the go-live date is already fixed.
- Two companies have merged. Two customer registers, product catalogues or supplier lists have to become one.
- A legacy system is being switched off. Its data has to land somewhere it can still be used.
- A previous attempt stalled. The project got as far as the mapping and stopped there.
What we take responsibility for
Who owns what is written into the project plan before we start: what we deliver, what your team decides, and who signs off each milestone.
- Mapping. Every field in scope is mapped and scored. Anything below your threshold goes to a named person on your side before it is used.
- Cleansing. Duplicates and inconsistent records are found and resolved by rules your team approves.
- Transformation. Changes of format, type and structure between the old system and the new. Which transformations the engine handles on your data is set out in the scope, not assumed.
- Testing. Trial loads, and a reconciliation of what left the old system against what arrived in the new one, measured against criteria you set.
- Transfer. The final load into the target system, after your sign-off.
How it runs
- Scope. Systems, data objects, acceptance criteria and milestones.
- Install and connect. The engine goes into your environment with access to the source and the target.
- Map, cleanse and transform. Anything below threshold is reviewed with your people as it comes up, not saved for the end.
- Trial loads. Each one is reconciled against the criteria until the numbers agree.
- Final load and sign-off. You approve the load. The audit log of every mapping decision stays with you.
How it is priced
Project price, split across milestones agreed at the start.
What you provide
- Hosts for the engine, sized to the data volume. The tiers are on the technical page.
- Access to the source system, and write access to the target.
- People who know the data, to approve what falls below threshold and to sign off each milestone.
What it is not
It does not choose your target system or design its data model. If the target model is still being designed, the migration waits for it, as any migration would.
Tell us what you need to move or connect
We will tell you whether this is the right service for it, or which one is.
Book a demo