Published November 18, 2026
What the job is
Post-merger IT integration turns two companies' identities, networks, applications, data and IT teams into the operating model the deal assumed. It starts during diligence and runs well past closing.
The work has two clocks. Before closing, the law limits what the buyer may see and control. After closing, the business expects people to work together on day one.
Microsoft 365 mailbox, OneDrive, SharePoint and Teams moves have their own Trench Notes page.
How far to integrate
The first decision belongs to the deal, not to IT. Will the acquired company run as a separate unit, share some functions, or disappear into the buyer? The IT plan follows that answer.
The answer can differ by layer. A company kept as a separate brand may still move to the buyer's identity system and security tools while keeping its own product systems.
The approaches
| Approach | What it involves | When it fits |
|---|---|---|
| Hold separate | The acquired company keeps its systems. IT connects only identity, security monitoring and financial reporting. | A standalone unit, or a business that may be sold again. |
| Absorb | The acquired company moves onto the buyer's systems, and its own are retired. | A smaller company buying into a larger one with the same processes. |
| Best of both | Each system is chosen from either company, one area at a time. | Companies of similar size, each with platforms the other lacks. |
| New platform | Both companies move to a system neither runs today. | Both current systems are near end of life. |
A program can mix these. Decide per application, with the business owner who will live with the choice.
What may happen before closing
For deals that need a Hart-Scott-Rodino filing, the statute bars the buyer from acquiring the target's voting securities or assets until the waiting period ends. The FTC says the period is 30 days after filing, or 15 days for a cash tender offer or a bankruptcy. A Second Request extends it.
In the EU, the European Commission says a concentration with a Community dimension must be notified and may not be implemented before notification or until the Commission declares it compatible.
The FTC warns that sharing information before closing can contribute to gun jumping if the buyer effectively gains beneficial ownership of the seller. Where the companies compete, information exchange can also be evidence of an illegal agreement under Section 1 of the Sherman Act.
The FTC's guidance for diligence: share the least information needed, aggregate or mask competitive data, and use clean teams that exclude anyone responsible for competitive planning, pricing or strategy.
In January 2025 the FTC announced a $5.6 million civil penalty against XCL Resources, Verdun Oil and EP Energy for gun jumping. The complaint said the buyers halted EP's drilling plans and coordinated its customer contracts and prices before the waiting period ended. The maximum civil penalty for an HSR violation is $53,088 per day, and the FTC left it unchanged for 2026.
For IT, this means pre-closing work is planning. Connecting networks, granting the buyer access to the target's systems, or directing the target's IT decisions are questions for antitrust counsel before anyone acts.
The order of the work
- Diligence. Through counsel and any clean team, collect the target's application list, contracts, infrastructure, security posture and IT staff count. Record which contracts need consent to assign or change control.
- Day-one plan. Define what must work at closing: email between the companies, a shared directory, access to a few shared applications, payroll, and the buyer's security monitoring. Keep the list short.
- Security baseline at closing. Bring the acquired company's endpoints, identities and internet-facing systems into the buyer's monitoring before connecting networks.
- Identity coexistence. Let users find and reach each other before any mailbox moves. In Microsoft Entra ID, cross-tenant synchronization creates and removes B2B collaboration users in another tenant automatically.
- Network connection. Connect networks only after the security baseline is met, through controlled points rather than open routing between sites.
- Application decisions and waves. Decide keep, move or retire for each application with its owner, then migrate in waves after the shared services are stable.
- ERP and finance systems last. Move them at a period or year end agreed with the controller.
- Exit transition services. End each transition service only after its replacement is accepted.
What takes longer than expected
- Contracts. Software licenses, outsourcing agreements and SaaS terms may need the vendor's consent to transfer. Check each for assignment and change-of-control terms, and ask early.
- Identity. Look for duplicate names, conflicting email domains and different joiner and leaver processes before the directories meet.
- Data that cannot be shared yet. Customer, employee and health data may carry consent or contract limits that survive the deal. Legal has to clear each data flow. Microsoft says cross-tenant synchronization is intended for use within one organization, and that using it across organizations can add compliance duties, including under the GDPR.
- ERP. Two charts of accounts, two close calendars and two sets of reports have to agree before one system can serve both companies.
- People. Staff who run the acquired company's systems may leave during the uncertainty, taking knowledge the plan depends on.
What plans leave out
- Cross-tenant synchronization is not a migration tool. Microsoft says the source tenant is still needed for synchronized users to authenticate, and the tool does not move SharePoint or OneDrive data.
- It is one-way. Each user synchronized needs a Microsoft Entra ID P1 license in the source tenant. Its sync cycle is fixed to start every 40 minutes, and it does not synchronize devices or contacts.
- Shadow IT and SaaS bought on expense reports, which no contract list shows.
- The acquired company's open security findings, audit exceptions and unpatched systems, which the buyer inherits at closing.
- Both companies' backup, monitoring and support contracts running in parallel until the last migration is done.
Contracts, cost and the compliance clock
If the seller will keep running systems for the buyer after a carve-out, put each service in the transition services agreement with its price, its end date and the notice needed to extend it.
Public buyers get limited relief on internal controls. SEC staff guidance lets management leave an acquired business out of its assessment of internal control over financial reporting. The exclusion may not extend beyond one year from the acquisition date, or cover more than one annual report. The report must name the business and its significance, and material changes to internal control caused by the acquisition must still be disclosed.
Cybersecurity incidents in the acquired environment count after closing. For a public company, the SEC says an Item 1.05 Form 8-K is generally due four business days after it determines an incident is material.
Budget for consent fees, double licensing, transition services, retention bonuses for key IT staff, and the temporary staff who carry the migration.
Skills and operations
Name one integration lead with authority across both IT teams, and an integration management office that tracks decisions, dependencies and the day-one list.
Decide early who runs the combined IT organization, and tell staff. Identify the people the acquired company's systems depend on, and agree retention terms with them before closing.
Settle these first
- What operating model does the deal assume for the acquired company, and what IT savings does the deal model count on?
- What has antitrust counsel cleared IT to see and do before closing?
- What must work on day one, and who signs that list off?
- Which transition services are needed, for how long, and what does each extension cost?
- Is the buyer public, and which annual report will first include the acquired business's internal controls?
- Which of the acquired company's IT staff must stay through the integration, and on what terms?
Questions
- Can IT connect the two companies' networks before the deal closes?
- Ask antitrust counsel first. For HSR-reportable deals, the buyer may not acquire the target's assets before the waiting period ends, and in January 2025 the FTC announced a $5.6 million penalty settlement with buyers it said took operational control of a target before the waiting period ended.
- How long is the HSR waiting period?
- The FTC says 30 days after filing, or 15 days for a cash tender offer or a bankruptcy. A Second Request extends it.
- What is a clean team in M&A diligence?
- A group allowed to see competitively sensitive information under set rules. The FTC says it should not include anyone responsible for competitive planning, pricing or strategy, and that reports to the business should be aggregated and blinded.
- Can cross-tenant synchronization replace a tenant migration?
- No. Microsoft says it is not a migration tool. Synchronized users still sign in through the source tenant, and their data stays there.
- Must a public buyer include the acquired company in its SOX 404 assessment right away?
- No. SEC staff guidance allows the acquired business to be excluded for up to one year from the acquisition date and from no more than one annual report. The report must name the excluded business.