Business Systems
How to integrate systems after an acquisition without replacing everything
Acquisitions create a systems problem fast. Connect reporting, data, and cross-company workflows without forcing every acquired business onto the same software.
- Published
- Author
- Demari Miller
- Series
- Cass & York
- Reading time
- 5 min read
The deal closes. Then the systems problem starts. The acquired company has its own CRM, accounting software, field tools, spreadsheets, customer records, reporting habits, and operating language. Corporate needs visibility across the group, but replacing every local system can create a second integration problem on top of the first.
The goal should not be to make every company look identical. The goal is to make the parts of the business that need to work together actually work together.
The wrong first move is often “standardize everything”
After an acquisition, it is tempting to pick the parent company's software stack and migrate the new business into it. Sometimes that is the right answer. Often it is not the first answer.
The acquired company may have scheduling software its dispatchers know well, a field application tied to how crews work, an industry-specific platform that the parent company does not use, or years of history in an accounting system that is expensive to unwind. Replacing those systems can mean months of migration work before leadership gets the visibility it wanted in the first place.
A better starting question is: what actually needs to become common across the group?
Create a common operating layer above the businesses
Instead of forcing every acquired company onto the same software immediately, connect the systems that already run the businesses and create a common layer for the information and workflows leadership needs across the portfolio.
That layer can pull from CRMs, accounting systems, ERPs, field applications, spreadsheets, document repositories, telematics systems, and other operating tools. The source systems can remain local while selected data is normalized into a group model.
This is what makes it possible to answer basic questions without assembling five spreadsheets every month: How much revenue did each business produce? Which customers overlap? Which locations are underperforming? Which jobs are waiting on paperwork? Which invoices are stuck? Which service lines are growing across the group?
Standardize the meaning before you standardize the software
Two companies can record the same real-world activity in completely different ways. One may call a service “commercial maintenance.” Another may split the same work across three service codes. One CRM may store a customer at the parent-company level while another stores every branch as a separate account.
If those differences are ignored, the consolidated dashboard can look polished while still being wrong.
The integration work should define a small set of group-level concepts and map each company's local records into them. Common examples include:
- Customers and customer groups
- Locations and business units
- Service or product categories
- Jobs, projects, orders, and invoices
- Revenue and cost categories
- Operating statuses and approval states
- Shared KPIs and reporting periods
The local detail does not need to disappear. A useful model keeps the source record, source system, and original value so people can trace a group number back to the business that produced it.
Decide what should stay local
Integration does not require operational uniformity. A portfolio company can keep its scheduling tool if it works. A field team can keep the application that fits its workflow. A specialized line of business can keep software the rest of the group does not need.
The question is whether the system blocks visibility, creates unnecessary manual work, or prevents a process that genuinely needs to be shared.
That distinction matters because it keeps the integration program focused on business outcomes instead of software replacement for its own sake.
Standardize the workflows that cross company boundaries
Reporting is usually the first problem leadership notices, but acquisitions also expose workflow gaps. A regional company may approve purchases one way, another may email PDFs to accounting, and a third may track exceptions in a spreadsheet.
You do not need to rebuild every local process. Start with the handoffs that matter across the group: billing review, purchase approvals, customer onboarding, compliance checks, close procedures, document collection, exception management, or other processes where work routinely crosses systems or teams.
A shared workflow can sit above the existing applications. The local system remains the system employees use for day-to-day work, while the group layer collects the required data, routes approvals, tracks exceptions, and shows what is still unresolved.
Make the second acquisition easier than the first
The biggest payoff comes when acquisition integration becomes repeatable. The first company is where you discover the common entities, reporting rules, source mappings, security model, and workflow patterns. Those should become reusable integration assets, not one-off project notes.
A repeatable onboarding package might include connectors for common systems, a canonical customer and location model, mapping templates, data-quality checks, identity rules, reporting definitions, workflow components, and a checklist for bringing a new company into the group.
Then the next acquisition does not start with a blank whiteboard. You already know the questions to ask and the architecture the new business needs to plug into.
What leadership gets
Done well, the parent company gets a group-level view without pretending every operating business is the same. Finance can reconcile numbers back to their sources. Operations can see exceptions across companies. Leadership can compare performance using consistent definitions. Local teams can keep tools that still serve them.
The result is not one giant replacement platform. It is a connected operating environment where information can move across the portfolio and where the differences between companies are explicit instead of buried in spreadsheets.
Where Cass & York fits
Cass & York builds the integration and operational software layer between the systems companies already use. For acquisitive businesses, that can mean connecting portfolio-company applications, creating a shared data model, consolidating reporting, automating cross-company workflows, and building the internal tools needed where off-the-shelf products stop fitting.
If your acquisition strategy is creating a growing stack of disconnected systems, talk to Cass & York about building the layer between them.
Share this article