M&A systems integration
Integrate multiple data sources for an acquisition
Rig is a technology and delivery partner for companies merging two data estates, from CRMs and ERPs to data warehouses.
Post-acquisition, you’ve got two systems for everything
You have two CRMs, two finance systems, two sets of reports, and an integration layer someone built years ago that nobody has touched since. The usual order is to choose the surviving systems first and integrate afterwards. That decision often takes months, and reporting waits for it.
- Day one
The board wants
One view of revenue, pipeline and cash in the first weeks
With RigBoth estates sync side by side, so combined reporting runs within weeks while every system is still duplicated.
- TSA exit
The board wants
The seller’s data safe before the transition agreement ends
With RigThe seller’s data and history sync into a warehouse you own before the exit date, whatever happens to the applications.
- Deal model
The board wants
The promised savings and revenue gains, shown quarter by quarter
With RigNumbers from both companies sit in one place, so you can track the deal model against what is happening.
- First close
The board wants
A consolidated reporting period on time, whether the systems are ready or not
With RigCombined reporting is already running, so finance does not build the combined figures by hand.
What happens to two of everything
Nothing is switched off on day one. Each duplicated layer moves to one governed version, and the source systems keep running until their own migration has passed its checks.
Two CRMs
One customer view
Both CRMs sync side by side. Duplicate accounts are matched in the warehouse with rules you can read, and neither CRM changes until you decide which one stays.
Two data estates
One governed layer
Warehouses, databases and key tools from both companies sync into one warehouse you own, and each is mapped before it arrives.
Two versions of every KPI
Certified metrics
Revenue, margin and pipeline are defined once for the group. Where the two companies counted differently, the difference is marked for finance to decide.
Reports in two BI tools
Dashboards and data apps
We rebuild the reports each company opens and retire the ones nobody opens.
Systems under a TSA
Synced out before the exit
Each system under the agreement keeps syncing until the exit date, so the last records arrive before handover.
Two sets of permissions
Role and row-level access
Who sees whose numbers is enforced from day one, including keeping the two sales teams apart while the deal requires it.
How the work runs
Map both estates
We build a systems map of each company that shows what runs, what flows between systems and who uses what. This is a fixed-price discovery sprint, and every later decision uses it.
Sync side by side
Both estates sync into one warehouse you own, on a schedule, with no change to either company’s production systems.
Report as one group
We match customers and certify the combined metrics. The board pack reads from this layer from the first close where the numbers are ready.
Migrate with the map
Each system migration is scoped and priced from the map, and nothing is switched off until its numbers match the original.
What Rig does not do
ERP implementation
Configuring a new ERP and buying its licences is work for an implementation partner. Rig maps the old systems, migrates the data and keeps reporting running through the move, alongside that partner.
Statutory accounting
Legal-entity consolidation stays in your finance systems and with your auditors. Rig reports across the entities from one set of definitions.
Switching systems off
The owner of each system decides when to switch it off. The map and the checks show when that is safe.
Instant hand-offs
Rig syncs on a schedule for reporting, planning and agents. Keep your integration tool for records that must move the moment something happens, and Rig Map shows those flows too.
Which system is changing?
Where to start
Common questions
How soon can we report as one group?
Combined reporting runs within weeks, long before the systems integration finishes. Both estates sync into one warehouse, the key metrics are certified, and the board pack reads from there while the systems underneath are still separate.
Do we need to choose the surviving CRM or ERP first?
No. Combined reporting can run before that decision, and the map shows what each system does, which is the evidence most groups use to choose.
How are duplicate customers matched?
They are matched in the warehouse, with rules your team can read and review. Nothing is merged inside the source systems, and a customer both companies share shows once, with both relationships.
Who can see whose data during the integration?
Role and row-level access applies from the first sync, to people and agents alike. If the deal requires the two sales teams to stay apart for a while, Rig enforces that while finance and the integration lead see the whole group.
Can the mapping start before we grant system access?
Yes. The first version of the map can come from your architecture documents and recorded walkthroughs. When we need data, access starts read-only, and wider permissions follow only for the phase you approve.
Who does the migration work?
Our engineers, your team or your systems integrator can do it, all working from the same map. Each migration has a fixed price and sign-off points, and nothing cuts over until the dry runs reconcile.
Does the work carry over to the next acquisition?
Yes. The map, definitions and models stay on Rig, so each add-on starts from the group’s existing map.
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.