The deal thesis for most PE-backed platform companies includes add-on acquisitions. Buy a platform at 8x, bolt on smaller companies at 5x to 6x, grow the combined entity, exit at 9x to 10x. The math works beautifully on a spreadsheet.
Where it breaks down is data.
Every add-on acquisition brings legacy ERP systems, different CRM platforms, different chart of accounts structures, and different definitions for the same metrics. Revenue means one thing in the platform company and something subtly different in the add-on. “Active customer” is defined one way in system A and another way in system B. The monthly close that took five days now takes twelve because the finance team is reconciling across two (or three, or four) sets of books.
One mid-market platform company I worked with completed three add-on acquisitions over 18 months. Each acquisition was strategically sound. The combined revenue was $120M. But fragmented data infrastructure delayed the consolidated reporting capability by six months. During that period, the management team could not produce a reliable combined P&L, could not reconcile customer data across entities, and could not answer basic questions from the PE sponsor. The estimated EBITDA impact of that delay, counting duplicate systems, manual reconciliation labor, and delayed cross-sell initiatives, was $8M.
That number is not unusual. Bain’s research on M&A integration consistently finds that data and systems integration is the most commonly cited challenge in achieving deal synergies. Not cultural integration. Not customer retention. Data.
Why data integration is different from systems integration
A common mistake is treating data integration as a technology project. Migrate everyone to the same ERP. Consolidate on one CRM. Implement a single data warehouse. These are systems integration tasks, and they take 12 to 18 months in the best case.
Data integration is the prerequisite. Before you can consolidate systems, you need to answer foundational questions. What does “revenue” mean across entities? How are customers defined and counted? Which chart of accounts structure will be the standard? What KPIs will the combined entity report?
You can answer these questions without touching a single system. And you should. Because the six to twelve months it takes to migrate systems is time you cannot afford to spend without consolidated reporting.
The goal of data integration is not perfect systems integration. It is a single source of truth for the metrics that matter, delivered in a timeframe that supports the value creation plan.
The 90-day framework
This framework assumes you have just closed an add-on acquisition. The platform company has established data infrastructure (not perfect, but functional). The add-on has its own systems and processes. The PE sponsor needs consolidated reporting as soon as possible.
Days 1 through 30. Map and assess
The first month is about understanding what you bought and where the data differences are. Resist the urge to start fixing things. You will make better decisions with a complete picture.
Inventory both data environments. For each entity, document the systems (ERP, CRM, billing, HR, BI tools, spreadsheets), the data they hold, the people who manage them, and how data flows between them. Pay special attention to the manual processes. The add-on’s critical business logic probably lives in Excel, and the person who maintains it may not have disclosed that during diligence.
Map the definitional differences. This is the most important activity in the first month. Pull the definitions for every metric that both companies report. Revenue, customer count, retention, churn, ARR/MRR, EBITDA adjustments, cost allocations. Compare them side by side.
I have seen “revenue” defined four different ways in a two-company combination. The platform recognized on delivery. The add-on recognized on invoice. The platform included setup fees in revenue. The add-on deferred them over the contract term. All legitimate accounting treatments. But you cannot add them together and call it consolidated revenue without understanding and adjusting for the differences.
Assess data quality. For each entity, test the basics. Does revenue reconcile across systems? Are customer counts consistent? Are there unexplained discontinuities in historical data? Use the 48-Hour Test framework on the add-on, treating it as if you were the buyer running diligence (which, in a sense, you are).
Identify integration priorities. Not everything needs to be integrated at once. Rank by impact on the value creation plan. Revenue reporting is almost always number one. Customer data is usually number two. Operational metrics depend on the thesis. Cost data is important but can often wait.
Deliverable at Day 30: A data integration assessment that maps both environments, catalogs definitional differences, flags data quality issues, and recommends a prioritized integration sequence with estimated effort for each item.
Days 31 through 60. Align and reconcile
Now you start fixing things, but in a specific order. The goal for month two is to get to a reconciled combined view of the metrics that matter, even if the underlying systems are still separate.
Harmonize the chart of accounts. Decide which chart of accounts structure will be the standard. Map the add-on’s accounts to the platform’s structure. This mapping does not require changing the add-on’s ERP. It requires a translation layer that converts the add-on’s financial data into the platform’s framework for consolidated reporting.
Most mid-market companies have between 100 and 300 GL accounts. The mapping work for a straightforward add-on takes 40 to 80 hours. The tricky part is not the mapping itself. It is the judgment calls. When the add-on classifies something as COGS that the platform classifies as SG&A, someone needs to decide which treatment applies to the combined entity. Get the CFO to make these calls early. Leaving them unresolved creates drift that compounds every month.
Deduplicate the customer master. If the platform and the add-on serve overlapping markets, there will be shared customers. The same company appearing in both CRMs with slightly different names, different contacts, and different contract terms. This overlap is often the source of the cross-sell opportunity that justified the acquisition.
To capture that opportunity, you need a unified customer view. Start by exporting customer lists from both entities. Match on company name, domain, and address. Flag duplicates. For each duplicate, designate one entity as the master record and decide how to handle the relationship going forward.
This sounds simple. In practice, a $50M to $100M combined entity typically has 200 to 500 duplicate customer records requiring manual review. Plan for it.
Align KPI definitions. For the metrics that the PE sponsor tracks, agree on a single definition. Write it down. Calculate both entities’ metrics using the new definition. Restate historical data where feasible. Where historical restatement is not feasible, document the bridge between old and new definitions.
The common KPIs that need alignment: revenue (recognition methodology), retention (gross and net, with cohort definitions), customer count (active definition), ARR/MRR (calculation basis), CAC (allocation methodology), and close rate (pipeline stage definitions).
Deliverable at Day 60: A consolidated reporting package that shows combined financial and operational metrics using harmonized definitions. The data may still come from separate systems, but the output is one set of numbers the PE sponsor and board can rely on.
Days 61 through 90. Integrate and automate
The final month is about making the reconciled view sustainable. A manual consolidated report that takes five days to produce is a stopgap. You need a process that runs monthly without heroic effort.
Automate the consolidation. Build the translation layer between the add-on’s systems and the platform’s reporting. This can be as simple as a structured spreadsheet with documented formulas, or as robust as an automated data pipeline. The complexity depends on your systems and your team. The principle is the same: reduce the manual steps required to produce the consolidated report.
For most mid-market companies, this means building an Excel-based or Google Sheets-based consolidation workbook with automated data feeds from each entity. Not glamorous. But reliable, auditable, and maintainable.
Establish the combined close process. Document the end-to-end monthly close for the combined entity. Who is responsible for each step? What data needs to be exchanged between entities? What are the dependencies? What is the deadline for each component?
The first combined close will be slow. Expect 15 to 20 business days. By month three, target 10 to 12. By month six, target 7 to 8. Each cycle should include a brief retrospective: what went wrong, what took too long, what can be improved.
Build the cross-sell analytics. If the deal thesis includes cross-sell between entities, build the analytics now. Using the deduplicated customer master, identify customers of Entity A that are not customers of Entity B, and vice versa. Segment by size, industry, geography, and product fit. Quantify the cross-sell opportunity by segment. Deliver this to the sales team as a prioritized target list.
This analysis is often the first tangible evidence of deal synergies. Showing the board that you have identified $15M in cross-sell pipeline within 90 days of close is a powerful signal that the integration is on track.
Deliverable at Day 90: An automated (or semi-automated) consolidated reporting process, a documented combined close procedure, and a quantified cross-sell pipeline. The PE sponsor can see combined metrics monthly, the finance team can produce them without extraordinary effort, and the sales team has actionable integration targets.
The four hardest problems and how to handle them
Customer master deduplication at scale
When you have thousands of customers across two or more entities, manual deduplication is impractical. The matching logic needs to account for variations in company names (Inc vs. Inc. vs. Incorporated), mergers and acquisitions among your own customers, and multiple locations or divisions that buy separately.
Start with automated matching on domain name and EIN/tax ID. These are the most reliable unique identifiers. Then layer on fuzzy matching on company name. Finally, manual review for the gray zone (typically 10% to 15% of records). Assign a clear master record for each duplicate and document the merge logic.
Chart of accounts harmonization across different ERPs
If the platform runs NetSuite and the add-on runs QuickBooks, the account structures may have fundamentally different levels of detail. The platform might have 250 accounts with clear hierarchies. The add-on might have 80 accounts with flat structures and heavy use of classes or departments for segmentation.
Do not try to make them match perfectly. Build a mapping that translates the add-on’s structure into the platform’s framework at the reporting level. Accept that some granularity will be lost in translation. As long as the consolidated P&L, balance sheet, and cash flow are accurate and consistent, the mapping is working.
KPI definition alignment when historical data cannot be restated
Sometimes you cannot restate historical data to match the new definition. The add-on did not track the data required for the platform’s retention calculation. Or the historical revenue recognition was done differently and restating three years of data is impractical.
In these cases, create a clear bridge. “From the date of acquisition forward, all metrics use the harmonized definitions. Historical data prior to acquisition uses the entity-specific definitions. Here is the documented crosswalk showing the differences and their estimated impact.”
Buyers and PE sponsors can work with this. What they cannot work with is unlabeled inconsistency.
Reporting consolidation when the finance team is already at capacity
This is the most practical and the most common challenge. Your platform finance team is already running at full capacity. Adding the close and reporting responsibilities for an acquired entity pushes them past their limit. Quality drops. Timelines slip. The team burns out.
There are two levers. Temporary capacity (a contract resource dedicated to integration for 90 to 120 days) or process simplification (eliminating or deferring non-essential reporting during the integration period). The best approach is usually both. Add a temporary resource and reduce the reporting scope to the essentials for the first three months.
The mistake that costs the most
The single most expensive mistake in add-on data integration is waiting. Waiting for the “right” technology. Waiting for the systems migration. Waiting for the next hire. Every month without consolidated reporting is a month where the PE sponsor cannot see the combined picture, the cross-sell opportunity is not being pursued, and the integration synergies in the deal model are not being validated.
The 90-day framework is not about achieving perfection. It is about achieving visibility. Once the management team and the PE sponsor can see the combined metrics, they can make informed decisions about where to invest, what to fix, and how to accelerate the value creation plan.
For more on what the first 100 days after any acquisition should look like, see Post-Acquisition Data Playbook: The First 100 Days.
For the data checklist that buyers will eventually apply to your combined entity when you go to exit, see PE Exit Readiness: The Data Checklist Most Teams Miss.
For a weekly brief on data integration, portfolio company operations, and PE value creation, subscribe to Inside the Data Room.