IT Integration After an Acquisition: The First Ninety Days

The lawyers finish, the money moves, and a buyer owns a second business by the end of the afternoon. The technology work starts about an hour later, when somebody asks whether the acquired staff can get into their email.

A sale and purchase agreement, shortened to SPA in deal work, says very little about technology. It moves shares and assets, and leaves the buyer to find out what the acquired business was running.

Treat the following as illustrative. A Christchurch contracting business buys a 16-staff competitor and keeps both operations trading while it works out what to merge.

The seller’s IT provider stays on a month-to-month retainer that nobody cancels for eight months, at $1,150 a month. About $9,200.

Backup, mail filtering and antivirus subscriptions on the acquired side duplicate cover the buyer already pays for. At about $11 per user per month across 16 people, about $2,100 a year.

Two sets of books and two job systems get reconciled by hand for four hours a week. At $38 an hour, about $7,900.

Those three lines come to about $19,200 in the first year. None of it shows up on the deal sheet, because these costs start after settlement and come out of the operating budget.

What Is IT Integration After an Acquisition?

IT integration after acquisition, which advisers call post-merger integration, is the work of turning two separate technology environments into one that a single business can run and support. It covers identity and logins, mail flow, file storage, the line-of-business systems that carry the work, the licences and contracts underneath them, and the network at each site.

You are merging two directories, two mail systems and two sets of licences into one environment. The order you work in decides what the whole exercise costs, and that order is set out further down this post.

Deferring the work is a decision as well. A buyer who drifts past three months usually carries two of everything for a year.

Which systems does an acquisition actually touch?

An acquisition touches six system groups in most small and mid-sized deals. Each has an owner on the seller’s side who is leaving, and most of what they know was never written down.

• Identity, meaning the accounts and passwords staff use to log in, held in a directory on each side.
• Mail, including the mailboxes, the distribution lists and the address the acquired brand still publishes.
• Files, from a server in a cupboard through to whatever sits in the seller’s cloud storage.
• Line-of-business systems: the job, quoting, payroll or dispatch platform the acquired business runs on.
• Licences and contracts, some of them attached to a company that is about to stop existing.
• Connectivity and network hardware at each site, including whatever the seller’s provider still reaches remotely.

Very few buyers hold a full picture of those six at settlement, which is why the final cost comes in above the estimate. Building the inventory takes about a day and turns that estimate back into a fixed price.

Why do the first ninety days set the cost?

The first ninety days set the cost because nothing gets cancelled after them. A second IT provider keeps invoicing, a second set of Microsoft 365 licences keeps renewing, and nobody stops either.

Staff learn the workarounds too. Six months of copying data between two systems by hand becomes the way the job is done, and unwinding it later costs more than doing the integration at settlement.

Post-merger integration competes with everything else on your plate after a deal. Give it a named owner and a date, or it loses every week to something more urgent.

What Has to Work on Day One After a Deal Settles?

Three things have to work, and the list is shorter than most buyers assume: acquired staff can log in to the systems they used the day before, mail keeps flowing, and payments to staff and suppliers keep clearing. Everything else can wait a fortnight without costing money.

Day one is about continuity of trade. Nothing has to be merged for the acquired business to keep invoicing.

IT integration after acquisition goes wrong when a buyer moves logins, mailboxes and file storage in the same week as settlement. Do all three at once and staff have nothing left that works while you fix it.

What can wait until week four?

Four things can wait: shared file access across both businesses, reporting, the intranet, and email signatures and branding. None of those stop an invoice going out.

Branding is the item owners push hardest to change. Leaving it alone costs nothing, and a signature block with the old logo will not lose a customer.

Who should hold the day one IT checklist?

One named person on the buyer’s side should hold it, with authority to ring the seller’s provider directly. Split it across three inboxes and nobody owns it, which is how the first fortnight gets lost.

That role often sits with virtual CIO support, because it needs somebody who can read both a licence agreement and a network diagram.

