Is SharePoint cross-tenant migration the same as tenant-to-tenant migration?

They refer to the same broad movement between different Microsoft 365 tenants, but this page focuses on cross-organizational planning, mapping and business-transition scenarios such as mergers, consolidation and divestitures.

Can I migrate selected SharePoint sites between tenants?

Yes. EdbMails allows administrators to select the SharePoint sites and supported content included in the migration.

Does EdbMails support automatic SharePoint site mapping?

Yes. The current workflow includes automatic mapping as well as manual and previous-mapping options.

Can I run incremental migration after the first cross-tenant pass?

Yes. The documented workflow supports later incremental processing for supported new or modified content.

Is cross-tenant migration the same as restoring a backup to another tenant?

No. Migration uses the live source tenant. Cross-tenant backup restore uses a previously created backup as the source.

Do I need separate Microsoft Entra applications for cross-tenant migration?

Yes. The current EdbMails workflow uses separate Source and Target Microsoft Entra application registrations, each with the documented permissions and admin consent.

Can I test a cross-tenant migration before moving all sites?

Yes. You can run a pilot migration on representative sites to validate source and target connectivity, mapping and results before scaling to larger production waves.

What mapping options are available if automatic mapping does not fit my target structure?

In addition to automatic mapping, EdbMails provides manual mapping and previous-mapping options so you can align each source site with the intended target location.

Can I migrate several SharePoint sites in a single cross-tenant project?

Yes. You can load the available sites, select multiple sites and migrate them within the same project according to your approved scope.

How can I confirm which content migrated or was skipped?

Review the migration logs after each job. The logs help you identify failed or skipped items so they can be resolved before the final transition.

How do I validate a completed cross-tenant migration?

Check that the target sites match the approved mapping, verify representative lists, libraries, documents, files and folders, validate important permissions and metadata where required, and review the logs.

SharePoint Cross-Tenant Migration

Move SharePoint Content Across Tenant Boundaries

EdbMails simplifies SharePoint cross-tenant migration by helping administrators transfer supported sites and content between separate Microsoft 365 tenants. Select the required SharePoint sites, map source locations to target destinations, and review migration progress and results with greater control.

Understanding Cross-Tenant SharePoint Migration

SharePoint cross-tenant migration is the transfer of supported SharePoint Online content between separate Microsoft 365 tenants. Although closely related to tenant-to-tenant migration, cross-tenant projects often place greater emphasis on organization boundaries, target information architecture, site ownership, permission planning, merger or divestiture requirements, and post-migration validation.

EdbMails helps administrators connect separate Microsoft 365 tenants, select SharePoint sites, map them to the correct target locations, migrate supported content, run incremental passes, and review migration logs.

When organizations need cross-tenant SharePoint migration

Business event	Typical SharePoint requirement
Merger or acquisition	Move selected or complete business SharePoint sites into the acquiring tenant.
Tenant consolidation	Standardize several Microsoft 365 environments into one destination tenant.
Divestiture	Separate approved SharePoint sites and content into a new tenant.
Business-unit transfer	Move only the sites belonging to a department or operational unit.
Microsoft 365 reorganization	Re-map SharePoint sites into a new tenant structure and naming model.

Cross-tenant migration planning areas

Site inventory: Identify the SharePoint sites, site collections and supported content that belong in the new tenant.

Target architecture: Decide which source sites map to which target sites before production migration.

Administrative access: Prepare the source and target Microsoft 365 administrative accounts and SharePoint access.

Microsoft Entra configuration: Create the separate Source and Target applications required by the current EdbMails workflow.

Pilot migration: Validate representative sites before migrating larger batches.

Incremental passes: Capture supported changes created while source sites remain active.

Validation: Review logs and check important content in the destination.

How EdbMails performs SharePoint cross-tenant migration

Install and launch EdbMails.

Select the SharePoint and OneDrive migration workflow and choose SharePoint Sites Migration.

Connect to the source SharePoint Online tenant using the documented source application-registration details.

Load and select the SharePoint sites to migrate.

Connect to the target SharePoint Online tenant using the documented target application-registration details.

Choose automatic, manual or previous migration mapping as appropriate.

Review source-to-target site mapping.

Start the migration and monitor progress.

Review migration logs after the job.

Run an incremental migration if supported source content changed after the first migration pass.

Cross-tenant migration vs cross-tenant backup restore

These are different intents and should remain on different pages. Cross-tenant migration moves supported live SharePoint content from a source tenant to a target tenant as part of a planned transition. Cross-tenant backup restore starts from a previously created backup repository and restores protected content into another tenant.

If your project starts from the live source tenant, this migration page is the relevant cluster. If the source is a stored SharePoint backup, use the dedicated SharePoint backup/restore content instead.

Reduce risk with staged migration

Large cross-tenant projects are easier to control when they are divided into logical site batches. Start with lower-risk or representative sites, verify the target, then proceed with larger production waves. Keep a clear site-mapping document and use logs after every batch so skipped or failed items are resolved before the final transition.

Cross-tenant migration validation checklist

Correct source sites were selected.

Target sites match the approved mapping plan.

Representative lists, libraries, documents, files and folders are present.

Important permissions and metadata are validated where required.

Migration logs have been reviewed for failures or skipped content.

A final incremental pass has been completed when the source remained active.

Frequently Asked Questions

Is SharePoint cross-tenant migration the same as tenant-to-tenant migration?
They refer to the same broad movement between different Microsoft 365 tenants, but this page focuses on cross-organizational planning, mapping and business-transition scenarios such as mergers, consolidation and divestitures.
Can I migrate selected SharePoint sites between tenants?
Yes. EdbMails allows administrators to select the SharePoint sites and supported content included in the migration.
Does EdbMails support automatic SharePoint site mapping?
Yes. The current workflow includes automatic mapping as well as manual and previous-mapping options.
Can I run incremental migration after the first cross-tenant pass?
Yes. The documented workflow supports later incremental processing for supported new or modified content.
Is cross-tenant migration the same as restoring a backup to another tenant?
No. Migration uses the live source tenant. Cross-tenant backup restore uses a previously created backup as the source.
Do I need separate Microsoft Entra applications for cross-tenant migration?
Yes. The current EdbMails workflow uses separate Source and Target Microsoft Entra application registrations, each with the documented permissions and admin consent.

Can I test a cross-tenant migration before moving all sites?
Yes. You can run a pilot migration on representative sites to validate source and target connectivity, mapping and results before scaling to larger production waves.
What mapping options are available if automatic mapping does not fit my target structure?
In addition to automatic mapping, EdbMails provides manual mapping and previous-mapping options so you can align each source site with the intended target location.
Can I migrate several SharePoint sites in a single cross-tenant project?
Yes. You can load the available sites, select multiple sites and migrate them within the same project according to your approved scope.
How can I confirm which content migrated or was skipped?
Review the migration logs after each job. The logs help you identify failed or skipped items so they can be resolved before the final transition.
How do I validate a completed cross-tenant migration?
Check that the target sites match the approved mapping, verify representative lists, libraries, documents, files and folders, validate important permissions and metadata where required, and review the logs.