SharePoint migration step-by-step

In TheMigrator → Tenants, trigger a site discovery on the source tenant. Review the list of discovered sites — note sizes, last activity dates, and owners.

• Archive sites with no activity in 12+ months rather than migrating them.
• Very large sites (>1 TB) should be migrated in their own dedicated job.
• Note any sites using classic SharePoint features (InfoPath, 2013 workflows) — these will not work in the destination.

In TheMigrator → New migration, select SharePoint. Select source and destination tenants.

TheMigrator auto-matches sites by name. Review each mapping in the site mapping table.

• Matched sites (green): destination site exists and was auto-matched — verify the URL is correct.
• Unmatched sites (yellow): no destination site found — select from the dropdown or create the site in SharePoint Admin Center first.
• Sites marked as skip will not be migrated.

Launch the job and monitor in the job detail view. SharePoint migrations are measured in GB transferred, not item counts. Large document libraries (>100 GB) will show slower item rates but steady byte transfer rates.

• Throttle errors (429) are common for large sites — the worker retries with backoff automatically.
• If a specific file is consistently erroring, check if it exceeds 250 GB (the Graph API file size limit) or has a name containing characters not allowed in SharePoint URLs.

After migration, spot-check permissions on 5–10 sites. Confirm site owners, members, and visitors have the correct access. Check at least one document library with unique permissions.

Anonymous sharing links are invalidated after migration. Document every external link before migration and regenerate them in the destination. Notify recipients of the new links.