A post merger integration checklist is a phased task list that tells the combined company what has to happen, who owns it and when, from the weeks before close through Day 100 and beyond. It covers leadership, people, finance, IT systems, CRM, the website and customers, so no task falls between two teams.
Closing itself is taking longer: about 30% of the 50 largest deals were delayed by roughly six months, mostly by regulators and other outside factors (McKinsey, 2024). The time between signing and close is when Day 1 gets prepared. After close, much of the day-to-day friction for B2B companies sits in systems: two CRMs, two websites and two versions of the pipeline report. That’s the part our m&a systems integration team works on, and it’s where this checklist goes deeper than most.
Below you’ll find the full checklist, split by phase and by workstream, plus a dedicated IT section. Copy it into your own tracker or grab the ready-made version.
Download the free template: Google Sheet / XLS
What is a post merger integration checklist?
It’s the working document an integration team uses to turn the deal thesis into dated tasks with named owners. The deal model says what the combined company should achieve; the checklist says who changes which system, contract or process to get there, and by when. You’ll also see it called a post acquisition integration checklist, a merger and acquisition integration checklist, a post merger checklist or, for smaller deals, a merging two companies checklist. The content is the same.
Start using it before the deal closes. Most of the Day 1 risks (payroll, system access, customer notices, change-of-control clauses) have to be prepared while the two companies still operate under clean-team rules. After close, the checklist becomes the agenda for the integration management office (IMO) until the combined company runs on one set of processes and one stack, usually somewhere between Day 100 and the end of Year 1.
The template follows four phases, each with a different goal:
- Pre-close: plan, inventory both companies and protect Day 1.
- Day 1: keep the business running and tell people what’s changing.
- First 30 days: name owners, confirm target systems and build one view of the pipeline.
- Days 31-100: consolidate CRM, website, tools and reporting, then check synergy progress.
Work after Day 100 (retiring the last duplicate systems, governance, the Year 1 review) runs from the same list, just at a slower cadence.
Post acquisition integration checklist by phase
Use the four tables in order. Owners are typical roles; swap in names before the first IMO meeting, and add a due date column if you’re tracking in a spreadsheet.
Pre-close
| Task | Owner | Done |
| Set up the IMO and name one integration lead with decision rights | CEO / deal sponsor | ☐ |
| Turn the synergy case into targets with owners and dates | CFO | ☐ |
| Inventory both companies’ systems: CRM, marketing automation, ERP, website, domains, analytics | CIO / RevOps lead | ☐ |
| Agree clean-team rules for what data can be shared before close | Legal | ☐ |
| Decide the Day 1 leadership structure and reporting lines | CEO / HR | ☐ |
| Identify key people and prepare retention offers | HR | ☐ |
| Review contracts with change-of-control or assignment clauses | Legal / Finance | ☐ |
| Draft Day 1 messages for employees, customers and partners | Communications lead | ☐ |
| List the systems that stay untouched on Day 1 | CIO | ☐ |
Day 1
| Task | Owner | Done |
| Announce internally first, then externally; leaders run team sessions | CEO | ☐ |
| Send customer and partner notices with one named contact each | Sales / Customer success | ☐ |
| Confirm payroll, benefits and email work for every employee | HR / IT | ☐ |
| Open cross-company access to chat, shared drives and calendars, least privilege only | IT / Security | ☐ |
| Add “now part of” messaging to the acquired website; leave URLs unchanged | Marketing | ☐ |
| Freeze CRM field, pipeline and pricing changes until owners are named | RevOps lead | ☐ |
| Publish signing authority and spend approval rules | Finance / Legal | ☐ |
| Open the integration issue log and daily stand-up | Integration lead | ☐ |
First 30 days
| Task | Owner | Done |
| Build a combined pipeline report, even if it pulls from two CRMs | RevOps lead | ☐ |
| Choose the target CRM and approve the migration plan | RevOps lead / CIO | ☐ |
| Map overlapping accounts and give each one a single owner | Sales leadership | ☐ |
| Finalize and announce the top two layers of the org chart | CEO / HR | ☐ |
| Map the chart of accounts and align the month-end close calendar | Finance | ☐ |
| Run a security review: MFA, offboarding, vendor access on both sides | Security | ☐ |
| Decide which website and domain survive and how redirects will work | Marketing / Web | ☐ |
| Baseline the KPIs the synergy case depends on | CFO / IMO | ☐ |
| Run a first employee pulse survey | HR | ☐ |
Days 31-100
| Task | Owner | Done |
| Migrate CRM data: dedupe accounts and contacts, map deal stages, keep history | RevOps lead | ☐ |
| Unify lead routing, lifecycle stages and attribution rules | RevOps / Marketing ops | ☐ |
| Consolidate websites with a full 301 redirect map and content migration | Web / SEO | ☐ |
| Merge analytics, tag management and consent settings | Marketing ops | ☐ |
| Harmonize pricing, packaging and contract templates | Sales / Legal | ☐ |
| Align sales compensation and quotas for the next period | Sales / HR | ☐ |
| Retire duplicate tools and cancel unused licenses | IT / Procurement | ☐ |
| Launch one board and management reporting pack | CFO | ☐ |
| Hold the Day 100 synergy review and re-baseline the plan | IMO / CFO | ☐ |
Merger integration checklist by workstream
The phase tables tell you when. This view tells each workstream lead what they’re accountable for across the whole integration, which is how most IMOs run their weekly reviews. Give every workstream one lead, a short status each week and a clear escalation path to the integration lead.
| Workstream | What to check | Typical owner | Risk if it slips |
| Leadership and communication | Decision rights and governance agreed; one integration narrative; cadence for all-hands and manager briefings | CEO / Integration lead | Rumors fill the gap and key people start interviewing |
| People and HR | Org design, retention offers, payroll and benefits, policy alignment, culture pulse checks | CHRO | Attrition among the people who hold customer relationships |
| Finance | Chart of accounts mapping, close calendar, banking, approval limits, synergy tracking | CFO | Board numbers nobody trusts, synergies nobody can prove |
| IT systems and data | Systems inventory, access and security, data ownership, tool and license rationalization | CIO / IT lead | Security gaps, duplicate spend, data no one can join |
| CRM and revenue operations | Target CRM, data migration, pipeline stages, routing, attribution, combined forecast | RevOps lead | Two forecasts, double-counted pipeline, reps working the same accounts |
| Website and brand | Brand architecture, domain strategy, 301 redirects, analytics and consent, form-to-CRM paths | CMO / Web lead | Lost organic traffic and prospects who can’t tell which company to contact |
| Customers | Account mapping, notices, contract terms, support routing, cross-sell plan | CRO / Customer success | Churn during the quiet weeks after the announcement |
Keep the company integration checklist in one place. A shared sheet with phase, workstream, owner, due date and status columns lets the IMO filter by either view without maintaining two lists.
Post merger IT integration checklist
IT carries more of the deal value than its share of the integration budget suggests. In a Deloitte analysis of 30 transactions, IT was the main driver of more than half the synergies captured (Deloitte, 2023). For B2B companies, the systems that touch revenue (CRM, marketing automation, the website and reporting) decide whether the combined go-to-market team can sell from Day 31 or spends the quarter reconciling spreadsheets. Here’s what to cover in IT integration for M&A.
Systems inventory
List every system on both sides before you decide anything. For each one, record the owner, the contract end date, the number of users, what it connects to and which team would feel it if it went down.
- CRM, marketing automation, CPQ and billing
- ERP and finance tools
- Websites, domains, DNS, hosting and CMS
- Analytics, tag management and consent tools
- Data warehouse, BI dashboards and spreadsheets that act as systems
Access and security
On Day 1, give people access to what they need to collaborate and nothing more. Enforce MFA on both sides, align offboarding so departing employees lose access the same day, and review admin rights and third-party integrations in the acquired company’s tools. Shared logins in marketing and web tools are a common blind spot.
Data migration
Decide which system is the source of truth for each object (accounts, contacts, deals, products, invoices) before moving records. Clean before you migrate: dedupe, standardize country and industry values, and archive records nobody has touched in years. Run a test migration on a subset, check the reports your leadership uses, then schedule the cutover outside quarter-end.
CRM consolidation
Pick the target CRM by how well it fits the combined sales motion and reporting needs. Then map pipeline stages and definitions, rebuild routing and assignment rules, merge overlapping accounts with one owner, carry over activity history and rebuild the forecast in one place. Until the cutover, a combined pipeline report pulled from both CRMs keeps leadership looking at one number.
Website consolidation
Decide the brand architecture first: one brand, an endorsed brand (“part of”) or separate brands. If the acquired site is retired, build a URL-by-URL 301 redirect map, migrate the content that ranks or converts, move forms so they still write to the right CRM, and merge analytics before launch. Monitor rankings, crawl errors and form submissions for at least eight weeks after the switch.
How DevriX helps with the systems side
DevriX consolidates CRMs, websites, domains, tracking and reporting into one operating model on a 100-day plan tied to the synergy case. You get a Day 1 systems assessment, an integration roadmap with named owners, a merged CRM and web presence, and unified reporting. Recent work includes merging Spotlio’s EU and US platforms into one with SEO preserved and moving Unblu from HubSpot to Salesforce in five days. For PE-backed add-ons and carve-outs, the same work runs as part of our post merger integration consulting.
Book a free 30-minute PMI Readiness Call
Common post-merger integration mistakes
- Leaving synergy targets in the deal model. If a synergy has no owner and no date on the checklist, nobody is working on it. Assign each one before close.
- Changing too much on Day 1. Day 1 is for stability: payroll runs, customers get answers, systems stay up. Save migrations for when owners and target systems are confirmed.
- Running two CRMs past Day 100. Two pipelines mean two forecasts, reps chasing the same accounts and a board pack stitched together by hand. Set a cutover date in the first 30 days.
- Migrating dirty data. Duplicates and inconsistent fields move straight into the new CRM and break routing and reporting. Clean and dedupe first.
- Retiring a website without a redirect map. Pages that ranked for years drop out of search, and inbound leads drop with them. Map every URL that has traffic or backlinks.
- Going quiet with customers. The weeks after an announcement are when competitors call your accounts. Give every overlapping account one owner and one message early.
Post merger integration checklist XLS and PDF
The downloadable template holds everything above in a format your IMO can run from week one.
- Google Sheet / XLS: three tabs (by phase, by workstream, IT integration) with columns for task, owner, due date, status and notes. Filter by owner for weekly reviews or by phase for steering committee updates.
- PDF: the same checklist laid out for printing or adding to a board or integration kickoff pack.
Before you share it, delete the tasks that don’t apply to your deal, add the ones specific to your industry and replace the role names with real people. A checklist where every row says “IT” or “HR” doesn’t get done.
Download the free template: Google Sheet / XLS | PDF
FAQ
What should a merger integration checklist include?
Tasks grouped by phase (pre-close, Day 1, first 30 days, days 31-100) and by workstream (leadership, people, finance, IT and data, CRM and RevOps, website and brand, customers), each with a named owner, a due date and a status. It should also list the synergy targets so progress can be checked at Day 100.
Is there a post merger integration checklist XLS or PDF template?
Yes. The free template on this page comes as a Google Sheet you can download as XLS and as a PDF. Both include the phase, workstream and IT integration checklists.
What is post merger IT integration?
It’s the work of combining both companies’ technology: systems inventory, access and security, data migration, CRM consolidation, website and domain consolidation, and retiring duplicate tools. For B2B companies, the revenue systems usually come first because they affect selling and reporting right away.
How long does post-merger integration take?
Day 1 readiness and core consolidation usually fit within the first 100 days. Full integration of reporting, governance and the last legacy systems tends to run to the end of Year 1, longer for large or cross-border deals.
Who owns the post acquisition checklist?
The integration lead, working through the IMO, owns the list as a whole. Each workstream lead owns their rows, and the CFO owns the synergy targets the list is built to deliver.
How is an integration planning checklist different from an integration plan?
The plan sets the goals, structure, budget and timeline. The integration planning checklist is the task-level view of that plan that teams update every week.
Next steps
A post merger integration checklist only works when every row has an owner and a date, and when the IT, CRM and website rows get the same attention as the org chart. Start it before close, run Day 1 for stability, and use the first 100 days to get to one pipeline, one website and one set of numbers.
Download the free template: Google Sheet / XLS | PDF. If your systems are where the integration is stuck, book a free 30-minute PMI Readiness Call with DevriX.