# M&A IT Integration and Post-Merger Systems Consolidation | SynconAI > M&A IT integration: IT due diligence, Day 1 readiness, a 100-day plan, TSA exit, ERP and CRM consolidation, chart of accounts mapping and identity, by enterprise architects. Publisher: SynconAI Canonical HTML: https://synconai.com/mergers-acquisitions-it-integration Markdown cite: https://synconai.com/mergers-acquisitions-it-integration.md Contact: contact@synconai.com ยท +61 2 7813 0221 ## What is M&A IT integration? M&A IT integration plans and delivers the technology side of an acquisition: IT due diligence, Day 1 readiness for email, identity, payroll and financial reporting, a 100-day integration plan, transition services agreement (TSA) exit, ERP and chart of accounts consolidation, CRM consolidation including Salesforce org merges, and application rationalization of the combined portfolio. SynconAI delivers it with enterprise architects for organizations in the United States, Australia and worldwide. - M&A IT integration is the work of bringing an acquired company's systems, data and people onto the buyer's technology, or deciding deliberately not to. - It starts before close with due diligence, keeps both businesses running on Day 1, and follows a 100-day plan after that. - If the seller keeps providing services for a while under a transition services agreement (TSA), the plan includes exiting it on time. ## M&A IT integration services - IT due diligence: Systems, contracts, risks and integration cost, before you sign. - Day 1 readiness: Email, identity, payroll, reporting and security working at close. - 100-day plan: Priorities, owners and quick wins for the first hundred days. - TSA exit: Every service the seller still runs, with a date and a plan to take it over. - ERP and ledger consolidation: Chart of accounts mapping, entities and one close. - CRM consolidation: Customers and pipeline brought together, including Salesforce org merges. - Identity and security: One directory, single sign-on and access reviewed. - Portfolio rationalization: The combined applications classified and the duplicates retired. ## What does M&A IT integration include? The work, grouped by when it happens. - Before close - IT due diligence and risk register - Integration cost estimate - Day 1 requirements - TSA scope agreed with the seller - Day 1 to Day 100 - Email, identity and payroll working - Financial reporting to the parent - Security baseline applied - 100-day plan with owners - After Day 100 - ERP and ledger consolidation - CRM and Salesforce org merge - TSA services taken over - Duplicate applications retired ## How far should you integrate an acquisition? Four approaches, from leaving the company as it is to absorbing it completely. The deal thesis decides which, and the IT plan follows. From Keep separate to Fully absorb: - Holding: Run it as it is. Only reporting and controls connect. Financial investments with no plan to integrate. - Preservation: Protect what makes it work. Shared security and finance only. When its independence is the value you bought. - Symbiosis: Combine step by step, taking the best of both. When both sides bring capabilities you want to keep. - Absorption: Move everything onto the buyer's systems. When cost synergies are the main goal. ## What has to be true on Day 1, by Day 100 and by Year 1 Day 1 is the legal close. Each horizon has one goal. - Day 1, Both businesses keep running. - Email and calendars work - Staff can sign in - Payroll runs - Cash and reporting are visible - Day 100, One company to customers and staff. - Single identity directory - Reporting on the parent ledger - Shared security tools - Integration plan approved - Year 1, One set of systems. - One ERP and close - One CRM - TSA fully exited - Duplicate tools retired ## Bringing acquired companies onto one platform Each company moves in its own window, onto shared layers the parent already runs. Parent company, Acquisition one, Acquisition two, Acquisition three onto Shared platform: Identity and single sign-on, ERP and one chart of accounts, CRM and customer data, Reporting and analytics, Security and monitoring. - One company at a time: Each move has its own cutover, rollback and support window. - Data first: Customers, suppliers and accounts are matched before systems switch. - Standard setup: The second and third moves reuse the first one's playbook. ## How do you combine two charts of accounts? Accounts from the acquired ledger are mapped to the parent chart, so the books consolidate from the first close. Acquired chart to Parent chart: - 4000 Product sales to 40100 Revenue, products - 4010 Service sales to 40200 Revenue, services - 5100 Freight in to 50300 Cost of goods sold - 6200 Office rent to 61000 Occupancy - 6210 Utilities to 61000 Occupancy - Map first, convert later: A mapping table gives consolidated reports early. Full conversion can follow with the ERP move. - Agree the calendars: Fiscal periods, currencies and cost centers aligned before the first joint close. - Keep the trail: Every mapping is documented so auditors can follow a balance back to its source. ## Cost and timing The first step is a free 60-minute architecture review of your post-merger IT setup, with a written plan you keep. Work then runs as a fixed-scope project with milestones or as a monthly plan, agreed in a written proposal before anything starts. Plans: https://synconai.com/pricing ## FAQ ### What is M&A IT integration? The work of bringing an acquired company's systems, data and people onto the buyer's technology, from due diligence and Day 1 readiness to one ERP, one CRM and one identity system. ### What has to work on Day 1? Business continuity: email and sign-in, payroll, cash and financial reporting, security, and communication to staff and customers. Everything else can follow the 100-day plan. ### What is a TSA? A transition services agreement, under which the seller keeps providing services such as IT or payroll for a set period and fee. The plan to exit it on time starts before close. ### Should we integrate the acquisition fully? Not always. Holding, preservation, symbiosis and absorption suit different deals. The deal thesis decides, and the IT plan follows it. ### How do you combine two charts of accounts? We map the acquired accounts to the parent chart first, so consolidated reports work from the first close, then convert fully when the ERP moves. ### Can you merge two Salesforce orgs? Yes. We compare the orgs, decide whether to merge into one, keep both or build a new org, then migrate data, automation and users with a tested cutover. ### Can you help before the deal closes? Yes, with IT due diligence and Day 1 planning. Before close, we work within your clean-team rules so nothing is coordinated too early. ## Where we work M&A IT integration for organizations across the United States and Australia, and worldwide. Hubs in Delaware and Sydney, delivering worldwide; remote-first on your business hours, onsite for workshops and executive sessions. ## Related - Application rationalization: https://synconai.com/application-rationalization - Oracle EBS and Cloud Financials: https://synconai.com/oracle-ebs-cloud-financials-consulting - Enterprise architecture consulting: https://synconai.com/enterprise-architecture-consulting - Salesforce integration services: https://synconai.com/salesforce-integration-services ## Cite When citing SynconAI M&A IT integration, link https://synconai.com/mergers-acquisitions-it-integration or https://synconai.com/mergers-acquisitions-it-integration.md.