Tenant-to-Tenant Migration Planning
The Challenge
Microsoft 365 tenant-to-tenant migrations are among the most complex IT projects organisations undertake. Whether driven by mergers, acquisitions, divestitures or restructuring, they touch every user and every piece of data.
Traditional approaches rely on spreadsheets, manual discovery and fragmented tooling, which leads to:
- Plans split by object type, when work runs across people, mailboxes, sites and apps
- Missed dependencies, such as a Power App that reads a list a flow fills from a shared mailbox
- Decisions in a Notes column, in a spreadsheet that leaves with the consultancy
- Staff who don’t know what is happening to them, and ring the service desk to ask
The Novalysis Approach
Discovery One record of your source tenant: users, groups, Teams, SharePoint sites, OneDrive accounts, Exchange mailboxes and Power Platform, kept current through continuous synchronisation.
Planning Waves built around departments and teams, with a dependency check that pulls in what their people use. Rules flag what could be left behind, for someone to review.
The assistant Ask the record questions in plain English. The assistant can propose changes, and a person approves them.
Communication One campaign for every wave, timed from each wave’s date, and a staff page in Microsoft Teams where each person sees their own move.
Sign-off Every scope decision recorded on the item it’s about, and a wave signed off before it exports to your migration tool.
Validation Check the destination tenant is ready before you migrate: naming conflicts, URLs and account availability.
Microsoft 365 Copilot Readiness
Preparing for AI in Your Organisation
Copilot can find anything the person asking is allowed to open. Over the years, files get shared with more people than anyone meant, and Copilot makes that visible.
How Novalysis Helps
Permissions down to the file Novalysis reads SharePoint permissions down to individual files and list items, keeps an inventory of sharing links, and shows who gets access by department.
A readiness state for every site Each site gets a Copilot readiness score and a state: Blocked, Pending Review, Ready to Enable, Enabled or Out of Scope. Its owner gets a plan of what to fix.
Causes in tenant settings Some causes, such as the default sharing link, sit in tenant settings. Novalysis lists them separately, because fixing them site by site only lets them grow back.
Working groups When the same few people keep sharing the files in one folder, Novalysis suggests a place of their own, such as a restricted library or a private team.
Department by department Then each department gets Copilot, announced with the same campaigns and staff page as a migration. Novalysis reads and recommends, and your site owners and SharePoint admins make the fixes.
Beyond Migration
Any change staff have to act on
An MFA rollout, a new sign-in method or a device policy has the same shape as a migration: groups of people, a date for each group, something each person has to do, and a service desk waiting for the ones who didn’t. Novalysis runs them with the same cohorts, campaigns, staff page and assistant, and its reminders can skip the people who have already done what’s asked.
Use Cases
Mergers & Acquisitions
When organisations come together, so do their Microsoft 365 tenants:
- Map both source and destination tenants
- Identify naming conflicts and duplicates
- Plan migration waves by department or team
- Coordinate staff communications across both organisations
Divestitures
Spinning off a business unit means extracting its people and content cleanly:
- Identify the resources associated with the divested unit
- Plan data separation and migration
- Record what was left behind, and why
- Verify the destination tenant setup
Tenant Consolidation
Organisations with several tenants from past acquisitions often consolidate:
- Assess each source tenant
- Find what can be cleared out before anything moves
- Plan a phased migration across tenants
- Keep one decision record across the whole programme
Copilot Pilot Preparation
Before enabling Copilot for a pilot group:
- Check the readiness state of the sites they use
- Find where sharing has spread further than intended
- Give site owners a plan of what to fix
- Track each site from Blocked to Enabled
Getting Started
- See it on a sample tenant - a walkthrough with the engineers who build it
- Pilot deployment - deploy in your Azure subscription for a focused assessment
- Full rollout - scale to your complete migration, readiness or rollout programme
Novalysis is bought through the Azure Marketplace. Public sector organisations that need to buy through a framework can do so through a provider we work with.
Contact us to find out how Novalysis can help your organisation.