What should a SharePoint migration checklist include?

It should include source discovery, target preparation, Microsoft Entra app registration, pilot migration, production waves, incremental cutover and post-migration validation.

Should every migration include a pilot?

A pilot is strongly recommended because it validates authentication, mapping, migration behavior and target results before larger production batches.

Do I need a final incremental pass?

If the source remained active during the main migration, a later incremental pass can process supported new or modified content before final transition.

Who should validate migrated SharePoint sites?

Technical teams should review logs and configuration, while business or site owners should validate representative content in the target.

Is this checklist only for tenant-to-tenant migration?

No. The same framework can support cross-tenant, consolidation, merger and other SharePoint Online migration scenarios.

How do I prepare the Microsoft Entra app registrations for the checklist?

Create separate Source and Target applications in the respective tenants, add the documented permissions, grant admin consent and record the Client ID, Tenant ID and Client Secret Value securely.

What source-to-target mapping options are available in EdbMails?

The workflow provides automatic, manual and previous mapping options so each source site can be associated with the intended target site before migration.

Can I migrate only selected SharePoint sites from the checklist scope?

Yes. Selective migration lets you choose the specific sites and supported content that belong in the approved migration scope.

How should large SharePoint projects be organized in the checklist?

Group the sites into manageable migration waves by business priority, then confirm the approved sources and review mapping before starting each batch.

Why are migration logs part of the checklist?

Migration logs record completed, skipped and failed operations, so you can resolve important errors and document unresolved exceptions before closing the project.

Does the checklist support cross-tenant consolidation projects?

Yes. The same discovery, preparation, mapping, pilot, production and validation steps apply when consolidating multiple SharePoint Online sources into one target tenant.

SharePoint Migration Checklist

Follow a Practical SharePoint Migration Checklist

Use this SharePoint migration checklist to prepare your source environment, confirm site ownership, review access, map destinations, and verify migrated content. Follow a clear sequence from assessment through post-migration checks, with EdbMails available to handle supported SharePoint content transfers.

What the SharePoint Migration Checklist Includes

A SharePoint migration checklist helps administrators verify that discovery, target preparation, app registration, site mapping, pilot testing, migration execution, incremental cutover and post-migration validation are completed in the correct order.

This checklist is designed around the documented EdbMails SharePoint migration workflow and can be used for SharePoint Online tenant-to-tenant, cross-tenant, consolidation and merger-related migration projects.

1. Discovery and source assessment checklist

Inventory SharePoint site collections and subsites in scope.

Identify site owners and business-critical sites.

Record important lists, document libraries, files and folders.

Review obsolete, duplicate or unnecessary content where appropriate.

Identify sites that should not be migrated.

Estimate the number of source sites included in the project.

Document business priorities and migration waves.

2. Target tenant preparation checklist

Confirm the target Microsoft 365 tenant and SharePoint Online environment.

Define target site names and destination URLs.

Create or prepare target sites where required.

Document source-to-target site mappings.

Confirm target administrative access.

Validate storage and service readiness in the destination.

3. Microsoft Entra app registration checklist

Create the SharePoint Migration Source application in the source tenant.

Create the SharePoint Migration Target application in the target tenant.

Add the permissions documented for each application role.

Grant tenant-wide admin consent as required.

Record the Client ID, Tenant ID and Client Secret Value securely.

Confirm that source and target application details are entered into the correct EdbMails connection.

4. Pilot migration checklist

Select a representative SharePoint site.

Connect successfully to the source tenant.

Load and select the correct source site.

Connect successfully to the target tenant.

Review source-to-target site mapping.

Run the pilot migration.

Review migration logs.

Validate representative migrated content in the target.

Record issues and update the production migration plan.

5. Production migration checklist

Group SharePoint sites into manageable migration waves.

Confirm the approved source sites for each wave.

Review site mapping before starting the batch.

Start the migration and monitor progress.

Review completed, skipped and failed operations.

Resolve important migration errors before moving to the next wave.

Have site owners validate representative business content.

6. Incremental migration and cutover checklist

Confirm whether the source remained active during migration.

Schedule the final incremental pass near cutover.

Use the same documented migration environment required for incremental checking.

Run the incremental migration for supported new or modified content.

Review final logs and exceptions.

Communicate the cutover time to users and site owners.

Confirm when users should begin working exclusively in the target.

7. Post-migration validation checklist

Validation area	Check
Site mapping	Confirm source sites migrated to the intended target locations.
Lists and libraries	Verify representative lists and document libraries.
Files and folders	Open representative documents and confirm important folder structures.
Permissions	Validate critical access where permissions are part of the migration scope.
Metadata	Check important metadata where required by business processes.
Logs	Review failed or skipped items and document unresolved exceptions.
Business acceptance	Obtain validation from the relevant site owners before final project closure.

Download-ready project checklist structure

For larger projects, copy these checklist sections into your internal migration tracker and add columns for owner, planned date, completion status, issue reference and validation result. This helps keep technical migration tasks aligned with business acceptance.

Frequently Asked Questions

What should a SharePoint migration checklist include?
It should include source discovery, target preparation, Microsoft Entra app registration, pilot migration, production waves, incremental cutover and post-migration validation.
Should every migration include a pilot?
A pilot is strongly recommended because it validates authentication, mapping, migration behavior and target results before larger production batches.
Do I need a final incremental pass?
If the source remained active during the main migration, a later incremental pass can process supported new or modified content before final transition.
Who should validate migrated SharePoint sites?
Technical teams should review logs and configuration, while business or site owners should validate representative content in the target.
Is this checklist only for tenant-to-tenant migration?
No. The same framework can support cross-tenant, consolidation, merger and other SharePoint Online migration scenarios.
How do I prepare the Microsoft Entra app registrations for the checklist?
Create separate Source and Target applications in the respective tenants, add the documented permissions, grant admin consent and record the Client ID, Tenant ID and Client Secret Value securely.

What source-to-target mapping options are available in EdbMails?
The workflow provides automatic, manual and previous mapping options so each source site can be associated with the intended target site before migration.
Can I migrate only selected SharePoint sites from the checklist scope?
Yes. Selective migration lets you choose the specific sites and supported content that belong in the approved migration scope.
How should large SharePoint projects be organized in the checklist?
Group the sites into manageable migration waves by business priority, then confirm the approved sources and review mapping before starting each batch.
Why are migration logs part of the checklist?
Migration logs record completed, skipped and failed operations, so you can resolve important errors and document unresolved exceptions before closing the project.
Does the checklist support cross-tenant consolidation projects?
Yes. The same discovery, preparation, mapping, pilot, production and validation steps apply when consolidating multiple SharePoint Online sources into one target tenant.