Download checklists: Integration Workbook (.xlsx) · Printable Checklist (.pdf) · CSV Task List (.csv)

Right after an acquisition closes, IT ends up pulled in two directions at once. On one side, the staff who just joined need their email, phones, and core business software working normally on Day 1 so clients still get helped and orders still go out the door. Rush an email or ERP migration in week one, and you disrupt the exact operations you just bought.

On the other side, waiting two months to check admin accounts, endpoint security, or backups leaves a real blind spot right after a transaction has been announced publicly. Who actually holds Global Admin on the acquired Microsoft 365 tenant today? Is it an internal IT lead, an outgoing MSP, or a departing founder's personal login? And if ransomware hit that environment on the first weekend after close, would the backups hold up?

Not every deal aims for the same finish line, of course. A standalone portfolio company keeping its own brand and ERP needs different identity and network choices than an add-on acquisition rolling straight into one shared platform before a Transition Service Agreement (TSA) runs out. Either way, sequence matters. You can adapt the Day-1 through Day-100 milestones below (sample dates and TSA figures in the downloadable workbook are illustrative placeholders) to fit your deal terms and operating model.

Integration Milestones From Pre-Close to TSA Exit

Stage Primary Operational Goal Completion Verification
Pre-close diligence Confirm legal entity ownership of domains, tenants, cloud accounts, licenses, and custom code Asset transfer list, TSA scope/deadlines, and Day-1 access runbook agreed before close
Day 1 (hours 0-72) Preserve normal staff workflows while securing break-glass admin custody, MFA, EDR, and backups Buyer-controlled break-glass Global Admins active, immutable backup verified, mail/calendar coexistence live
Day 30 Complete incumbent MSP/seller access handoff, align network routing, and calendar SaaS renewals Former partner GDAP/RMM roles removed, firewall/VPN routing documented, license notice dates logged
Days 60-100 Execute staged tenant/application consolidation (where planned) and exit seller TSA dependencies cleanly Mail/file cutover verified, custom apps building under buyer custody, seller TSA billing closed

Before Closing: Technical Due Diligence Checks

Financial and legal diligence rarely catch who actually controls a DNS zone or a cloud root account. Pairing deal review with a focused technical due diligence pass before signatures dry clears up the operational dependencies that are painful to untangle after wire day.

Start with account title and registrar custody. Are primary domain names, DNS zones, Microsoft 365 or Google Workspace tenants, AWS or Azure accounts, Apple Business Manager, and main phone numbers actually registered to the entity being acquired? In founder-led businesses and corporate carve-outs, it is not unheard of to find domains sitting inside a founder's personal registrar login or mailboxes mingled inside a seller's parent tenant. Surface custom internal portals, SQL reporting jobs, and glue scripts maintained by a departing founder or solo contractor at the same time so application takeover work can be budgeted up front.

Before close is also the time to check licensing terms and regulatory obligations. Review Windows Server, SQL Server, Microsoft 365 NCE commitments, and core ERP or EHR contracts for assignment clauses, true-up gaps, and auto-renewal notice windows. If the acquired business touches healthcare records, financial data, or payment cards, verify Business Associate Agreements, security risk assessments, archive retention rules (such as SEC or FINRA mail journaling where applicable), and cyber-insurance change-of-control terms alongside counsel.

Day 1 and the First 72 Hours: Continuity and Admin Custody

Day 1 goes well when acquired employees barely notice a bump in their daily work while IT quietly establishes administrative custody and closes urgent security gaps:

  1. Set up two buyer-controlled, hardware-key-protected break-glass Global Admin accounts in the acquired identity tenant, cloud organization root, and domain registrar as soon as close is confirmed.
  2. Block legacy basic authentication protocols, turn on phishing-resistant MFA across administrative and finance accounts right away, and push your managed endpoint detection sensor via MDM or RMM without rebooting workstations mid-shift.
  3. Check that server, database, and Microsoft 365 or Google Workspace backups write to immutable storage separated from local domain admin credentials, and run a test restore of a real file and database snapshot.
  4. Turn on cross-tenant calendar free/busy sharing, federated chat, and verified alias routing (paired with aligned SPF and DKIM) so teams can work together immediately while a full Microsoft 365 migration waits for a properly scoped weekend.

Around Day 30: Vendor Handoffs, Network Overlap, and SaaS Renewals

By week four, Day-1 fires have usually settled down, which makes it the right moment to clean up lingering third-party access. Even after buyer IT starts handling support tickets, old Microsoft GDAP or DAP partner delegations, former MSP RMM agents, firewall VPN accounts, and shared SSH keys frequently remain active unless someone audits them line by line. Walk through a structured handoff checklist with the outgoing provider, then rotate shared administrative secrets once your own support channels are running.

Watch out for local IP collisions before linking office firewalls as well. Acquired branch offices routinely sit on the same default 192.168.1.0/24 or 10.0.0.0/16 subnets as the buyer's network, so document VLANs, static printer and scanner IPs, and NAT translation or re-numbering windows before bringing up site-to-site VPNs. Around the same mark, run a SaaS and Microsoft 365 license audit against accounts-payable ledgers so duplicate subscriptions get flagged ahead of 60- or 90-day cancellation notice windows.

Days 60 to 100: Consolidation and Exiting the Seller TSA

When the operating plan calls for folding tenants and infrastructure together, pace the final cutovers around your TSA exit dates—extending past Day 90 to Day 100 or beyond if seller carve-out dependencies or a seasonal business freeze make rushing unwise. Pre-stage email, SharePoint, and OneDrive history in the background, give staff plain instructions ahead of device re-enrollment, and schedule dedicated deskside or remote support for the Monday morning after cutover.

Before closing out the TSA, move git repositories, CI/CD pipelines, deployment secrets, and consolidated management reporting into buyer-owned accounts. Export any historical records needed for tax, audit, or legal retention before retiring leftover seller tenants, and get written sign-off confirming TSA billing has ended. You can see how briskData works alongside deal teams, operating partners, and internal IT across pre-close technical due diligence and post-merger IT integration.