Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A change in leadership does not, by itself, mean your organization needs a new Microsoft 365 tenant. First determine whether the business is keeping its current tenant or undergoing a merger, acquisition, divestiture, or reorganization that requires workloads to move. Then secure continuity for administrator access, domains, subscriptions, licenses, and billing before outgoing leaders or administrators leave.
1. Decide what is changing—and what is staying
Ask the incoming leadership and transaction owner whether the organization will keep its current legal entity, Microsoft 365 tenant, domains, and Microsoft agreement, or whether business units will be consolidated or separated. Microsoft identifies mergers, acquisitions, divestitures, and reorganizations as situations in which an organization may need to move data and workloads between tenants; an executive succession alone is not identified as a reason to migrate. See Microsoft’s Microsoft 365 migration overview.
Map the business outcome to the existing arrangement before changing accounts or subscriptions. Microsoft treats the organization, tenant, subscription, license, and user account as distinct concepts, so changing one does not automatically transfer the others. Its overview of subscriptions, licenses, accounts, and tenants is a useful reference when creating that inventory.
2. Preserve identity and administrator access
Before anyone departs, record the tenant ID, verified domains, administrator-role assignments, emergency access process, and business owners responsible for identity, email, collaboration, and billing. Confirm that designated staff can sign in and perform the tasks they will inherit; do not make an outgoing leader the only person able to administer or pay for the service.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- The Microsoft Office 365 Bible: The Most Updated and Complete Guide to Excel, Word, PowerPoint, Outlook, OneNote, OneDrive, Teams, Access, and Publisher from Beginners to Advanced
- ABIS BOOK
Use least privilege: give each administrator the narrowest role needed for their work. Microsoft describes Global Administrator as highly privileged and says it should be limited to emergency scenarios when an existing role cannot be used. Review Microsoft’s guidance on performing an internal admin takeover for that role guidance, but note its takeover procedure is specifically for an unmanaged account created through self-service signup—a directory without a Global Administrator. It is not a general ownership-transfer procedure for a managed corporate tenant.
3. Confirm control of your domains
For a business domain used with Microsoft email, identify the registrar, the account owner, who can sign in, and who controls DNS. Microsoft recommends knowing where the domain is registered and having the necessary sign-in details when setting up Microsoft 365 for business. The setup process can include adding and verifying a domain, adding users, and assigning licenses; see Microsoft’s setup planning guidance.
If a merger or separation requires a domain to move between tenants, treat domain release and cutover as a dedicated technical workstream. The setup and unmanaged-account takeover guidance do not constitute a transaction-specific domain transfer plan. In particular, the TXT-record verification described in the takeover procedure proves domain control for that narrowly scoped unmanaged-account case; do not treat it as a general way to take over an established, managed tenant.
4. Reconcile subscriptions, licenses, and billing
Record the agreement type, billing-account owner, renewal and purchasing responsibilities, subscription locations, license assignments, and the people who can view invoices or make purchases. These responsibilities may belong to different people and tenants, so verify each one rather than assuming they follow the executive role.
Rank #3
Microsoft documents a specific multi-tenant billing arrangement for enterprise customers with a Microsoft Customer Agreement. In that arrangement, an associated tenant can receive billing-management access, provisioning access, or both. Billing management enables billing roles for tasks such as invoice access and purchasing; provisioning access concerns creating subscriptions in an associated tenant. To move a subscription, the receiving tenant’s Global Administrator must accept the provisioning request, and all licenses in the subscription must be available. See Microsoft’s multi-tenant billing guidance.
Understand the consequences before removing an associated billing relationship: Microsoft says removal is permanent, revokes role access for users in that tenant, and prevents future subscription moves to it. Subscriptions already moved remain there and continue to be billed to the original account. Do not assume this Microsoft 365 process governs Azure: if Azure subscriptions are also changing hands, handle them separately. Microsoft’s Azure subscription billing-transfer guidance says moving an Azure subscription to another Microsoft Entra tenant permanently removes Azure role assignments; transferring billing ownership without moving the service tenant is a separate option described there.
5. Choose a migration path only if the business requires one
If the organization is consolidating or separating tenants, first define the scope: affected users, identities, groups, domains, workloads, and dependencies. Microsoft documents both workload-specific migration tools and Migration Orchestrator for coordinated moves across multiple workloads. Start with the migration overview and migration documentation to identify relevant planning and orchestration resources.
Do not commit to a migration duration or downtime estimate without a plan validated for your tenant and workloads. The Microsoft material cited here does not establish a universal timeline, outage estimate, or readiness assessment. For a complex merger, divestiture, or multi-workload consolidation, specialist migration planning may help coordinate dependencies and reduce avoidable disruption.
A manual copy between accounts is not a general substitute for tenant migration. Microsoft’s manual-transfer instructions apply to limited account-change scenarios when the Switch plans wizard is unavailable; Microsoft characterizes that process as unsupported, complicated, and time-consuming, and calls for careful planning to minimize downtime and data loss. Use it only if your situation meets the documented conditions in the manual-transfer guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Set policy and records requirements before changing accounts
Legal holds, retention, privacy, regulatory, employment, and records obligations depend on the organization’s jurisdiction, industry, contracts, and circumstances. Ask legal, compliance, and records owners to define the requirements before deprovisioning accounts or moving data; there is no single retention period that can be assumed for every organization.
Quick Recap
Preparation checklist
- Confirm whether the change is leadership succession only or a structural transaction requiring tenant consolidation or separation.
- Document the tenant, verified domains, administrator assignments, emergency access, and accountable business owners.
- Verify registrar, DNS, and billing-account access before people who control them leave.
- Inventory agreements, subscriptions, license assignments, renewals, invoice access, and purchasing authority.
- If migration is in scope, define workloads, users, identities, domains, dependencies, and policy requirements before setting a timeline.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
