Key takeaways
- System integration after close typically takes 60–180 days depending on complexity, with ERP migrations at the high end and CRM migrations in the 60–90 day range.
- The most common hidden cost in post-close integration is undocumented systems, integrations, custom scripts, and shadow tools that no one inventoried before close.
- Founders who document their full system inventory, vendor contracts, and integration dependencies before close reduce integration cost by 30–50% and eliminate the most common post-close surprises.
In this article
- Why technology integration is the most overlooked post-close risk
- The three post-close technology outcomes
- ERP systems: NetSuite, QuickBooks, Sage, what migration actually costs
- CRM migration: data, field mapping, and historical record preservation
- Payroll and HR systems: ADP, Paychex, Gusto, parallel payroll and transition risk
- What to document before close: the system inventory
- Integration timeline benchmarks by system type
- Common integration failure patterns
- Integration cost estimation and budgeting
- Common mistakes in post-close technology integration
Why technology integration is the most overlooked post-close risk
Technology integration issues are cited in 56% of post-close integrations as a source of significant unexpected cost, with median unplanned spend of $150,000–$500,000 for middle market transactions.
60–180 days
typical full technology integration timeline post-close
$150K–$500K
median unplanned technology integration spend in middle market deals
56%
of post-close integrations cite technology issues as a significant unexpected cost source
Most M&A conversations focus on financial systems, team continuity, and customer retention. Almost no pre-close conversation focuses on what happens to the 15–40 software systems a typical $10M–$75M business is running. This gap is expensive. System integration is the operational foundation of post-close performance: if the ERP does not connect to the buyer's reporting infrastructure, the monthly financial package cannot be produced. If payroll is not transitioned cleanly, employees do not get paid on time. If the CRM migration loses historical records, the sales team loses five years of relationship context.
Dollar math: A $25M revenue company running NetSuite for ERP, Salesforce for CRM, and ADP for payroll. A PE buyer with a Sage Intacct + HubSpot + Paychex standard platform needs to migrate all three. ERP migration: $100,000–$200,000 in consulting and implementation. CRM migration: $40,000–$80,000 in data migration and re-training. Payroll transition: $15,000–$30,000 in parallel processing and configuration. Total: $155,000–$310,000, none of which was in the seller's financial model.
The three post-close technology outcomes
Not every post-close technology situation ends in full migration. There are three common outcomes, each with different cost, timeline, and complexity profiles.
Three Post-Close Technology Integration Models
Scroll to see more →
PE sponsors with a standardized technology platform across portfolio companies achieve 20–35% lower post-close integration cost than those managing bespoke integrations on a deal-by-deal basis.
A food distribution company was acquired by a PE sponsor whose three other portfolio companies all ran NetSuite. The target ran QuickBooks Enterprise with 12 years of historical data and 47 custom reports. The buyer chose full migration to NetSuite. The migration took 140 days, cost $185,000 in implementation fees, and required three months of parallel operation during which the CFO ran both systems simultaneously. The total cost including internal time was approximately $240,000, $10,000 more than the original estimate because the custom reports were not fully documented before the engagement.
ERP systems: NetSuite, QuickBooks, Sage, what migration actually costs
ERP migration is typically the most expensive and time-consuming technology integration in a post-close scenario. The cost range is wide because complexity varies enormously: a QuickBooks migration to NetSuite for a 30-person professional services firm is fundamentally different from a Sage 100 migration to NetSuite for a 150-person manufacturer with multi-warehouse inventory, custom manufacturing BOMs, and EDI integrations.
ERP Migration Cost by System and Complexity
Scroll to see more →
The hidden cost driver in ERP migration is always undocumented customizations. Every business that has run an ERP for more than five years has accumulated custom reports, custom fields, custom workflows, and sometimes custom code that the current team treats as normal but that no one has formally documented. These customizations need to be inventoried before migration begins, not discovered during it.
Before close, document every ERP customization: custom fields, custom reports, custom integrations to other systems, and any third-party modules or connectors. A 10-page system inventory document costs $5,000–$15,000 in internal or consulting time to produce. Discovering those customizations mid-migration, when an ERP consultant is billing $250–$400/hour, costs 5–10x more.
Working through this yourself?
Kolton works directly with founders on M&A readiness, deal structure, and AI implementation — one advisor, not a team of generalists.
Schedule a conversation →CRM migration: data, field mapping, and historical record preservation
CRM migration is less expensive than ERP migration but carries its own risks, primarily around historical data quality, field mapping between platforms, and sales team adoption during the transition period.
60–90 days
typical CRM migration timeline for mid-complexity implementations
$40K–$80K
typical CRM migration cost for $10M–$50M company
5 years
minimum historical CRM data that should be preserved in any migration
The most common CRM migration scenario in middle market PE acquisitions: Salesforce to HubSpot, or HubSpot to Salesforce, depending on the buyer's platform standard. The technical migration, exporting contacts, companies, deals, and activity history; field mapping to the new platform; importing and deduplicating records, which is straightforward with the right implementation partner.
CRM Migration Risk Areas
Payroll and HR systems: ADP, Paychex, Gusto, parallel payroll and transition risk
Payroll transition is the highest-stakes technology migration in a post-close integration, not because it is the most expensive, but because failure has immediate, visible consequences: employees do not get paid correctly. This makes payroll transitions uniquely sensitive and requires more careful planning than any other system.
Step 1: System audit, document current payroll platform, pay frequency, employee classifications, benefits integrations, and state tax registrations
Step 2: Gap analysis, identify all differences between current platform and target platform: pay codes, deduction types, benefit elections, direct deposit configurations
Step 3: Parallel run, process at least one full payroll cycle on both old and new platform simultaneously; reconcile outputs before switching
Step 4: Employee data migration, transfer all employee records, YTD earnings, tax withholdings, and direct deposit information
Step 5: Benefits integration, reconnect health insurance, 401(k), and other benefits to the new payroll platform
Step 6: Go-live and validation, run first live payroll; compare to last parallel run; have HR team available for same-day issue resolution
Payroll Platform Migration Comparison
Scroll to see more →
The parallel payroll run is not optional. Running one full payroll cycle on both platforms before cutting over is the single most important risk mitigation step in a payroll migration. The cost of a parallel run is approximately two to four hours of HR and payroll team time plus any additional platform fees. The cost of a payroll error affecting 50 employees is measured in trust, legal exposure, and emergency remediation, typically 10–50x the cost of the parallel run.
What to document before close: the system inventory
The single most high-value action a founder can take to reduce post-close integration cost and delay is producing a comprehensive system inventory before the transaction closes. This document becomes part of the diligence data room and the post-close integration plan.
System Inventory Document Structure
The shadow systems section is the most important and most overlooked. In almost every middle market company, someone in finance runs a "master spreadsheet" that reconciles data from two or three systems that do not talk to each other. Someone in operations maintains a tracking database in Excel that gets updated manually every Monday. These shadow systems are often mission-critical, and often unknown to anyone except the person who built them.
Shadow systems and undocumented integrations account for 35–45% of unplanned post-close technology cost, making them the single largest driver of integration budget overruns in middle market transactions.
Integration timeline benchmarks by system type
Post-Close Integration Timeline Benchmarks by System
Scroll to see more →
ERP integration is always last and always delayed for three structural reasons: (1) ERP data is the most complex to migrate, multi-year transaction history, chart of accounts mapping, inventory records, work orders; (2) ERP customizations are rarely fully documented, and discovery during migration adds scope; (3) ERP migration requires parallel operation, running both systems simultaneously, which consumes significant finance team bandwidth. The cost of delayed ERP integration is real: dual data entry across both systems, monthly reconciliation between legacy and new ERP, and financial reporting that cannot be fully consolidated until the migration closes. Budget 30–40% of ERP migration cost as the cost of the delay period.
Common integration failure patterns
Post-Close Integration Failure Patterns
Scroll to see more →
A 90-person distribution company attempted a simultaneous migration of ERP, CRM, and payroll in the 60 days following close. The ERP migration encountered undocumented integrations with three vendor portals that required custom API work. The CRM migration lost 18 months of activity history due to a field mapping error discovered post-migration. The payroll migration completed on time but with three employees receiving incorrect amounts in the first pay cycle. Total unplanned cost: $185,000. Timeline: 9 months to full stabilization instead of 3. Root cause: all three systems started simultaneously with no phasing.
Integration cost estimation and budgeting
System Integration Cost Ranges
Scroll to see more →
What Drives Integration Cost Variation
Rule of thumb for budgeting integration in the deal model: 1–3% of transaction value is a commonly used estimate for systems-heavy businesses (distribution, manufacturing, multi-location services). A $20M transaction in a systems-heavy sector should budget $200,000–$600,000 for technology integration. This is often not included in the initial deal model, which is why post-close integration cost surprises are so common. Include it in the deal model before close, not after.
Common mistakes in post-close technology integration
Assuming the acquirer will handle it. A PE buyer with three other portfolio companies and a standard technology platform has a playbook for integration. But that playbook assumes your systems are documented, your contracts are transferable, and your data is clean. If any of those assumptions are wrong, the timeline slips and the cost escalates, and the cost is typically shared or borne by the target company.
Not documenting system dependencies before close. The database that populates the weekly sales report depends on an SFTP feed from the CRM, which depends on a nightly sync from the ERP. If you do not document this chain, the integration team discovers it when the weekly sales report breaks on Day 14 post-close. That discovery costs time, credibility, and money to diagnose and fix.
Underestimating payroll transition risk. Finance teams with sophisticated ERP migration experience often treat payroll as a simple data migration. It is not, and it is a compliance-critical, employee-visible process with tax, benefits, and garnishment implications that require specialized expertise. Engage a payroll migration specialist, not just a general IT integrator.
The most expensive post-close technology failure is not a failed migration, and it is a data loss event. Historical CRM data, ERP transaction records, and payroll records are not recoverable if they are not properly exported and archived before the migration begins. Before any migration starts, take a full data backup, store it in a separate, non-cloud-dependent location, and verify the backup is complete. This takes one day and costs almost nothing. Not doing it has cost companies their entire historical data record.
Frequently asked questions
Who should own the system inventory process?
The CFO or COO should own it, with support from whoever manages IT (even if that is an outside managed services provider). Engaging an IT consulting firm to conduct a formal system audit typically costs $10,000–$25,000 and produces a deliverable that is useful in diligence, integration planning, and ongoing IT governance, well worth the investment.
How early before close should the system inventory be completed?
Ideally 6–12 months before a planned sale process. At minimum, before the LOI is signed. A system inventory that surfaces a material undocumented integration or a software license that does not transfer in a change of control is much easier to resolve pre-close than post-close.
What if the buyer's standard platform is dramatically different from ours?
This is worth negotiating during the LOI process if system continuity matters to you. Some founders successfully negotiate a 12–18 month transition period before full platform migration, allowing the business to stabilize under new ownership before absorbing the operational disruption of system migration.
Does ERP migration affect working capital calculations?
Yes, and this is an underappreciated risk. ERP migrations often require a cutover period where historical financial data is unavailable, which can affect the accuracy of the working capital true-up calculation at close. Coordinate your ERP migration timeline with your M&A attorney to ensure the working capital peg is calculated before any system cutover.
Research sources
Disclaimer: Financial figures and case studies in this article are illustrative, based on representative middle market assumptions, and are not guarantees of outcome. Statistical references are drawn from cited third-party research; individual transaction and operational results vary based on business characteristics, market conditions, and deal structure. This content is for informational purposes only and does not constitute legal, financial, or investment advice. Consult qualified advisors for guidance specific to your situation.
Explore adjacent topics
