Integrating an acquisition

You bought the company. You got its systems and its data. Now what?

The deal comes with another CRM, another ERP and a finance system nobody on your side has logged into yet. Each one has its own idea of who your customers and suppliers are. EDOP helps you work out which records belong together and gives you one version of each, so you can run the group as one business.

Sound familiar?

The deal closed. The data didn’t.

On paper you’re one company. In your systems you’re still two, or five, and nobody worries too much until someone asks a question about the whole group.

The board wants one supplier number.

Finance pulls figures from four systems, gets four answers, and spends a week explaining the difference.

Two of your reps pitched the same customer.

Neither knew the other company already had the account. The cross-sell plan was a guess, and the customer could tell.

The master list lives in someone’s spreadsheet.

One analyst exports, cleans and reconciles it by hand. When they’re on vacation, so is the list.

Another deal is already in diligence.

Everything you matched by hand this time, you’ll be matching again in a few months.

Who it’s for

Every team is asking something different. They’re all stuck on the same thing.

Finance wants spend. Sales wants overlap. IT wants to avoid a rushed ERP migration. None of them get there until someone works out which records describe the same customer, supplier or product.

Role
What they need
What EDOP gives them
Acquisition integration lead

Evidence that the data side is on track, not just the org chart.

Every company’s records in one place, with the overlap counted and the duplicates resolved.

CFO and finance

One spend figure per supplier, and one payee to pay.

One record per supplier, linked back to every version of it in every system.

Procurement

A single supplier list to negotiate from.

Duplicates removed and addresses verified.

Sales leadership

To know who already buys from the other side of the business.

One record per customer across every CRM, so shared accounts are obvious.

CIO and IT

A combined view now, without forcing an ERP consolidation first.

Source systems stay as they are. Teams get the clean data through API, SQL or the EDOP interface.

What combining the data involves

What bringing an acquired company’s data together actually looks like.

Integrating an acquisition covers people, processes and systems. This part is just the data: getting the acquired company’s records to agree with yours, whether or not you ever combine the systems they live in.

Step
Without EDOP
With EDOP
01
Take stock
Each company keeps its own systems, and nobody can tell you how many customers you share.
Connect each company’s systems to Data Hub and see exactly what you’ve got, overlap included.
02
Match and merge
Someone exports everything to Excel and starts matching names by hand.
Four-phase deduplication pairs up the records that belong together. Anything it isn’t sure about goes to a person.
03
Run as one business
The list is stale by the time it’s shared, and finance and sales quote different numbers.
Finance, procurement and sales work from the same record for every customer, supplier and product.
04
The next deal
Back to Excel.
Plug the new company into the same Data Hub. Its records are matched against what’s already there.
Check your position

Can you answer these today?

Tick anything that would take more than a day, or a spreadsheet, to answer.

Tick any you can’t answer quickly.
Your options

Four ways to combine customer and supplier data, compared

Migrating to one ERP gives the cleanest end state but the slowest first answer. Spreadsheets give a fast first answer that goes stale. Black Tiger gives one governed record per customer and supplier across both companies while their systems stay as they are.

  • Does this
  • Partly, or only with extra work
  • Doesn’t do this

Scroll to compare →

Compared onBlack TigerEDOPSystems stay as they areOption 2Migrate onto the group ERP firstOption 3Reconcile in spreadsheets or BIOption 4Build it in-house
What you getOne governed record per customer and supplier, linked to each company’s own IDsOne system for both companiesA one-time overlap listWhatever the data team builds and maintains
Change to the acquired company’s systemsNone: records come in through files, feeds or the APIFull replacementNoneUsually none
Who does the workBusiness team with Black Tiger; little IT timeIT and a systems integratorFinance or operations analystsData engineers
Uncertain matchesScored and sent to a person to decideHandled in migration rulesJudged by hand, cell by cellWhatever rules the team writes
New duplicates after day one
Yes: Every new record is checked on arrival
Partly: Prevented once both companies share one system
No: Not caught
Partly: Only if someone builds it
Audit trail of decisions
Yes: Yes, per value
Partly: Migration logs
No: No
Partly: Only if someone builds it
Reusable for the next deal
Yes: Yes, add the next company as a source
Partly: Partly: methods and templates carry over
No: No
Partly: Partly
Main riskNew vendor alongside your ERP; writing merged records back into the ERP is on the roadmap, not available todaySynergy decisions wait for the migrationWrong answers from a stale copyThe project depends on one or two people

How to choose

Each option fits a different deal. Pick the one that matches yours.

Option 2Migrate onto the group ERP first

If the deal is large, the integration budget is approved, and synergy decisions can wait for go-live.

Option 3Reconcile in spreadsheets or BI

If you need one answer, once, for a board pack and the lists are small.

Option 4Build it in-house

If you have data engineers who can own matching and stewardship for years, and few source systems.

Black TigerUse Black Tiger

If you need a working, governed view of shared customers and suppliers while both companies keep their systems, and you expect to do it again on the next deal.

Last checked: November 2026. Option columns describe each category in general; individual products differ.

Built on EDOP

This runs on Black Tiger’s Enterprise Data Operations Platform. Our data engineers work alongside your team while you bring each company’s data together.

Data Hub
Data Dedup
Data Verify
Reference Data
Data Reports
See the full platform

Before you ask

We’re already partway through the integration. Is it too late?

Not at all. EDOP works with whatever systems you have right now, migrated or not. A good place to start is one data set, usually suppliers or customers, then add the rest as systems are merged or switched off.

Do we need to move everyone onto one ERP first?

No. Your systems keep running as they are. EDOP pulls their data into Data Hub and combines it there, so you get one view before, during or instead of a system consolidation.

What happens when we buy the next company?

You connect its systems to Data Hub. Its records are checked against the ones you already have, so it joins the same view instead of starting a new list.

What kind of data can we combine?

Customers, suppliers, products and employees, including data that’s stuck in PDFs.

See it on your data

Send us two lists that should match

Pick customers, suppliers or products from two companies you own. We’ll show you how many are really the same, and what the combined record looks like.