How Do You Decide Between One Microsoft 365 Tenant and Two?

Ask whether the two businesses will trade as one brand within a year. If the answer is yes, migrate into a single tenant and accept the higher upfront cost. If the acquired business keeps its own name and its own customers, two tenants with a trust between them cost less to set up, and you carry the extra running cost every year after that.

A tenant is the container Microsoft 365 gives a business: one set of staff accounts, one set of mailboxes, one place where the rules about who can open what are written down. Each side of a deal arrives with its own, and neither can see into the other by default.

Microsoft’s tenant-to-tenant migration guidance names a merger or acquisition as one of the standard reasons a business consolidates into a single tenant, and treats identity mapping between the two as a planning step of its own. That mapping decides whether staff keep the address they sign in with, the user principal name.

Everything downstream depends on that answer, from mail routing to file permissions to licence counts.

When does keeping two tenants make sense?

Keeping two tenants makes sense when the buyer paid for the acquired brand itself. Somebody who bought a name, a customer list and a book of contracts has reason to keep that business separate for a year or two.

Two tenants also suit a line-of-business platform tied to the acquired company’s own directory. A franchise group faces the same identity question permanently, because running one technology standard across sites the group does not own never ends in a merger. The overhead is real: two sets of policies, two licence renewals, two places to remove a leaver.

A buyer who chooses two tenants now should still budget for Microsoft 365 tenant consolidation later, because brands usually merge in the end.

What does a trust between two tenants do?

It lets people in each tenant work with people in the other without moving any data. Microsoft’s planning guidance names the three pieces: mail routing between the tenants, calendar free and busy sharing, and federation so the two chat systems connect.

Set that up before anyone tries to book a joint meeting. Staff on both sides will try in the first week, so configure it before then.

What Should IT Due Diligence Have Found Before Settlement?

Due diligence should have found six answers that most buyers go looking for only after the deal: who holds the domain registration, which licences transfer, what the outgoing owner’s personal accounts are still running, what the seller’s IT provider is contractually entitled to do, where the data physically lives, and what state the backups are in.

Business.govt.nz describes due diligence as the process of understanding what assets, liabilities and commercial potential a business has, and its checklist tells buyers to confirm the business owns all key assets and can sell them. The same checklist covers every contract the business has signed, including the IT support and connectivity agreements.

IT due diligence asks the same question about the things that carry no serial number. A business can be sold with a domain name, a tenant and a software licence it does not own. Every gap on that list becomes a paid line item once IT integration after acquisition begins.

Which licences transfer with the business and which do not?

Software sold to a legal entity usually stays with that entity, and software sold per user moves with the user. Perpetual licences bought by a company being wound up go missing most often, and nobody notices until a renewal fails.

Get the list before settlement and check each line against the vendor’s own transfer terms. How software licensing handles a change of legal entity decides whether you are renewing or repurchasing.

What can the seller’s IT provider do when it loses the account?

The seller’s provider can do whatever its contract allows, which is often more than you expect. Remote access, administrator rights on the tenant and the ability to move a domain can all sit with the outgoing provider on the day you take over.

Ask for that contract in the first week and read the termination and access clauses. Then change the credentials that matter and put a date in writing on when the old access ends.

Start with who legally holds the domain registration, because a buyer that cannot edit its own records cannot move mail or verify a tenant.

In What Order Should Two IT Environments Be Merged?

Merge identity first, then mail, then files, then the line-of-business systems, and leave the tidy-up until last. Each step depends on the one before it. Buyers who run them in parallel to save time usually add a fortnight.

The same Microsoft guidance is explicit about the dependencies. Teams content depends on Exchange mailboxes, so mailboxes move first or alongside, and OneDrive and SharePoint move better together.

Everyone remembers mail, and it has the most moving parts. Moving mailboxes between tenants has its own order of operations and its own failure modes, and deserves a planning session.

