What does a OneDrive migration checklist cover?

It covers discovery, target readiness, Microsoft Entra configuration, mapping, pilot migration, production waves, incremental migration and post-migration validation.

What goes in the discovery checklist?

List the OneDrive users and sites in scope, record data volume and business owner, identify obsolete content, separate pilot and production waves, and flag renamed users and domain changes.

How do I confirm target readiness?

Confirm the target Microsoft 365 users exist and their OneDrive sites are available, verify destination ownership and naming, and resolve missing or disabled target accounts before migration.

What Microsoft Entra steps are in the checklist?

Create the source and target apps in their tenants, add the documented Microsoft Graph permissions, grant admin consent in each tenant, keep each app's credentials together and do not mix source and target credentials.

What should the mapping checklist confirm?

Load the required OneDrive sites, review automatic mappings, correct renamed users or domain changes, confirm every source user points to the intended target user, and save the final mapping.

What is in the production migration checklist?

Process users in manageable batches, monitor progress and Microsoft 365 throttling, review logs after each wave, and resolve exceptions before starting the next batch where practical.

What is in the incremental migration checklist?

Confirm whether users changed source data after the first pass, keep the same migration computer for previously migrated sites, reuse the verified mapping, run the subsequent pass, and review the logs and target changes.

Can this checklist be used for tenant-to-tenant and consolidation?

Yes. It is aligned with the EdbMails OneDrive workflow and supports tenant-to-tenant, cross-tenant and consolidation scenarios.

Does the checklist replace a pilot migration?

No. A pilot is part of the checklist and validates the process before production waves begin.

OneDrive Migration Checklist

Check Every Stage of Your OneDrive Migration

Use this OneDrive migration checklist to organize every stage of a user-file transfer, from assessment and account mapping to pilot migration and final validation. The guide highlights the checks administrators should complete, while EdbMails helps migrate supported OneDrive content between tenants.

OneDrive Migration Checklist: Before, During, and After

Use this OneDrive migration checklist to verify that the source and target Microsoft 365 tenants are prepared, users are mapped correctly, migration waves are controlled and the destination is validated before the project is closed.

The checklist is aligned with the current EdbMails OneDrive migration workflow, including Microsoft Entra app registration, source and target connection, site selection, mapping, simultaneous migration, incremental migration and migration logs.

Discovery checklist

List the OneDrive users and sites in scope.

Record approximate data volume and business owner.

Identify obsolete users or content that should not migrate.

Separate pilot users and production migration waves.

Identify renamed users, domain changes and mapping exceptions.

Target readiness checklist

Confirm target Microsoft 365 users exist.

Confirm required target OneDrive sites are available.

Verify destination ownership and account naming.

Resolve missing or disabled target accounts before migration.

Microsoft Entra configuration checklist

Create the OneDrive Migration Source app in the source tenant.

Create the OneDrive Migration Target app in the target tenant.

Add the documented Microsoft Graph application permissions.

Grant admin consent in each corresponding tenant.

Keep Client ID, Tenant ID and Client Secret Value from each app together.

Do not mix source app credentials with target tenant credentials.

Mapping checklist

Load the required OneDrive sites.

Review automatic mappings.

Correct renamed users or domain changes manually.

Confirm every source user points to the intended target user.

Save or document the final mapping used by the project.

Pilot checklist

Select representative users.

Run the migration.

Review logs for completed, skipped or failed items.

Validate target files and folders.

Record any procedure changes before the production waves.

Production migration checklist

Process users in manageable batches.

Monitor migration progress and Microsoft 365 throttling.

Review logs after each wave.

Resolve exceptions before starting the next batch where practical.

Incremental migration checklist

Confirm whether users continued changing source data after the first pass.

Retain the same migration computer for previously migrated OneDrive sites.

Reuse the verified source-to-target mapping.

Run the subsequent pass for supported new or modified content.

Review the resulting logs and target changes.

Post-migration checklist

Verify representative target accounts.

Confirm expected files and folders are present and usable.

Validate business-critical metadata, sharing or access where required.

Document skipped, failed or manually remediated items.

Obtain business or project sign-off before closure.

Frequently Asked Questions

What does a OneDrive migration checklist cover?
It covers discovery, target readiness, Microsoft Entra configuration, mapping, pilot migration, production waves, incremental migration and post-migration validation.
What goes in the discovery checklist?
List the OneDrive users and sites in scope, record data volume and business owner, identify obsolete content, separate pilot and production waves, and flag renamed users and domain changes.
How do I confirm target readiness?
Confirm the target Microsoft 365 users exist and their OneDrive sites are available, verify destination ownership and naming, and resolve missing or disabled target accounts before migration.
What Microsoft Entra steps are in the checklist?
Create the source and target apps in their tenants, add the documented Microsoft Graph permissions, grant admin consent in each tenant, keep each app's credentials together and do not mix source and target credentials.
What should the mapping checklist confirm?
Load the required OneDrive sites, review automatic mappings, correct renamed users or domain changes, confirm every source user points to the intended target user, and save the final mapping.
What is in the pilot checklist?
Select representative users, run the migration, review logs for completed, skipped or failed items, validate target files and folders, and record any procedure changes before production.

What is in the production migration checklist?
Process users in manageable batches, monitor progress and Microsoft 365 throttling, review logs after each wave, and resolve exceptions before starting the next batch where practical.
What is in the incremental migration checklist?
Confirm whether users changed source data after the first pass, keep the same migration computer for previously migrated sites, reuse the verified mapping, run the subsequent pass, and review the logs and target changes.
What is in the post-migration checklist?
Verify representative target accounts, confirm expected files and folders, validate business-critical metadata, sharing or access, document exceptions, and obtain business or project sign-off before closure.
Can this checklist be used for tenant-to-tenant and consolidation?
Yes. It is aligned with the EdbMails OneDrive workflow and supports tenant-to-tenant, cross-tenant and consolidation scenarios.
Does the checklist replace a pilot migration?
No. A pilot is part of the checklist and validates the process before production waves begin.