New Zealand | The Real Cost of M&A Isn’t the Migration. It’s What Happens in Between. 

New Zealand | The Real Cost of M&A Isn’t the Migration. It’s What Happens in Between. 

Join our community of 1,000+ IT professionals, and receive tech tips and updates once a week.

The Real Cost of M&A Isn’t the Migration. It’s What Happens in Between. 

New Zealand | The Real Cost of M&A Isn’t the Migration. It’s What Happens in Between. 

By Monday, someone senior has sent an all-staff email promising “one company from day one”. By Tuesday, a new starter in the acquired business is asking the service desk why she can’t see her new manager’s calendar. The service desk is asking IT what day one was supposed to mean. 

Nobody has moved a mailbox yet. The expectations have already shipped. 

Most M&A tenant migrations start in that gap, between what the announcement promised and what the project planned. It’s also where most of their money goes, though not the way people expect. Moving people is the cheaper part. Living in co-existence mode while you move them is where the bill grows.

Day 1 needs less than the announcement promised 

Day 1 in an acquisition is a communications event. The deal is public and people want to find each other. In practice that means a colleague from the other company appears in the address book, and a meeting invite shows whether they’re free. It also means email between the two companies doesn’t land in junk or get flagged as phishing. In a week full of unfamiliar “welcome to the family” messages, that’s harder than it sounds. 

That list is achievable in weeks, sometimes days, without migrating anyone. 

Full integration (one tenant, one identity, one set of everything) is Day 2 work, and Day 2 is measured in months. The trouble starts when an executive promises Day 2 on Day 1. Usually in good faith, always before IT has been asked. Agree what Day 1 means and looks like before the announcement is written. That conversation is far cheaper than the one afterwards.

Which tenant wins, and whose rules come with it

In most acquisitions the tenant question settles itself: the purchaser leads and already owns one. 

The harder question hides underneath. A tenant carries years of decisions: 

  • How freely people can share externally
  • What guests can see
  • How Teams get named
  • Which security controls staff accept, and which they’ve learned to work around 

The acquired business has its own set of those decisions, and it’s about to lose most of them. 

Moving in together works the same way. Two households, two couches, one lounge room. The argument about which couch stays is rarely about the couch. 

Some of the acquired company’s settings will be better than yours. Some of its people will lose a way of working they chose on purpose, and they’ll notice on their first morning. Deciding whose rules survive, setting by setting, is an executive call with a technical explanation attached. When it’s handed to the target tenant’s admins as a configuration task, the answer defaults to “ours”. The acquired business then learns what the merger means for them from a sharing link that stopped working. 

As explored in Know Your Tenant Before You Move It, the acquired tenant has its own history. In an acquisition, that history becomes everybody’s.

Duplicate identities: the same person, twice

Mergers produce doubles. An integration lead given an account in the purchaser’s tenant during due diligence. A CFO who was “set up early” to see the board papers, and now has two mailboxes and a meeting history split down the middle. Contractors who worked for both firms join the list. 

Each double is a small identity collision. Usually the account that already exists in the target wins, and the source mailbox and files are migrated into it. None of these is hard on its own. They are fiddly, and they cluster around the most senior people in the building. Look for them early because when found late, each one becomes an urgent favour for an executive. 

Identity continuity was identified as one of the six requirements in What a Microsoft 365 Tenant-to-tenant Migration Actually Involves. This is where it gets tested.

What a staged migration actually looks like

Larger M&A migrations are usually staged, moved in batches over weeks, because moving several thousand people in one weekend makes everyone nervous. In the blog Know Your People explored how a batch feels to the person in it. Here’s what it means for the organisation. 

A batch moves each person’s own things: their mailbox and their OneDrive. Shared things stay where they are. SharePoint sites and Teams remain live in the source tenant and stay the source of truth until the last batch has moved. 

Picture a migrated user on a Tuesday afternoon. Her mail arrives in the new tenant, and her personal files are there too. The project team she spends most of her day in is still in the old tenant, along with every document the team works on. Every edit she makes lands back there. She is working in two tenants at once. So is everyone in her batch, and everyone in every batch before hers. 

Why not move shared content with each batch? A team with forty members drawn from six batches has to live somewhere, and it can only live in one place at a time. 

