Migrate
Migrate systems, reports and data at a fixed price, in weeks
Our engineers work with your team on CRM, customer platform and ERP changes, BI retirement and merger integration.
Know what your systems really do before you move them
Custom fields carry meanings nobody wrote down. An integration writes the number finance reports on. An object has been dead since 2019 and still sits in every export.
Rig reads all of it, the schema and the way the systems are used together: how records are structured, which fields are written to and by what, which pipelines and reports depend on them, and which parts of the estate nobody has touched in a year. The migration plan is built on that map.
Common migration scenarios
CRM to CRM
Before you move a CRM, you need to know which fields are still used and which are ten years of abandoned experiments. Rig audits the org against real usage, flags the fields and objects nobody needs, and shows the automations a previous integrator left behind.
Where that logic belongs in the warehouse, it moves there first, so finance flows keep working through the cutover. Then we map, dry run and migrate.
Merging two data estates
A merger leaves you with two of everything and one platform to reach. You have to decide which CRM survives, what happens to ten years of finance history in the one that does not, and in what order flows can be cut over without breaking month-end.
Rig gives you an estate map scoped by legal entity, a fate for every system, and a sequence built on what depends on what. Definitions are aligned once and applied to past data, so reporting survives the merge.
We also move warehouses and semantic layers, importing the metric definitions you already have so nobody retypes them.
Customer story / An education software group
One data and reporting layer for a merged group, without the technical debt
After two education software companies merged, the group is bringing both companies’ warehouses, pipelines, BI and CRM data onto one governed data and reporting layer in Snowflake. It is rebuilding only what people use, and retiring tools as it goes.
Read the storyCommon questions
Can we just do the audit?
Yes, and many engagements start there. You get the evidence and a prioritised plan, and you decide afterwards whether there is a migration at all.
Is the audit only for CRMs?
No. The CRM is usually at the centre, but the audit covers the estate around it: ERP, finance, the warehouse and the integrations between them.
How long does a migration take?
It depends on the size of the estate, but the shape is the same. The audit plan comes back within a few weeks of us getting access to your sources. The migration is a second phase, scoped and priced from that plan and measured in weeks. We will tell you on the call if yours is the exception.
Do you run the migration, or do we?
Either of us can run it, and we often share the work. Some clients want us to run it, while others take the map, the plan and the dry run and cut over with their own team. A few have a systems integrator who works from what we produce. The audit is the same in all three cases.
We already have a systems integrator. Does Rig replace them?
Not usually. Mapping, auditing and dry runs are the parts Rig makes faster, and they are the parts most likely to go wrong by hand. Plenty of engagements end with an integrator running a plan that Rig built and checked.
What happens to our reporting history?
Definitions are aligned once and applied to past data, so a metric means the same thing on either side of the move. Anything that cannot be reconciled is flagged during the audit, before cutover.
Do you need access to production data to start?
No. The first version of the map is built from synthetic samples of the schema. When real data is needed, access starts read-only and least-privilege, and wider permissions are granted only for the phase you approve.
Can you translate our legacy SQL or stored procedures automatically?
No. Be wary of any tool that promises it. Rig maps the estate, shows what is used, and checks that answers still match after the move. Our team converts the SQL with you, working from that map.
Can you migrate a semantic layer or existing metric definitions?
Often we can. Where definitions already exist in a modelling or BI layer, we import each one with its SQL, joins and description intact. Where they only exist in people’s heads, the audit is how they get written down.
What if the destination has no query history to learn from?
That is normal for a platform that has just been set up. Rig profiles the warehouse directly, tests joins against real key overlap, proposes metrics and checks them against the data, then drafts the definitions for your team to review.
Talk to Rig
What work do you want to improve?
Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.