Every major M&A deal has an Integration Management Office (IMO) or Integration Lead. The IMO is responsible for the integration plan, the integration timeline, the integration budget, and ultimately whether the synergies are captured.
IT is typically underrepresented in the IMO. This is a mistake.
The IT integration work — consolidating identity stores, migrating data and applications, unifying the network — is the most technically complex, most time-consuming, and most failure-prone part of any post-merger integration. And it’s the part that most determines whether the Day 1 experience for 5,000 combined employees is smooth or chaotic.
The IMO Structure That Works for IT
The IMO typically has a workstream for each major function: Finance, HR, Operations, Sales, Legal, IT.
The IT workstream should have three sub-teams:
Workstream 1: Identity and Access (highest risk)
- AD / Azure AD consolidation
- M365 tenant migration
- IAM integration
- Service account management
Workstream 2: Applications and Data
- Application migration decisions (migrate / retire / coexist)
- Data migration execution
- SaaS platform consolidation
Workstream 3: Infrastructure and Operations
- Network integration
- Endpoint management
- Security operations unification
- Service desk / help desk integration
The IT Integration Timeline
Most IT integrations follow a compressed timeline:
Day 1 to Day 30: Stabilize
- Get both companies’ users productive immediately
- Ensure email, Teams/Slack, and core business applications work
- Address the critical Day 1 failures
- No major infrastructure changes yet
Day 30 to Day 90: Integrate Identity
- Consolidate to a single identity provider
- Migrate to a single M365 tenant (if applicable)
- Re-establish SSO for all critical applications
Day 90 to Day 180: Integrate Applications
- Begin application migration waves
- Retire duplicate SaaS platforms
- Consolidate data warehouses
Day 180 to Day 365: Consolidate Infrastructure
- Network infrastructure integration
- Data center consolidation
- End of legacy infrastructure life
Year 2: Optimize
- Cloud optimization
- Toolchain simplification
- Security posture improvement
The IT Integration KPIs
The IMO tracks integration KPIs. For IT integration, the right KPIs are:
Stability
- Uptime of critical systems (target: 99.9% during integration)
- Number of P1/P2 incidents in the first 30 days post-close (target: declining)
- Help desk ticket volume vs. baseline (target: return to baseline by Day 90)
Progress
- % of users migrated to consolidated identity platform (target: 100% by Day 60)
- % of applications migrated/retired/consolidated (target: defined per application)
- % of SaaS platforms deduplicated (target: 80% by Day 120)
Synergy Capture
- Annual SaaS cost savings from deduplication (track vs. deal model)
- Annual cloud cost savings from cloud optimization (track vs. deal model)
- IT FTE reduction from integration (track vs. deal model)
Risk
- Security incidents attributable to integration work (target: zero critical incidents)
- Unresolved critical/high security findings post-integration (target: zero)
Why IT Belongs in IMO Leadership
The reason IT is usually underrepresented in the IMO is that IT integration is often viewed as a support function — something that enables the business workstreams but doesn’t have independent business risk.
This is wrong. IT integration failure is a business risk. When the payroll system breaks, that’s a business risk. When the sales team’s CRM stops working, that’s a business risk. When the identity integration fails and 3,000 people can’t log into their applications, that’s a critical business risk.
The IT workstream lead should have a seat at the IMO leadership table — not just report into the IMO, but participate in IMO decisions that affect the integration timeline and the Day 1 experience.
The IMO IT Integration Checklist for Day 1
IT Infrastructure (6 items)
- IT help desk staffed and configured to handle both companies’ users from Day 1
- Both companies’ users can access their primary business applications (email, collaboration, core business app)
- VPN / network connectivity verified for all remote users in both companies
- SSO is working for all primary applications — users are not managing separate passwords for more than 3 systems
- MDM / device management coverage confirmed for all corporate devices in both companies
- IT incident response plan is updated for the merged entity and the response team is staffed
Identity (3 items) 7. Azure AD Connect (or equivalent) is running and syncing both companies’ identity stores 8. All privileged accounts in both environments have MFA enabled 9. Service account password status confirmed — no service account passwords expiring in the next 30 days
Communication (2 items) 10. User communication sent: new credentials, new system URLs, help desk contact information 11. IT escalation path published — both companies’ IT teams know who to call for what
Governance (2 items) 12. IT integration governance (steering committee, escalation path, decision rights) documented and communicated 13. Day 30 IT workstream plan reviewed and approved by IMO