What happens to shared files and permissions?

Permissions rarely survive a file move intact. Folder structures come across and the access rules get rebuilt, which is why files sit after identity.

Two directories sit underneath all of it. Each has its own accounts, its own groups and its own naming convention, and somebody has to decide which wins before a single file moves.

Microsoft renamed Azure Active Directory to Microsoft Entra ID, and both names still turn up in vendor documentation. Expect the seller’s paperwork to use the old one.

When does the line-of-business system move?

The line-of-business system moves last, and in some deals it never moves at all. A quoting or job platform that works is worth leaving alone while you learn what it does for the business.

IT integration after acquisition ends at a decision about that platform. The buyer either settles on one system or keeps both on purpose. Replacing them is a separate project and it belongs on a later budget.

An acquisition is also one of the events that sends a technology roadmap back for review. Keep that review outside the ninety days.

What Happens to Customer Data in an Acquisition?

Customer personal information moves with the business, and the Privacy Act 2020 provides for it. Information privacy principle 11 lists, among the grounds for disclosing personal information, that the disclosure is necessary to facilitate the sale or other disposition of a business as a going concern.

The Privacy Act 2020 replaced the Privacy Act 1993, so a policy still citing the 1993 Act has not been reviewed since 2020. Updating it takes an hour and removes an easy finding from any complaint.

You become the agency holding that information on settlement day, and you are responsible immediately. That includes the security duty and any access request that arrives the following week.

Does the acquired customer list need cleaning up first?

It needs checking, and the check belongs in due diligence. A customer database full of records nobody can account for becomes your problem the moment the deal completes.

Ask what the information was collected for, how long it has been held, and whether the business has ever had a breach. Record the answers, because you will be the one explaining them later.

What Does IT Integration After Acquisition Cost?

Expect between $8,000 and $22,000 as a one-off for a 10 to 25 user acquisition, plus two to four months of running both environments. Identity and mail are the largest single line. IT integration after acquisition is priced as a project, so the figure tracks headcount and the number of line-of-business systems that move.

Set that against the illustrative buyer above. Ending the seller’s provider retainer at month three, five months earlier than the drift case, saves about $5,700.

Removing the duplicated backup and filtering subscriptions in the second month saves about $1,800. Folding two sets of records into one takes the manual reconciliation from four hours a week to one, worth roughly $5,900.

Call it about $13,400 of the $19,200 recovered in year one, against an integration cost of about $9,500 at the midpoint of the table. Net gain in year one, about $3,900.

From year two the duplicated running cost has gone, so the figure settles near $19,000 a year. Those numbers are illustrative and they scale with headcount. A five-person acquisition shows the same pattern with smaller figures.

How Do You Integrate Two Businesses Without Stopping Trade?

Run it in stages, with day one scoped down to logins, mail flow and payments.

1. Confirm on settlement day that every acquired staff member can log in and that mail is flowing both ways.
2. Get the seller’s IT contract, read the termination and access clauses, then change the credentials that matter.
3. Inventory the six system groups above, with an owner and a current monthly cost against each line.
4. Decide one tenant or two, write down the reason, and hold that decision for at least a year.
5. Give every phase of the migration a date and a named owner, working in the order set out above.
6. Cancel the duplicated subscriptions and close out the second provider once the work is verified.

Steps one and two belong to the first week and need no budget approval. Steps three to six are the ninety days of IT integration after acquisition, and a buyer who finishes them is running a single supported environment.

Book a Ninety-Day Integration Plan

Exodesk has supported South Island businesses since 1989 and works with clients across Canterbury, Otago and Southland from offices in Christchurch and Dunedin. Our team handles the IT consulting and integration work that follows a deal, from the day one continuity check through to the last duplicated subscription.

Contact us today to discuss how we can help your business or connect with us on LinkedIn to stay updated with more insights.

Frequently Asked Questions

How long does IT integration take after an acquisition?

