Post-Merger Integration Roadmap Template: Phases, Steps and Milestones
8 min read ยท 2026-10-09
A post-merger integration roadmap template is a plan that shows how two companies become one after a deal closes, phase by phase. It lists what must happen before closing, on Day 1, in the first 100 days and over the following year. Each step has an owner and a milestone.
This template assumes 12 to 18 months. Your timeline depends on deal size and how much you combine. The template below covers that full period in 6 phases. Use it as it is, or change the durations to match your deal.
The roadmap at a glance
Goal: Combine two organizations into one working company, keep customers and key people, and deliver the value the deal was built on. Duration: 12 to 18 months, starting 6 to 8 weeks before the deal closes
Pre-close planning (6 to 8 weeks before closing)
Get ready so that nothing important is decided under pressure on Day 1.
- Set up an Integration Management Office (IMO) with one integration lead and one owner per function.
- Write down the deal thesis: why this deal makes sense and which synergies it should deliver.
- Choose the integration level for each function: keep separate, partly combine or fully combine.
- Set up a clean team for sensitive data, and check with legal counsel what may be shared before closing.
- Draft the Day 1 communication plan for employees, customers, suppliers and investors.
Milestone: The Day 1 plan is signed off by both leadership teams and the IMO is staffed.
Day 1 and first week (1 week)
Close the deal without disrupting customers, payroll or daily operations.
- Send the announcement to all employees at the same time, followed by team meetings with managers.
- Contact key customers and suppliers directly with a named contact person.
- Confirm payroll, banking access, legal entity changes and signing authority.
- Give everyone a list of what changes now and what stays the same for the time being.
Milestone: Every employee has received the announcement, and payroll and customer service run without interruption.
Stabilize (Weeks 2 to 6)
Protect the business while people learn the new structure.
- Confirm the new leadership team and the reporting lines for the top two levels.
- Start retention talks with the people the business cannot afford to lose.
- Track customer issues and complaints weekly to catch early warning signs.
- Run the transition service agreement (TSA) with the seller if the deal includes one.
Milestone: Leadership structure is announced and key-person retention agreements are signed.
Design and quick wins (Weeks 7 to 14)
Turn the integration plan into detailed work plans and deliver the first quick wins.
- Map each synergy to an owner, a target date and a way to measure it.
- Design the target operating model: structure, processes and decision rights.
- Choose which systems to keep for finance, HR, CRM and IT.
- Run a culture assessment through interviews and short surveys in both companies.
- Deliver two or three quick wins, such as cross-selling to shared customers or combining a supplier contract.
Milestone: The Day 100 review is held, with an approved target operating model and a synergy tracker in use.
Integrate operations and systems (Months 4 to 12)
Move people, processes and tools onto the target model.
- Migrate systems in waves, starting with finance and HR, then sales and operations.
- Combine teams and roles according to the new structure.
- Align policies: pay, benefits, travel, security and approval rules.
- Exit the TSA services one by one as your own systems take over.
Milestone: Finance closes the month on one system and all TSA services have ended.
Optimize and close the integration (Months 12 to 18)
Confirm the value was delivered and hand the work back to normal management.
- Compare delivered synergies with the targets set in pre-close planning.
- Run a lessons-learned review with the IMO and function owners.
- Move open items into regular business plans and close the IMO.
Milestone: The final integration report is approved and the IMO is formally closed.
What a post-merger integration roadmap is, and what it is not
A post-merger integration roadmap is a timeline of outcomes. It shows the big phases, the order they happen in and the checkpoints that tell you the integration is on track. Leadership, the board and function heads use it to answer one question: where are we?
It is not the detailed task list. Each function, such as IT, HR or finance, should keep its own detailed work plan. The roadmap sits above those plans and links them together. If your roadmap has more than a few dozen items, it has become a project plan, and people will stop reading it.
A good roadmap answers four things for every phase:
- What we are trying to achieve.
- Who owns it.
- When it should be done.
- How we will know it is done.
How to adapt the template to your deal
Not every merger needs full integration. The first decision is how far you want to combine the two companies. This template assumes 12 to 18 months. Your timeline depends on deal size and how much you combine. A small acquisition kept as a separate brand might only merge finance, legal and HR, so you can shorten or remove several phases. A merger of equals that combines everything will use every phase, and possibly more time.
Go through each function and choose one of three levels. Then delete or shorten the phases that do not apply.
Also adjust the durations to your context. Cross-border deals can need more time for legal entities, local labor rules and payroll. Deals in regulated industries may need regulator approval before certain changes. Ask your legal and HR advisors before you lock in dates.
- Keep separate: the acquired company keeps its own processes. You only connect reporting and controls.
- Partly combine: you share some functions, such as procurement or IT support, but keep separate sales teams or brands.
- Fully combine: one structure, one set of systems, one way of working.
Who owns what: the Integration Management Office
The Integration Management Office, or IMO, is the small team that runs the integration. It does not do all the work. It sets the rhythm, tracks progress, removes blockers and makes sure each function moves at the same pace as the others. A typical setup looks like this:
Hold a weekly IMO meeting during the first 100 days, then move to every two weeks. Keep the format short: status by function, risks, decisions needed. Review the roadmap with the executive sponsor once a month.
- Executive sponsor: a senior leader who makes final decisions and unblocks issues across functions.
- Integration lead: runs the IMO full time and owns the roadmap.
- Function leads: one per area, such as finance, HR, IT, sales, operations and legal. They own their part of the plan.
- Communications lead: owns all internal and external messages, so people hear one consistent story.
- Synergy owner: tracks cost and revenue synergies against the targets.
Communication: the part of the roadmap people forget
Integrations can stall on people issues as much as on systems. When employees do not know what is happening, they fill the silence with rumors, and good people start answering recruiters. Customers who hear nothing may assume service will get worse.
Build communication into every phase of the roadmap, not as a side task. Plan who hears what, from whom and when. Managers should hear news shortly before their teams, so they can answer questions.
- Before closing: prepare messages and FAQs, and train managers to answer common questions.
- Day 1: one announcement for everyone, then team meetings and direct calls to key customers.
- Rest of the first 100 days (weeks 2 to 14): regular updates, even when there is little news. Say what is decided and what is still open.
- Months 4 to 18: share progress at milestones and explain changes before they happen.
How to track progress and synergies
A roadmap only works if you can see where you are. Give every milestone a clear pass or fail test. "IT integration progressing" is not a milestone. "All employees use one email domain" is.
For synergies, keep a simple tracker with one line per synergy: description, owner, target value, target date, status. Review it at every IMO meeting. Separate synergies that are only planned from those that are confirmed in the accounts, so leadership sees the real picture.
You can build this roadmap in a spreadsheet, a slide deck or a project tool such as Jira or Notion. What matters is that one version exists, that everyone looks at the same one, and that someone updates it every week.
Common mistakes to avoid
- Starting to plan only after the deal closes, so plan Day 1 at least 6 weeks before closing.
- Sharing sensitive data such as prices or customer lists before closing, so use a clean team and check with legal counsel first.
- Trying to integrate everything at once, so choose an integration level per function and migrate systems in waves.
- Ignoring culture until problems appear, so run a culture assessment in the first 100 days and act on what it shows.
- Letting retention slip while leaders focus on systems, so sign key-person agreements during the stabilize phase.
- Never closing the IMO, so set a clear end date and move open work into normal business plans.
Frequently asked questions
What should a post-merger integration roadmap template include?
It should include the phases of the integration, the steps in each phase, an owner for each step and a milestone that shows when the phase is done. This template covers pre-close planning, Day 1, stabilization, design and quick wins, systems and operations integration, and a closing review. Add a synergy tracker and a communication plan alongside it.
How long does post-merger integration take?
This template assumes 12 to 18 months. Your timeline depends on deal size and how much you combine. A small acquisition that stays mostly separate needs fewer phases. A full merger of two large companies, with many systems and countries, can need more time.
What is a 100-day integration plan?
A 100-day plan covers the first part of the integration after closing. In this template, it includes three phases: Day 1, Stabilize, and Design and quick wins. It focuses on keeping the business running, confirming leadership, keeping key people and customers, and designing the target operating model. It ends with the Day 100 review, where leadership approves the plan for the rest of the integration.
Who should own the integration roadmap?
The integration lead inside the Integration Management Office should own the roadmap and keep it updated. Function leads own their own parts of it, and an executive sponsor makes final decisions. One owner and one shared version avoid conflicting plans.