Mail has a similar limit. A domain can be verified in only one tenant at a time, so the addresses everyone has been using can’t move until everyone is ready to move with them. Shared content and the domain move together, at the end.

Coexistence is a bridge, and bridges charge rent 

That Tuesday afternoon has a running cost, and it’s charged by the week. Coexistence tooling stays in place while everyone is split, and two admin teams keep two tenants running. Meanwhile the service desk answers a steady stream of “which side am I on?” tickets, and the answer changes with every batch. 

Joining two organisations needs that bridge, and those running costs are its rent. Rent accumulates, and every extra batch in the schedule adds weeks of it. In the blog What a Microsoft 365 Tenant-to-tenant Migration Actually Involves explained why coexistence is where the budget quietly goes. This is how. Nobody approves one large invoice; the schedule simply gets a batch longer at every planning meeting.

Every staged migration ends in a big bang

Staging feels like the safe choice, and for each individual move it is. Smaller batches mean smaller failures, with time to learn between them. 

What staging can’t do is avoid the big bang. Shared content and the domain still move at the end, in one event, for everyone. A staged migration is a big-bang migration with a long run-up. 

So the real decision is how long that run-up should be: how many weeks of split working and bridge rent you’ll pay to lower the risk of each step before the last one. Sometimes several months is right. Sometimes one well-rehearsed weekend for a few hundred people is cheaper and shorter than six batches, and far less confusing. The principle explored in the blog Lift-and-shift or Spring Clean? applies here.  The less you carry, the more realistic a short run-up becomes. 

Either way, the date usually comes from somewhere else. Buy a business out of a larger group and a Transition Services Agreement probably sets the clock; the next post covers how those clocks run. Buy a whole company and there’s often no TSA at all, so the deadline comes from synergy targets, a licence renewal or the integration plan the board approved. 

Know which one you’re working to before you choose the run-up. IT can price each option. The business decides which one it’s buying.

Key takeaways

  • Day 1 means people can find, see and email each other. Promise that, and plan everything else as Day 2.
  • Which tenant wins is usually settled. Whose rules win isn’t, and that call belongs to executives.
  • In a staged migration, shared content and the domain move last, so migrated people work across two tenants until the end.
  • Coexistence costs accrue weekly, and every staged migration finishes with a big bang. Choose the length of the run-up deliberately.

Before the Day 1 email goes out

Insentra has sat in the “whose rules win” meeting more often than anyone would choose to, and has priced the long run-up against the short one for organisations of most shapes. If the deal hasn’t been announced yet, that’s the best moment to talk. After the Day 1 email, it’s still a good one.

Planning an M&A tenant migration? Get ahead of the complexity.

Bringing two Microsoft 365 environments together takes more than a migration plan. From managing identities and coexistence to minimising disruption, the decisions you make early can save considerable time, cost and frustration later. 

Want to understand what a successful migration looks like? 

Download Insentra’s A Comprehensive Guide to Microsoft 365 Tenant Migrations for practical guidance on planning, execution and reducing migration risks. 

Need expert guidance for your migration? 

Whether you’re planning an acquisition, consolidating tenants or already navigating the challenges of coexistence, Insentra’s migration specialists can help you plan your next move with confidence. 

Contact Insentra’s migration experts 

Hungry for more?

If you’re waiting for a sign, this is it.

We’re a certified amazing place to work, with an incredible team and fascinating projects – and we’re ready for you to join us! Go through our simple application process. Once you’re done, we will be in touch shortly!

Who is Insentra?

Imagine a business which exists to help IT Partners & Vendors grow and thrive.

Insentra is a 100% channel business. This means we provide a range of Advisory, Professional and Managed IT services exclusively for and through our Partners.

Our #PartnerObsessed business model achieves powerful results for our Partners and their Clients with our crew’s deep expertise and specialised knowledge.

We love what we do and are driven by a relentless determination to deliver exceptional service excellence.

New Zealand | The Real Cost of M&A Isn’t the Migration. It’s What Happens in Between. 

Insentra maintains ISO/IEC 27001:2022 and ISO/IEC 27701:2019 certifications

We are proud to announce that Insentra has successfully maintained its ISO/IEC 27001:2022 and ISO/IEC 27701:2019 certifications