A 10 to 25 user acquisition usually takes about ninety days from settlement to a single supported environment, assuming the tenant decision is made inside the first fortnight. Identity and mail account for four to eight weeks of that. The job or quoting platform can run past that window on purpose. Enterprise post-merger integration in mergers and acquisitions, or M&A, is measured in years, and a deal of this size runs to weeks.

Who pays for IT integration after an acquisition, the buyer or the seller?

The buyer, in almost every deal. Integration costs sit outside the purchase price unless the sale and purchase agreement names a transition services agreement, known as a TSA, which is an arrangement where the seller keeps providing IT or administrative support for a set period at an agreed fee. Ask for a TSA where the seller runs systems the buyer cannot yet operate. Six to twelve weeks is a common term.

Can acquired staff keep their old email addresses?

Yes, and keeping them is usually the right call for the first year. The acquired domain stays live and its mail routes to the new mailboxes, so a customer writing to the old address still reaches somebody. Retiring the old address is a marketing decision with a technical dependency behind it.

Should the acquired business move to the buyer’s IT provider straight away?

No, and moving on the first day is a common mistake. The seller’s provider holds knowledge that was never written down, so a short paid overlap of four to eight weeks costs less than rediscovering the network from scratch.

How much does it cost to merge two Microsoft 365 tenants?

Merging two Microsoft 365 tenants costs roughly $3,000 to $8,000 in professional services for 10 to 25 users, covering identity mapping, mailbox moves and mail routing through the overlap. Licences keep billing on both sides until the second tenant is closed. Third-party migration tooling adds a few hundred dollars per user on larger moves.

Who has administrator access to the acquired systems after settlement?

Often nobody on the buyer’s side does, and losing that access is the most common day-one failure. An administrator credential held only by the seller’s provider stops the buyer changing anything until that provider cooperates. Collect the tenant administrator accounts, the registrar login and the network device passwords in writing before the settlement date.

Do you have to tell customers when their supplier is acquired?

No, there is no general obligation to notify every customer of an ownership change, and telling them anyway is good practice. The Privacy Act 2020 allows personal information to move where the disclosure is necessary to facilitate the sale of a business as a going concern, so the transfer itself is provided for in law. A short notice explaining who now holds the account prevents most of the questions. Send it from the acquired brand while that brand still means something to the customer.

What happens to the acquired business’s IT contracts?

Contracts follow whatever their own assignment clauses say, so some transfer with the business and some end on a change of control. Read the assignment and termination clauses in the IT support agreement, the connectivity contract and every software subscription before settlement.

How do you avoid paying for the same software twice after a merger?

Build one list of every subscription on both sides showing its renewal date, its per-user price and what it does, then mark the overlaps. Cancel the duplicated cover in the second month, once the buyer’s own tools are confirmed as covering the acquired devices. Most buyers find three to five overlapping subscriptions, and mail filtering and backup are the usual pair.

What is a carve-out and how does it change the IT work?

A carve-out is the purchase of part of a business, such as one branch or one product line, where the seller keeps trading with what remains. It is harder than buying a whole company, because the acquired staff and their data have to be separated out of systems that keep running for the seller. Expect a transition services agreement and a longer timeline. Budget for data extraction work that a whole-company deal would never need.

Is an acquisition a good time to replace an old system?

No, not during the first ninety days. A replacement piles change on top of change while nobody yet knows how the acquired business really works. Put the candidate on the technology roadmap for month six and integrate what already exists first.

Who provides IT integration support for acquisitions in Christchurch and Dunedin?

Exodesk plans and runs IT integration after acquisition for buyers across Canterbury, Otago and Southland, working from offices in Christchurch and Dunedin. The work covers the day one continuity check, the tenant decision, the identity and mail migration, the licence and contract review, and closing out duplicated subscriptions. Exodesk has operated since 1989 and provides IT support, managed services, cloud, cyber security and AI solutions to New Zealand businesses.