An acquisition does not automatically create a case for moving the acquired company onto the buyer’s ERP. The right decision depends on the deal thesis, operating model, process overlap, system condition, data risk, contract commitments and the level of integration the business actually needs.
For some transactions, the safest choice is to keep the target’s ERP running while reporting and controls are connected. Others justify selective back-office integration, a two-tier architecture or a phased move into the acquirer’s platform. A full replacement may be appropriate—but treating it as the default can introduce avoidable cost and operational risk.
This guide gives CFOs, CIOs, COOs, integration-management-office (IMO) leaders and private-equity operating teams a practical way to decide what to retain, connect, consolidate or replace, and how to protect business continuity while doing it.
Start with the deal thesis, not the ERP roadmap
The ERP decision should follow the operating model the transaction is intended to create. Before selecting a system, clarify what the buyer expects to achieve: cost synergies, shared services, cross-selling, supply-chain scale, geographic expansion, product portfolio expansion, or continued operation of the target as an independent business.
Those objectives lead to different technology choices. If the acquired company will remain operationally independent, immediate consolidation may add disruption without creating corresponding value. If finance, procurement, inventory or order management will be combined, separate systems may make the target operating model expensive to run.
ERP is also only one part of the application landscape. CRM, payroll, tax, warehouse management, manufacturing, ecommerce, banking, EDI and reporting systems may have their own integration priorities and contractual constraints. A sound plan distinguishes the ERP core from the applications and interfaces around it.
Four ERP integration paths after an acquisition
Most acquisition programmes can be assessed against four practical paths. These are operating choices, not product categories; a company may use different paths for different business units or process areas.
1. Retain the target ERP and operate separately
The acquired business continues using its existing ERP. The buyer establishes the minimum reporting, financial-control, security and governance connections needed to oversee the investment.
- Best suited to: a target with a differentiated operating model, limited process overlap, strong standalone performance, or a deal structure that preserves autonomy.
- Potential advantages: less immediate change for employees and customers; lower short-term migration exposure; preserves specialist workflows.
- Trade-offs: duplicate support, licensing, controls and reporting; more complex group consolidation; separate master data and process standards.
- Decision test: can the buyer obtain reliable financial and operational visibility without forcing a full system migration?
2. Connect selected processes while keeping both ERPs
The companies retain their ERP platforms but integrate specific workflows or data domains. Examples may include group reporting, intercompany transactions, shared customer or supplier records, procurement visibility, or consolidated inventory reporting.
- Best suited to: businesses that need operational coordination but are not ready—or do not need—to standardize every process.
- Potential advantages: targeted synergy capture without a wholesale replacement; staged integration; ability to preserve local capabilities.
- Trade-offs: interface monitoring, data ownership disputes, reconciliation work and dependency on integration architecture.
- Decision test: can the business define a clear system of record for each shared data object and process?
3. Adopt a two-tier ERP model
The acquirer retains its corporate ERP while the acquired business operates on a separate, often more suitable or simpler ERP. A controlled integration layer connects the two for agreed group processes and reporting.
- Best suited to: a large group acquiring smaller or operationally distinct businesses, especially where a single enterprise template would be too expensive or restrictive.
- Potential advantages: faster onboarding of acquisitions in some circumstances; local process flexibility; less pressure to customize the corporate ERP for every subsidiary.
- Trade-offs: governance across multiple platforms; duplicated application administration; integration and reporting complexity; need for a defined architecture standard.
- Decision test: can the group manage multiple ERPs with consistent controls, master-data rules, reporting definitions and support ownership?
4. Consolidate onto the buyer’s ERP or replace both platforms
The acquired business migrates to the acquirer’s existing ERP, or the combined organization selects a new platform. This can create a more standardized operating environment, but it is also the path with the broadest process, data, change and cutover implications.
- Best suited to: high process overlap, a clear shared-services model, an obsolete or unsupported target platform, or a deal thesis that depends on common operations.
- Potential advantages: fewer long-term platforms; common processes and controls; potential reduction in duplicated support and reporting effort.
- Trade-offs: migration cost, temporary dual running, training, customization decisions, business disruption and possible loss of valuable target-specific capability.
- Decision test: do the measurable benefits of standardization exceed the full cost and risk of moving the business?
Choose the path with a decision matrix
Use the matrix below to structure the first executive discussion. It is a screening tool, not an automatic scoring model. Validate the evidence for each factor before committing to a direction.
| Decision factor | Retain separately | Selective integration | Two-tier ERP | Consolidate / replace |
|---|---|---|---|---|
| Operating autonomy | High | Medium–high | Medium–high | Low–medium |
| Process overlap | Low | Targeted | Mixed | High |
| Need for common controls and reporting | Group-level reporting | Selected workflows | Standardized interfaces and controls | Broad process standardization |
| Near-term migration disruption | Lowest | Limited to selected domains | Depends on onboarding scope | Highest |
| Long-term platform complexity | Higher | Higher | Managed multi-platform | Potentially lower, if consolidation succeeds |
| Typical reason to choose | Preserve a distinct business | Capture specific synergies | Scale acquisitions without one rigid template | Run a genuinely combined operation |
Important: “Consolidate” does not automatically mean “use the buyer’s current ERP.” If the acquirer’s system is heavily customized, nearing end of support, poorly aligned to the target’s industry, or expensive to extend, a broader platform decision may be justified. Conversely, a new ERP selection should not be disguised as an acquisition integration requirement if the deal does not depend on it.
ERP due diligence: what to discover before the deal closes
ERP due diligence should produce evidence that helps the deal team understand operating risk, transition cost and the feasibility of the intended operating model. It is not simply an application inventory.
1. Platform condition and support exposure
- Record ERP product, edition, version, hosting model, deployment architecture and major customizations.
- Identify support and maintenance status, upgrade constraints, technical debt and specialist skills dependencies.
- Separate standard product capabilities from custom code, partner extensions and connected applications.
2. Business process and operational dependency
- Map order-to-cash, procure-to-pay, record-to-report, plan-to-produce, inventory, service and project workflows as relevant to the target.
- Identify business-critical processes that depend on manual workarounds, spreadsheets, individual employees or undocumented integrations.
- Determine which workflows are genuinely common and which support a differentiating product, service or customer experience.
3. Data, controls and reporting
- Assess chart of accounts, legal entities, dimensions, customer and supplier masters, item masters, units of measure and opening balances.
- Check data quality, duplicate records, ownership, retention, audit trails and reconciliation procedures.
- Understand how management reporting, statutory reporting, tax, consolidation and internal controls are produced today.
4. Contracts, licensing and third-party dependencies
- Review ERP subscriptions, user metrics, renewal dates, minimum commitments, support arrangements and termination terms.
- Check change-of-control, assignment, hosting, data-processing and third-party consent clauses with the appropriate legal and procurement teams.
- Identify implementation partner, independent software vendor, hosting provider, payroll, banking, EDI and other dependencies.
5. Transition feasibility and people
- Identify internal system owners, administrators, developers, report writers and process experts whose knowledge is essential.
- Assess capacity for integration work alongside normal operations and other deal workstreams.
- Estimate the time and cost of retaining, connecting, migrating, replacing and retiring the current environment.
During the pre-close period, access to target information and permitted activities must be managed through the transaction’s legal and clean-team protocols. Do not assume the buyer can direct the target’s systems, combine data or begin operational integration before closing. Legal counsel should define what diligence and planning are permitted for the specific transaction.
Separate Day 1 readiness from the long-term ERP end state
Day 1 is about keeping the business operational at legal close—not completing the ERP transformation. The target should be able to process orders, ship products, invoice customers, pay employees, receive supplier deliveries and meet essential reporting and control obligations under the approved transition model.
| Workstream | Day 1 requirement | Post-close integration work |
|---|---|---|
| Finance | Ability to close, report, pay and meet control obligations | Chart-of-accounts alignment, consolidation, shared services and process standardization |
| Customers and sales | Order capture, pricing, credit and invoicing continue | Customer master alignment, CRM/ERP workflow changes and account harmonization |
| Supply chain | Purchasing, receiving, inventory and fulfilment remain reliable | Supplier rationalization, planning, warehouse and intercompany process integration |
| People | Payroll, time capture and essential employee access function | HR and payroll platform consolidation, role redesign and training |
| Technology and data | Approved access, support, backups, monitoring and essential interfaces are in place | Data migration, architecture changes, application retirement and reporting transformation |
Build a Day 1 checklist around business outcomes and named owners, not a list of systems to switch on. A system may remain unchanged on Day 1 while its future-state decision is already documented, funded and governed.
Plan the first 100 days around decisions and dependencies
The first 100 days should reduce uncertainty and establish control. It should not become an arbitrary deadline for a complete ERP migration. The exact sequence depends on deal complexity, regulatory obligations, system condition and the agreed operating model.
- Confirm the interim operating model. Name process owners, system owners, escalation routes and decision rights across buyer and target teams.
- Stabilize critical operations. Monitor financial close, order processing, procurement, payroll, inventory, customer service and essential interfaces.
- Validate diligence assumptions. Recheck application inventory, contracts, data quality, customizations, support dependencies and costs discovered during diligence.
- Approve the ERP direction. Decide what to retain, connect, move, replace or retire by business unit and process domain.
- Establish the target architecture and controls. Define integration patterns, system-of-record ownership, identity and access controls, reporting definitions and data governance.
- Build a sequenced roadmap. Prioritize high-value, lower-risk changes; schedule complex migrations around financial and operational calendars.
- Track value and readiness. Measure realized benefits, one-off and recurring costs, operational incidents, data quality, adoption and TSA exit readiness.
Calculate the full cost of each ERP option
A comparison based only on software subscription or implementation fees will understate the economics of an acquisition. Build a scenario-based total cost of ownership model for each credible path.
One-time costs may include diligence, architecture, data cleansing, integration development, migration, testing, process redesign, training, change management, partner services, contract exit charges and temporary dual running.
Recurring costs may include subscriptions, hosting, support, security, integration monitoring, internal administration, specialist contractors, reporting and ongoing compliance.
Risk-adjusted costs should consider the operational impact of cutover failure, delayed financial close, fulfilment disruption, lost customer visibility, inaccurate inventory, payroll issues and delayed TSA exit. Do not insert generic percentages for these risks. Estimate exposure using the target’s actual volumes, margins, service obligations and control requirements.
Compare those costs with the deal-specific benefits: reduced duplicate operations, improved visibility, consolidated procurement, faster reporting, better customer coordination or the ability to scale a shared process. State assumptions clearly and show sensitivity where the business case depends on uncertain timing or synergy realization.
Common ERP integration mistakes in acquisitions
- Choosing the platform before defining the operating model. This turns a business decision into a technology preference.
- Assuming one ERP is always cheaper. Consolidation may reduce platform count but increase customization, migration and support costs.
- Moving data without agreeing ownership. Conflicting customer, supplier, item and financial records create reconciliation and control problems.
- Underestimating contracts and licensing. Renewal dates, user metrics, change-of-control terms and third-party dependencies can materially affect timing and cost.
- Combining Day 1 with the end-state programme. A rushed migration can put business continuity at risk when a controlled interim model would have been safer.
- Retiring the old system too early. Archive, audit, statutory, customer-service and operational requirements may continue after migration.
- Measuring technical completion instead of deal value. A migration can finish while expected synergies, process adoption or reporting improvements remain unrealized.
A practical decision rule for the deal team
Before approving an ERP integration path, require a one-page decision record that answers these questions:
- What operating-model change does the acquisition require?
- Which processes must be shared, and which should remain distinct?
- What must work on Day 1, and what can wait?
- What evidence supports retaining, connecting, adopting two tiers, or consolidating?
- Who owns each critical data domain and system interface?
- What are the one-time, recurring and risk-adjusted costs of each option?
- What conditions must be met before migration, cutover or TSA exit?
- How will the IMO verify that the technology plan is delivering the deal thesis?
If the team cannot answer these questions with evidence, the next step is not to select an ERP. It is to close the diligence gaps, document the interim model and assign accountable owners.
How to continue the ERP evaluation
ERP integration is only one part of the combined application architecture. If the transaction also requires CRM and ERP workflow alignment, review the ERP and CRM integration architecture guide. For a target platform that may need modernization, use the ERP upgrade vs. replacement decision framework. Teams preparing for a new implementation can also use the ERP implementation readiness assessment.
When the integration path requires a platform change, compare products against the combined organization’s real requirements—not just the buyer’s existing technology preference. The right answer may be a single ERP, a governed two-tier model or a period of controlled coexistence. The objective is to protect operating continuity while making the deal’s intended value achievable.
For additional context on ERP choices in acquisition programmes, see Baker Tilly’s analysis of ERP considerations in M&A and the TCS post-merger ERP integration roadmap. The distinction between Day 1 readiness and longer-term integration is also addressed in Deloitte’s M&A integration planning guidance.
