Bridging The Post-Close Gap: A CIO’s Blueprint for M&A Integration and Crisis Control
M&A success is decided in post-close execution. In this exclusive preview of his upcoming book Make IT Work: An IT Playbook for Mergers and Acquisitions, CIO Jason James covers repeatable playbooks, quick wins, and handling outages and human crises.
"Technology is the easy part. People are the hard part. Successful M&A integration is fundamentally a human challenge wrapped in a technical package."
A successful integration of two companies can feel almost magical. It’s like thinking an organization couldn’t match its original form, only to discover the combined entity is even better.
Think of it like when Steve Perry left Journey. Many assumed the band was done, but they found Arnel Pineda on YouTube, a frontman whose voice matched Perry’s, and kept the legacy thriving. When M&A integration is executed well, it creates a combined organization that far exceeds the sum of its parts.
Getting there requires technical discipline, strategic speed, and human empathy. The following article is adapted from my upcoming book, Make IT Work: An IT Playbook for Mergers and Acquisitions, offering a preview on building a scalable integration framework, securing early wins, and managing crises when things inevitably go sideways.
"Try never to be the smartest person in the room. And if you are, I suggest you invite smarter people, or find a different room." — Michael Dell, Founder and CEO, Dell Technologies
Codifying the strategy: The integration framework
The single most critical document in your M&A toolkit is a living, repeatable playbook that codifies lessons learned from past deals into a standardized process.
A battle-tested playbook directly supports the investment thesis. When a private equity sponsor or board watches you integrate a bolt-on acquisition in 60 days because your framework existed, IT stops being overhead and starts driving value.
Organize your integration framework into five phases:
- Pre-Close Preparation: Securing environments, auditing data centers, and establishing risk baselines.
- Day One Activities: Access control, domain transfers, and immediate security backups.
- 30-Day Milestones: Rapid network connectivity, identity baselines, and quick wins.
- 60-Day Milestones: Core system migrations and initial application alignment.
- 90-Day Milestones: Complete handoff, decommissioning legacy tools, and disbanding support teams.
Your playbook needs recipe-level detail specifying exact tasks, owners, dependencies, and acceptance criteria.
Pro tip: Create standardized templates for due diligence checklists, status reports, synergy tracking, risk registers, and communication plans before close. Deploying ready templates saves weeks of administrative ramp-up.
Frontline support: The integration SWAT team
For the first 90 days, establish a dedicated Integration SWAT Team, a cross-functional group of five to seven top performers (including an infrastructure engineer, application analyst, security analyst, help desk coordinator, and project coordinator).
Dedicated Channels: Create a friendly Slack/Teams channel (e.g., #Welcome-Aboard) and a shared inbox.
Remove Friction: If compliance or ticketing processes slow down new employees, have the SWAT team log tickets behind the scenes.
High Tech Meets High Touch: Staff this team with your most empathetic engineers. Technical brilliance paired with a bad attitude does more harm than a delayed migration.
High-impact workstreams: quick wins, plumbing, and data
Build momentum in the first 30 days with visible quick wins: unified email and calendar, single sign-on (SSO), unified collaboration tools, and a clean org chart.
Email migration is the primary psychological win
Email migration is the most visible win. Assigning employees an address on the acquiring company’s domain signals that it’s one unified company. Pilot test migrations first, keep auto-forwarding active for 90 days, and handle executive pushback by setting legacy emails as aliases while enforcing the new primary domain.
Network Plumbing & Application Rationalization
Network connectivity is a Week One requirement. Whether using cloud VPC peering or VPN tunnels, downstream migration cannot proceed until the networks can communicate.
Watch Out for IP Conflicts: Overlapping private IP ranges cause major integration delays. Plan for them during due diligence.
Application Rationalization: Avoid retiring tools in the first 90 days. Focus initial efforts on adding value. Save tool rationalization for the second half, guided strictly by cost, usage, functionality, and security data.
Data migration: The hidden beast
Moving data is easy; transforming schemas, reconciling duplicates, and validating quality is hard. Double your initial data migration timeline and add 25% for unknowns. Never migrate production-to-production directly; always stage and validate end-to-end in a test environment first.
Operational incident control: handling crises
"Always look for the fool in the deal. If you don’t find one, it’s you." — Mark Cuban, Investor and Entrepreneur
Despite planning, things go wrong, from Sev1 outages to canceled deals, such as Adobe’s abandoned $20B acquisition of Figma after 15 months of planning. Respond to operational issues using a structured framework.
Incident severity framework
Severity 1: Business impact
Criteria: Revenue is affected, a customer-facing platform is down, or a data breach occurs.
Immediate Action: All-hands response, executive notification within 30 minutes, and override all other integration work.
Severity 2: Significant disruption
Criteria: A core internal system is down, or a critical workstream is blocked.
Immediate Action: Same-day response and notification to workstream leads.
Severity 3: Minor issue
Criteria: An isolated end-user issue or non-critical secondary tool is offline.
Immediate Action: Manage through normal help desk queues and track in the integration backlog.
Pro tip: Avoid treating every issue as Severity 1, which burns out teams. Reserve maximum response for genuine crises.
The 4-hour rollback threshold
When a migration stalls, pre-defined criteria remove emotion:
Fix Forward: Resolve within 4 hours if there is no business impact.
Roll Back: Revert if unresolved after 4 hours or if actively impacting business operations.
A controlled rollback costs a single weekend, and yet pushing forward with a broken migration can cost five days of lost productivity.
The human factor: The ultimate metric
The hardest crises during an M&A integration are human: political friction, key resignations, and cultural pushback, among others.
Mergers and acquisitions are human challenges wrapped in a technical package. When CIOs realize this and proceed accordingly, they build lasting trust and successful organizations.
Jason James is Chief Information Officer (CIO) at Aptos, a leader in retail technology solutions, where he oversees the company's ever-evolving digital landscape and translates the company’s vision into an actionable IT roadmap. He has over two decades of leadership experience in SaaS, cybersecurity, IT infrastructure, and digital transformation. Before joining Aptos, Jason was CIO at several high-growth software and data analytics organizations within the healthcare sector. Earlier in his career, Jason held executive-level IT roles at the supply chain optimization provider, Servigistics (now PTC), the data intelligence firm PRGX, and internet service provider EarthLink. He is the author of Make IT Work: An IT Playbook for Mergers and Acquisitions.
If this caught your attention, that’s not accidental.
The best editorial systems don’t happen by accident. Outlever builds them.
