---
title: "Post-merger IT and data integration checklist | Rig"
description: "A checklist for the systems and data work after an acquisition: inventory, what to keep, customer and product mapping, history, and a shared reporting layer."
canonical: "https://rig.so/blog/post-merger-it-integration-checklist"
format: markdown
---

[PE integrations and reporting](https://rig.so/blog/private-equity)

# Two report packs after a deal is how operating partners start arguing

A post-merger IT and data integration checklist covers five jobs: inventory both estates, decide which systems are kept, map customers, products and accounts, move history, and put a shared reporting layer on top. If both companies keep their own report pack, the operating partners end up comparing two different revenue numbers at every board meeting.

By [Toby Mather](https://rig.so/blog/authors/toby-mather) · Published 20 November 2026

[Request a case study](https://rig.so/book-demo?offer=case_study&from=%2Fblog%2Fpost-merger-it-integration-checklist)

## Key takeaways

- Inventory both estates by usage, so you rebuild the reports people open and retire the rest.
- Combined reporting does not have to wait for the decision on which CRM or ERP survives.
- Customer, product and chart-of-accounts mapping is where the two companies’ numbers disagree, so give finance the final say.
- Sync the seller’s history into a warehouse you own before any transition services agreement ends.
- Certify group metrics once and keep a list of every figure that differs from the old reports until leaders agree it.

1. 01**Inventory**
   
   Systems, data flows and what people use
2. 02**Decide what is kept**
   
   Keep, retire or rebuild, with owners
3. 03**Map customers and products**
   
   Matching rules finance can read
4. 04**Move history**
   
   Into a warehouse you own
5. 05**Shared reporting layer**
   
   Certified group metrics and access

The checklist runs left to right. Reporting can start once both estates sync, while system decisions continue in parallel.

## What does this checklist cover?

This checklist covers the systems and data side of an acquisition: CRMs, ERPs, warehouses, pipelines, BI tools and the reporting built on them. It leaves the operating model, organisation design, legal entity work and the people plan to the deal team and their advisers.

Most integration plans choose the surviving systems first and integrate the data afterwards, so reporting waits months for a decision. Syncing both estates into one warehouse early lets the group report as one while those decisions are still being made.

## How do you inventory both estates?

Build a systems map for each company before anyone picks a winner. Usage is the most useful column on it. In a merged education software group Rig worked with, an overnight audit traced every Tableau workbook to the tables behind it and found that only about a third were still in use, so the rebuild covered those and nothing else.

1. List every system in each company: CRM, ERP, billing, support, product data, warehouses, pipelines and BI.
2. Record the data flows between them, including old integrations nobody has touched in years.
3. Name an owner for each system and each report pack.
4. Check usage from query history and BI logs, and mark each report as used, stale or never opened.
5. Note contract end dates and any transition services agreement that covers a system.

## How do you decide which systems are kept?

Decide system by system, using the map. Each decision needs a business owner, a date and a list of what depends on the system. An education software company Rig worked with planned to switch off a large share of its custom Salesforce fields, and mapping every dependency first let the cleanup run in a safe order.

1. For each duplicated system, list the reports, workflows and integrations that read from it.
2. Mark each one keep, retire or rebuild, and record who agreed.
3. Scope and price each migration from the map, one system at a time.
4. Keep both systems running until the new one passes its checks against the old numbers.

## How do you map customers, products and accounts?

This is where the two companies’ numbers stop agreeing. One company counts a customer per contract and the other per site, product codes overlap, and the charts of accounts were built for different businesses. In the merged education group, a raw count of customers came back several times higher than the true number, because most Salesforce accounts had no account type set.

1. Agree what one customer, one product and one account mean for the group.
2. Match duplicate customers in the warehouse with rules finance can read and challenge.
3. Map both product catalogues to one group product list.
4. Map both charts of accounts to one reporting structure for the board pack.
5. Where the companies counted differently, mark the difference for finance to decide.

## How do you move history without losing it?

History is what makes year-on-year comparisons possible after the deal. The applications may change several times, so keep the history in a warehouse the group owns, separate from any one system.

1. Sync each company’s systems into one warehouse you own, on a schedule, without changing production systems.
2. Keep syncing systems covered by a transition agreement until the exit date, so the last records arrive.
3. Check each source for parity, including deleted records, before switching an old connection off.
4. Keep the raw history after a system is retired, so old reports can be reproduced.

## How do you get to one reporting layer?

One reporting layer means each group metric has one definition, one owner and one place it is calculated. Rebuild the reports each company uses on that layer, and check each one against the original before it replaces it. The merged education group keeps a list of every metric that gives a different result in the old and new reporting, so leaders can review each one and agree the true answer.

1. Define revenue, margin, pipeline and customer counts once for the group, and certify them with finance.
2. Rebuild the reports people use on the shared layer, and retire the ones nobody opens.
3. Check each rebuilt report against the original before switching readers over.
4. Set role and row-level access from day one, including keeping two sales teams apart while the deal requires it.
5. Point the board pack at the shared layer from the first close where the numbers are ready.

## What do reports and agents need afterwards?

Once the group reports from one layer, the same certified metrics can serve dashboards, analysts and AI agents. Agents need the definitions, table descriptions and access rules to be in place first, or they will query whichever of the old customer tables they find. The same layer then supports the next acquisition, which is why buy-and-build groups set it up once and reuse it.

## How does Rig do it?

Rig is a technology and delivery partner for companies merging two data estates. Rig Map builds the systems map of each company, with data flows, dependencies and usage, in a fixed-price discovery sprint. Ingest syncs both estates side by side into one warehouse you own. Rig’s engineers match customers, certify the combined metrics with finance and rebuild the reports people use, checking each against the original.

Gateway applies role and row-level access to people and AI agents on the shared layer, and each system migration is scoped and priced from the map. The two education software case studies show this work on a merged reporting layer and on a Salesforce dependency map.

## Common questions

When should systems work start in the deal timeline?

Start the inventory as soon as you have access to both estates, ideally before close where the deal allows. Combined reporting needs both estates syncing, and that work can begin on day one.

Do we have to merge every system?

No. Many groups keep separate operational systems for a long time and report from one shared layer. Merge a system when the map shows a clear saving or a dependency problem, and only after its replacement passes checks.

How soon can reporting be comparable?

Reporting becomes comparable once customers, products and accounts are mapped and the group metrics are certified. Syncing both estates first means this does not wait for system decisions.

Where do the education case studies fit?

One shows a merged education software group moving two data stacks onto one reporting layer. The other shows a company mapping every Salesforce dependency before a large cleanup. Both are anonymous, and you can request either from the case study pages.

Who should own the group metrics?

Finance usually owns revenue and margin definitions, with the data team controlling how they are calculated and who can see them. Each metric needs one named owner.

## Related reading

[Post-merger IT and data integration](https://rig.so/use-cases/ma-systems-integration)[Rig for private equity](https://rig.so/for/private-equity)[Buy and build](https://rig.so/use-cases/buy-and-build)[Portfolio reporting](https://rig.so/use-cases/portfolio-reporting)[Case study: one reporting layer for a merged group](https://rig.so/case-studies/education-software-merger)[Case study: mapping Salesforce dependencies](https://rig.so/case-studies/education-software-group)[Rig Map](https://rig.so/products/rig-map)[Gateway](https://rig.so/products/gateway)[Ingest](https://rig.so/products/ingest)

## Sources

Vendor documentation checked on 20 November 2026. Confirm current features and terms with the vendor.

- [Rig case study: one data and reporting layer for a merged group](https://rig.so/case-studies/education-software-merger)
- [Rig case study: map every Salesforce dependency before you clean it up](https://rig.so/case-studies/education-software-group)

## About the author

[Toby Mather](https://rig.so/blog/authors/toby-mather), Co-founder and CEO, Rig. Toby co-founded Rig after seeing how hard it was for business teams and AI to work with complex internal data. He was previously co-founder and CEO of Lingumi and CPO at Novakid.

Talk to Rig

## Read how a team like yours did it

We send a relevant, approved customer story. If we have no public story in your exact area yet, we say so and offer a call.

[Request a case study](https://rig.so/book-demo?offer=case_study&from=%2Fblog%2Fpost-merger-it-integration-checklist)[Book a call with an architect](https://rig.so/book-demo?offer=architect_call&from=%2Fblog%2Fpost-merger-it-integration-checklist)

---

- [This page as HTML](https://rig.so/blog/post-merger-it-integration-checklist)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)
