Can EdbMails migrate complete SharePoint site collections?

Yes. The documented SharePoint migration scope includes site collections and supported content within those sites.

Can I migrate only selected site collections?

Yes. Administrators can select the SharePoint sites included in the migration instead of moving the entire tenant by default.

Can source site collections be mapped to different target sites?

Yes. EdbMails provides source-to-target site mapping with automatic and manual mapping options.

Should I test a site collection before large-scale migration?

Yes. A representative pilot migration helps validate source access, target mapping and expected results before larger production waves.

Can I run incremental migration after moving a site collection?

Yes, for supported new or modified content and when the documented incremental-migration conditions are maintained.

What is the difference between site collection migration and granular migration?

Site collection migration moves an entire business site, while granular migration moves only selected sites, libraries, lists, files or folders.

Can source site collections be mapped to different target URLs or names?

Yes. Mapping should be reviewed before production migration, especially when source and target URLs or site names differ.

How should production site collection migration be run?

Start production migration in manageable batches after a representative pilot, then review logs and validate representative content in the target.

What should be reviewed in the migration logs?

Review failed or skipped operations in the migration logs and resolve the issues before cutover.

SharePoint Site Collection Migration

Move SharePoint Site Collections to Another Tenant

EdbMails helps administrators migrate supported SharePoint site collections and their content to mapped locations in a target Microsoft 365 tenant. Select the required sites, prepare destination mappings, monitor transfer activity, and validate the results against your planned migration scope.

Understanding SharePoint Site Collection Migration

SharePoint site collection migration moves selected site collections and their supported content from a source SharePoint Online environment to a target Microsoft 365 tenant. It is useful when organizations need to migrate complete business sites while retaining control over source selection, target mapping, migration order and validation.

EdbMails supports migration of SharePoint site collections, subsites, lists, libraries, documents, files, folders and other supported SharePoint content. Administrators can select the required source sites, connect to the target tenant, map the sites and monitor the migration through logs.

When to migrate complete SharePoint site collections

Tenant-to-tenant migration: Move complete business sites into another Microsoft 365 tenant.

Mergers and acquisitions: Transfer acquired business site collections into the target corporate environment.

Tenant consolidation: Bring multiple SharePoint environments into a unified Microsoft 365 tenant.

Business-unit transfer: Move selected site collections owned by a department or subsidiary.

Information architecture changes: Re-map site collections to a new target SharePoint structure.

SharePoint site collection migration workflow

Inventory source site collections and identify the sites that belong in the migration scope.

Review obsolete or unnecessary content before the migration where appropriate.

Prepare source and target Microsoft 365 administrative access.

Complete the required Source and Target Microsoft Entra app registrations documented for the EdbMails SharePoint migration workflow.

Connect to the source SharePoint Online tenant and load available sites.

Select the site collections that need to migrate.

Connect to the target SharePoint Online tenant.

Map each source site collection to its intended target site.

Run a pilot migration for a representative site collection.

Start production migration in manageable batches.

Review migration logs and validate representative content in the target.

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

What content should be validated after migration?

Area	Post-migration validation
Site collection	Confirm the correct source site is present in the intended target location.
Subsites	Check supported subsites expected in the migration scope.
Lists and libraries	Verify representative lists and document libraries.
Files and folders	Open representative migrated documents and check important folder structures.
Permissions and metadata	Validate critical permissions and metadata where they are required by the business.
Migration logs	Review failed or skipped operations and resolve issues before cutover.

Site collection migration vs granular migration

Site collection migration is appropriate when an entire business site belongs in the target tenant. Granular SharePoint Migration is better when only selected sites, libraries, lists, files or folders should move. Defining the right level of scope before migration helps avoid unnecessary transfer and simplifies post-migration validation.

Site mapping for SharePoint site collections

EdbMails provides source-to-target site mapping in the documented SharePoint workflow. Administrators can use automatic mapping, manually map source sites to their destinations, or reuse previous migration mapping where applicable. Mapping should be reviewed before starting production migration, especially when source and target URLs or site names differ.

Use incremental migration for final changes

If users continue working in the source SharePoint site collection during the main migration, supported content may change before cutover. A later incremental migration can process supported new or modified content while avoiding unnecessary reprocessing of previously migrated data, provided the documented incremental-migration conditions are maintained.

Frequently Asked Questions

Can EdbMails migrate complete SharePoint site collections?
Yes. The documented SharePoint migration scope includes site collections and supported content within those sites.
Can I migrate only selected site collections?
Yes. Administrators can select the SharePoint sites included in the migration instead of moving the entire tenant by default.
Can source site collections be mapped to different target sites?
Yes. EdbMails provides source-to-target site mapping with automatic and manual mapping options.
Should I test a site collection before large-scale migration?
Yes. A representative pilot migration helps validate source access, target mapping and expected results before larger production waves.
Can I run incremental migration after moving a site collection?
Yes, for supported new or modified content and when the documented incremental-migration conditions are maintained.
What is the difference between site collection migration and granular migration?
Site collection migration moves an entire business site, while granular migration moves only selected sites, libraries, lists, files or folders.

What Microsoft Entra app registrations are required for site collection migration?
The EdbMails workflow requires separate Source and Target Microsoft Entra app registrations documented for the SharePoint migration process.
Can source site collections be mapped to different target URLs or names?
Yes. Mapping should be reviewed before production migration, especially when source and target URLs or site names differ.
What content is included when migrating a SharePoint site collection?
The documented scope includes site collections, subsites, lists, libraries, documents, files, folders and other supported SharePoint content.
How should production site collection migration be run?
Start production migration in manageable batches after a representative pilot, then review logs and validate representative content in the target.
What should be reviewed in the migration logs?
Review failed or skipped operations in the migration logs and resolve the issues before cutover.