Most SharePoint migration problems don't happen on migration day. They come from decisions that were never made beforehand: who should see what, which old content is worth keeping, and how users will find their files afterwards. This checklist covers the groundwork that makes a file-share or SharePoint-to-SharePoint Online migration go smoothly, whether you use ShareGate, the SharePoint Migration Tool (SPMT) or the SharePoint Migration Agent.
1. Inventory what you actually have
Scan the source and record total size, file counts, the deepest folder paths and the largest files. Both ShareGate and SPMT can produce pre-migration reports. Without an inventory, you can't estimate time or spot blockers early.
2. Clean up before you move
Old duplicates, abandoned project folders and files nobody has opened in years slow the migration and clutter the new site. Agree with each department on what to archive or delete. Migrating less content is the easiest speed-up there is.
3. Check paths, names and file types
SharePoint Online has rules on characters, path length and blocked file types. Long, deeply nested paths are the most common cause of failures. Flag them in the inventory and shorten or restructure before migration.
4. Design the target structure
Don't copy a 20-year-old file share folder-for-folder. Decide which content becomes separate sites, which becomes document libraries, and where metadata (columns) can replace deep folder trees.
5. Map permissions deliberately
File shares often carry years of one-off NTFS permissions. Map them to a small set of SharePoint groups or Microsoft 365 groups instead of recreating every exception. This step matters even more if you plan to roll out Microsoft 365 Copilot, which surfaces whatever a user already has access to.
Tip: Run a permissions report on the source first. Broken inheritance and "Everyone" access are much easier to fix before the move than after.
6. Decide what metadata must survive
Created by, modified date and version history are often legally or practically important. Confirm your tool and settings will preserve the metadata you need, and test it on a sample.
7. Plan for throttling
Microsoft 365 limits how fast data can be written. Large migrations run faster outside business hours and in planned batches. Build that into your timeline rather than promising an overnight move.
8. Run a pilot
Migrate one department or library end to end. Check permissions, metadata, links and how long it took. Use the results to adjust the plan before the full run.
9. Use incremental syncs and a clear cut-over
Do a bulk copy first, then incremental passes to pick up changes. Pick a cut-over moment when the old location becomes read-only, so nobody keeps saving to the wrong place.
10. Prepare users and validate afterwards
Tell people what's moving, when, and where to find it. After migration, compare item counts and spot-check permissions and metadata. PnP PowerShell scripts are useful here for automated validation reports.
Planning a migration?
Agnism Digital Solutions runs SharePoint and Microsoft 365 migrations with ShareGate, SPMT and PnP PowerShell. Book a free 30-minute call to talk through your plan.
Book a free call