IT Integration After Acquisition
Exodesk helps New Zealand buyers plan and deliver the IT work around an acquisition. We identify what must keep working, agree the authorised handover and plan the identity, email, file and business-system changes in scope.
Planning for IT integration after acquisition can begin before settlement where access is authorised. If the deal has settled, we establish continuity needs and supplier responsibilities first.
Tell us the deal stage, the size of each business and the systems involved
What is IT integration after acquisition?
IT integration after acquisition is the planned work of keeping an acquired business trading while its identity, email, files, business systems, licences and support arrangements move to the operating model the buyer chooses.
That end state can be one combined Microsoft 365 environment, or two environments kept on purpose with agreed collaboration. Integration does not mean combining every directory and application.
Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide.
Where acquisition projects start
Buyers ask about IT integration after acquisition at different stages of a deal. The first conversation establishes what is agreed and what access is permitted.
During due diligence
Authorised discovery of systems, suppliers, licences and dependencies while deal terms can reflect them.
Continuity first
Confirm what the acquired team needs to keep trading and who holds administrative control.
Outgoing IT provider
Plan an authorised handover with the seller provider, including access and an exit date.
One tenant or two
Compare consolidation with deliberate coexistence against operating, security and application needs.
Part of a business
Separate transferring staff and data from systems that keep running for the seller.
Still running two of everything
Bring a stalled integration back to a plan with owners, milestones and exit criteria.
What the project delivers
We document the decisions and delivery plan for each IT integration after acquisition project, then carry out the technical work the buyer approves.
- Inventory. Systems, suppliers, subscriptions, owners and critical dependencies, with exclusions recorded
- Continuity plan. A Day One continuity and authorised-access plan, including support and transition responsibilities
- End-state decision. A documented choice between consolidation and coexistence, with cost, security, application and operating requirements considered
- Staged delivery. Prerequisites, pilot, cutover, communications, acceptance and recovery for the workloads in scope
- Handover and decommissioning. A checklist covering access removal, service cancellations and the records that must be retained
Business-system replacement, custom integration, extensive data remediation and legal work are scoped separately where needed. Keeping two systems on purpose can be a valid outcome. Broader technology advice sits with our IT consulting service, and ongoing governance with vCIO services.
What has to work on Day One
Day One of IT integration after acquisition covers the essential services and controls the acquired operation needs to keep trading, and that list is specific to each deal. Business.govt.nz advises buyers to check key assets, contracts and staff knowledge before buying, and IT assets, licences and access can be material deal terms.
- Business tasks. Critical tasks, authorised users, application access, connectivity and essential data
- Control. Approved administrative control, MFA and recovery access, domain and DNS control, and emergency escalation
- Recovery. Backup coverage and evidence that essential data can be restored, with retention and any legal holds recorded
- Payments. Payment authorisation and fraud checks agreed with the finance lead
- Support. Known faults, owners, support coverage and the criteria for accepting each handover
Existing access to job, dispatch or file systems may be essential straight away, while new sharing between the businesses can wait where the business agrees. Where relevant, Microsoft 365 backup for acquired users is part of continuity.
An authorised handover from the outgoing provider
Technical capability is not legal authority. Before access changes, the parties confirm the authorised scope, contract obligations and exit plan for the seller IT provider.
We use named administrator accounts controlled by the business and an approved secure handover method, not shared passwords in email. Rotation, session revocation, delegated access, service accounts, remote tools and network access are planned together, because a password change alone does not end every form of access.
The buyer sponsor approves work, spending and changes, with emergency authority agreed in advance. Registrar access matters early; see domain name management.
Consolidate or coexist
In IT integration after acquisition, branding is one input to the tenant decision, not the rule. A single Microsoft 365 tenant can support several custom domains, and separate tenants can be a deliberate long-term choice.
- Operating model. How the businesses will work together and who administers what
- Security and compliance. Administration boundaries, contractual separation and regulatory requirements
- Applications. Business systems tied to a directory or tenant, and supplier constraints
- Cost and exit options. Running costs, migration effort and any likely future separation
Coexistence is several separate configurations: calendar sharing, Teams external or guest access, shared channels, file permissions, mail routing and cross-tenant access. Trusting the other tenant MFA or device claims is a specific security decision. Cross-tenant synchronisation manages B2B user objects across tenants, but Microsoft states it is not a migration tool, and it does not move mailboxes or files. We record the chosen approach and its review triggers.
Dependency-based phases and pilots
Identity mapping and a prepared destination come early, but the workloads do not follow one fixed sequence. Microsoft tenant-to-tenant guidance covers both individual workload moves and coordinated batches.
We select supported tooling for the workloads in scope and separate preparation, pilot, acceptance, cutover and follow-up, with outage windows and a recovery route recorded. Retention or legal holds are not removed just to let a migration proceed.
An old email address can be retained in many cases, but domain ownership, routing, aliases, DNS and sending authentication need a cutover plan. Permission preservation depends on the tool, identities and workload, so expected access and links are verified after each move. Mailbox moves follow our email migration approach, and wider workloads our cloud migration service.
Privacy, licences and contracts
Information privacy principle 11 allows disclosure to facilitate the sale of a business as a going concern, but it is not blanket permission to transfer every record and does not settle notification.
Since May 2026, IPP3A requires an agency collecting personal information from someone other than the individual to take reasonable steps to make them aware, subject to exceptions. Privacy decisions in IT integration after acquisition stay with the legal or privacy lead, who records the disclosure basis, notification decision and retention before data moves.
A per-user licence does not automatically follow its user. We check each subscription, the legal entity, change of control provisions and destination licensing, including any migration entitlement needed. Software licensing covers that review. The buyer, seller and their advisers decide ownership, consent and transition terms.
How the project proceeds
Milestones for IT integration after acquisition are set from the deal structure, permitted access, system dependencies and supplier availability.
Agree scope and authority
Confirm the sponsor, permitted access, systems in scope, exclusions and who approves changes.
Secure continuity
Put the Day One essentials, administrative control, recovery access and support contacts in place.
Decide the end state
Document consolidation or coexistence, the dependencies and the review triggers.
Pilot and deliver
Move the agreed workloads in stages, with tests, communications and a recovery route.
Accept and decommission
Verify users, data, access and records, then retire services once exit criteria are met.
Services are cancelled only after their exit criteria are met: protection, recovery and retention are in place and replacement support is active. Native OneDrive moves can leave redirects that depend on the source tenant, so the whole scope is validated before any tenant is deprovisioned.
What affects the cost?
We quote IT integration after acquisition from the scope, not from headcount alone.
- Scope. Users, data volume, workloads, business systems, carve-out boundaries and any excluded workloads
- Tooling and licensing. Migration tooling, destination licences and any migration entitlement the method needs
- Overlap. Services running in both environments until exit criteria are met, and outgoing supplier charges
- Timing. Change windows, after-hours work, travel and third-party supplier involvement
The proposal separates planning, continuity, migration and ongoing support, and states inclusions and exclusions before work starts.
Acquisition IT integration questions
How long does IT integration after acquisition take?
Timing depends on access, data, applications, suppliers and the chosen end state. We set agreed milestones and acceptance checks for each deal. Ninety days can be a useful planning horizon, while some workloads stay separate on purpose.
Who pays for IT integration after acquisition?
The sale and transition agreements decide responsibility. The buyer and seller agree charges, services, dependencies and exit terms. A transition services agreement is one option, not the only way to allocate costs.
Can staff keep their old email addresses?
In many cases, subject to control of the domain and the migration design. Domain association, routing, aliases and sending authentication need a cutover plan. Keeping the old address does not require keeping the old tenant indefinitely.
Must the IT provider change on settlement day?
Not necessarily. Agree a handover that preserves essential services and sets authorised access, support and exit dates. Provider overlap can help where needed, and its length and cost depend on the deal.
What does a Microsoft 365 tenant migration cost?
Request a scoped quote covering users, data, workloads, complexity, tooling, licensing and support. Coexistence, migration and application work are priced separately. User count alone does not establish a reliable price.
Who should hold administrative access?
Authorised administrators controlled by the business should hold the access and recovery arrangements needed for continuity. Supplier privileges and the handover are documented securely. Sessions, delegated rights and remote tools are reviewed as well as passwords.
Must customers be told about an acquisition?
That depends on the transaction and how information flows. A lawful disclosure does not by itself settle notification. Where another agency collects personal information indirectly, IPP3A and its exceptions need consideration, and the privacy or legal lead confirms the approach.
What happens to existing IT contracts?
Check the assignment, change of control, consent, renewal and termination provisions in each agreement. The transaction structure matters. Record which entity holds each agreement and which services must stay available through the transition.
Should old applications be replaced immediately?
Decide from business need and risk. Stable applications can stay where appropriate, while unsupported, unsafe or non-transferable systems are addressed when necessary. Replacement may be a separate project.
Who provides IT integration after acquisition in NZ?
Exodesk plans and delivers acquisition IT work from Christchurch and Dunedin, supporting businesses nationwide. The continuity, handover, migration, supplier coordination and acceptance work included is agreed for each deal.
Discuss acquisition IT integration
Tell us the deal stage, roughly how many people and sites each business has, and the main systems involved. We will suggest a scope for the IT integration after acquisition and the next step. Please leave passwords and confidential deal terms out.
Talk to us about an acquisition
Tell us about both businesses and what needs to keep working, and we will be in touch to arrange a time that suits.
Prefer to talk?
Christchurch
Level 1, 85 Riccarton Road
Christchurch 8011
03 343 3124
Dunedin
Level 3, Bartons Building
2 Stafford Street, Dunedin 9016
03 479 2941