Tenant Migration

Move from a CSP Office 365 Subscription to a New EA Tenant

Huda QurayshiHuda Qurayshi Nov 22, 2026 868 views

Question details

Determine whether an organization must migrate its Office 365 environment when moving from a CSP subscription to a separate tenant under an Enterprise Agreement.

Move from a CSP Office 365 Subscription to a New EA Tenant
Product
Microsoft Office 365
Device & OS
not provided
Scenario
The organization wants to move from an existing CSP tenant to a new, separate tenant under an Enterprise Agreement.
Observed behavior
The organization needs to understand whether a subscription change is sufficient or whether users, domains, and data must be migrated.
Before you start

Confirm that the Enterprise Agreement subscription will be assigned to a separate tenant rather than the existing CSP tenant. Inventory the source tenant's users, custom domains, mailboxes, documents, and other services that must move.

Solution 1Recommended

Plan and perform a tenant-to-tenant migration

Use this approach when the EA subscription is in a separate tenant and users need to retain services and data from the CSP environment.

A new tenant is a separate environment, so changing the subscription alone does not move its users, domain, mail, or files. Each workload needs an appropriate migration method and may have different prerequisites or limitations.

1
Set up the destination tenant

Create or access the EA tenant, then open the Microsoft 365 admin center to provision users and assign the required licenses. Use the tenant's onmicrosoft.com domain for initial accounts.

2
Choose migration methods

Inventory Exchange mailboxes, OneDrive files, SharePoint sites, Teams data, and other services in the source tenant. Review Microsoft documentation or a migration provider's guidance for each workload, including licensing, permissions, and supported data.

3
Plan identity and coexistence

Review user identities and sign-in requirements in the Microsoft 365 admin center and Microsoft Entra admin center. Schedule migration batches, user communications, and any necessary coexistence period before cutover.

4
Migrate and verify data

Configure the selected tenant-to-tenant migration tools and move the required workloads. Have users or administrators check representative mailboxes, files, permissions, and service access in the destination tenant.

5
Move the custom domain

In the source Microsoft 365 admin center, remove the custom domain from users and other dependencies before removing it from the tenant. Add and verify it in the destination admin center, update the required DNS records, and assign the new addresses to users.

Plan and perform a tenant-to-tenant migration
Migration methods vary: Microsoft's cross-tenant mailbox migration has specific prerequisites and licensing requirements. IMAP, cutover, staged, and hybrid migrations apply to particular source environments and are not interchangeable tenant-to-tenant methods.
Free Microsoft Office alternative

Continue working with Office files in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for opening and editing Office files as users transition between environments. It does not migrate Microsoft 365 tenants, mailboxes, or domains.

Open and edit documents while transitioning to a new tenantCompatible with Microsoft Office formats including DOCX, XLSX, and PPTXFamiliar editing interface for a smoother switchFree and lightweight office tools
microsoft office alternative - wps office

Frequently Asked Questions

Does moving to a new EA tenant require a migration?

Yes. A separate tenant does not automatically inherit the CSP tenant's users, domain, mailboxes, or files. Plan and migrate each required workload.

Can the same custom domain be used in both tenants at once?

No. Remove the domain and its dependencies from the source tenant before adding and verifying it in the destination tenant through the Microsoft 365 admin center.

Will mailbox migration also move OneDrive and Teams data?

No. Exchange, OneDrive, SharePoint, and Teams require separate planning. Check the selected migration method's support and prerequisites for each workload.

Can we avoid moving to a new tenant?

Possibly. Ask your Microsoft account team or licensing partner whether the EA subscription can be provisioned in the existing CSP tenant and confirm the applicable licensing conditions.