ShareGate is a common choice to move SharePoint Server content to SharePoint Online. It copies sites, libraries, lists, metadata, versions, and permissions, and it produces a migration report for every session. That report describes what the copy tool did. It does not tell you, on its own, whether the destination now holds everything the business expects.
A reliable migration therefore needs two things: a disciplined copy process and independent evidence of the result. This article covers the practices that matter most for SharePoint Server to SharePoint Online projects, and shows where Smart SharePoint Migration Toolkit fits: it scans the source and the destination, compares files and permissions, analyzes ShareGate report exports locally, and guards destination cleanup. It does not copy content.
1. Inventory the farm and assess complexity first
Do not start with a copy. Start with an inventory of what the farm really contains: site collections and subsites, libraries and their sizes, version history, unique permissions, workflows, forms, and customizations. Volume alone is a weak predictor of effort. A small site with classic workflows, InfoPath forms, custom permission levels, and hundreds of broken inheritance points can take longer than a large document archive.
- Identify classic workflows and InfoPath forms early. They need a redesign, for example with Power Automate or Power Apps, rather than a copy.
- Count libraries with very deep version history. Versions multiply migration time and destination storage.
- List objects with broken inheritance, users assigned directly, and disabled or unresolved accounts.
- Record custom permission levels and farm solutions that have no SharePoint Online equivalent.
Smart SharePoint Migration Toolkit turns its source scans into a complexity estimate based on thirteen weighted criteria (volume, history, customizations, permissions, and identity quality). When evidence is missing, for example without a permission scan, the affected criteria are excluded and the result is marked partial. Treat the estimate as a planning aid that always requires review, not as a verdict.
2. Write a reviewed source-to-target mapping
Every wave should rely on one written mapping between source URLs and destination URLs, reviewed before the first copy. This is where information architecture decisions are made: flattening subsites into separate sites, joining sites to a hub, or renaming libraries. Ad hoc copies outside the mapping are the main cause of content that nobody can find later.
In the toolkit, each migration folder holds a migration.mapping.txt file with one source URL and one target URL per line. The scan lists for both sides are derived from it, and the most specific source route applies to its descendants, so the same mapping drives scanning, comparison, and review.
3. Prepare identities and permissions before copying
Permission problems are cheaper to fix on the source than after migration.
- Map users and groups explicitly in ShareGate, and review accounts that no longer exist or are disabled in Active Directory.
- Reduce unnecessary broken inheritance and direct user assignments before the copy, with the site owners.
- Decide how SharePoint groups, Active Directory groups, and Microsoft 365 groups will be used on the destination.
Permission comparisons in the toolkit can use a cache of Entra users to separate disabled users from real gaps and to reduce limited-access noise. A mapping file, however reviewed, does not prove that group membership or effective access is equivalent on both sides.
4. Run a pilot on representative sites
Choose pilot sites that represent the hard cases, not only the easy ones: deep folders, large libraries, unique permissions, lists with lookup and person fields, and hidden lists. Use the installed ShareGate version and the real scope.
Pilot results are scoped evidence. In a synthetic pilot documented with the toolkit, ShareGate could not resolve hidden lists until they were made visible. Check hidden-list handling with your own version and scope, and never change a list's visibility automatically to make it discoverable.
5. Scan both sides and use fresh evidence
A comparison is only as good as the scans it compares. Scan the source and the destination for each wave, and rescan after each copy pass.
- Use the newest completed scan for each side, and compare scans taken close together.
- Reject scans that ended with errors or have no valid completion evidence.
- Normalize time zones between SharePoint Server and SharePoint Online before comparing modification dates.
The toolkit records a scan receipt for each inventory and verifies it before a comparison. It selects the newest completed scan traceably, asks for confirmation before an older scan is used, and blocks a comparison when a receipt does not match its inventory.
6. Compare files and permissions independently of the copy report
A ShareGate report lists what happened in each session: successes, warnings, and errors. A comparison of fresh scans answers a different question: what does the destination contain compared with the source, right now?
- Files: matched, missing in target, extra in target, changed version, and target older. Version-aware comparison catches files that exist on both sides but are not current on the destination.
- Permissions: matched, missing, and extra assignments, per scope.
The toolkit produces an HTML review and an Excel workbook for each comparison, with counters and per-library or per-scope evidence, and keeps a scan history to show progress between passes. Its success rate summarizes the compared scans. It does not certify that a migration is complete.
7. Treat incremental copies with care
Incremental copies are efficient, but they rely on modification dates. ShareGate documents that a permission-only change does not update an item's modified date, so an incremental pass does not bring it over. See ShareGate's guidance on copying content permissions.
- Compare permissions separately after each incremental pass.
- Review the right correction for each item instead of overwriting items automatically.
- Remember that repairing an item permission can create a new destination version, which later version comparisons must take into account.
8. Plan sharing links separately
ShareGate does not preserve existing internal or external sharing links. See ShareGate's sharing link limitation. Inventory sharing links on the source, plan how they will be replaced, and tell the people who rely on them. Matching item permissions are not proof that sharing links were preserved, and the Shared With column itself can be out of date.
9. Analyze ShareGate reports, then cross-check them
Export the ShareGate migration report of each session as CSV or Excel and keep it with the migration evidence. The toolkit dashboard reads the newest export locally, without connecting to a site or importing ShareGate, and groups report lines into issue patterns that the operator marks To fix, Accepted, or Fixed.
A cross-check panel then shows the ShareGate issues next to the latest file and permission comparisons, by destination site and list. The two measures have different denominators and are never merged into one success rate. Marking a pattern Fixed records an operator decision; only a new scan and comparison can show the result.
10. Clean up the destination only after review
Test copies, repeated passes, and changed mappings can leave duplicates or unexpected items on the destination. Clean them up only from reviewed evidence.
The toolkit generates cleanup scripts from a reviewed comparison. They run in dry-run mode by default, require explicit confirmation, revalidate each item before acting, and send only reviewed destination items to the recycle bin. A comparison never runs cleanup by itself. After cleanup, scan and compare again.
11. Protect the migration evidence
Scans, comparison workbooks, ShareGate exports, and logs contain user names, group names, and paths. Keep them in a private migration workspace with restricted access, and keep the migration log of decisions: accepted issues, deferred items, and owner sign-off.
Checklist by phase
| Phase | Practice | Evidence to keep |
|---|---|---|
| Assess | Inventory the farm and estimate complexity | Source scans and complexity review |
| Plan | Write and review the source-to-target mapping | Mapping file per wave |
| Prepare | Clean permissions and map identities | User and group mapping, Entra users cache |
| Pilot | Test hard cases with the installed ShareGate version | Pilot reports and comparisons |
| Copy | Run ShareGate passes per wave | ShareGate report exports |
| Validate | Rescan both sides and compare files and permissions | HTML and Excel reviews, scan history |
| Remediate | Fix reviewed issues, then rescan | Issue states, cleanup dry runs |
| Close | Owner review and sign-off | Final comparisons and decision log |
Boundaries
A clean or warning-only ShareGate report does not prove that every file, version, and permission reached the destination, and a high comparison success rate is not a completeness certificate. Both are evidence to review with the site owners. Smart SharePoint Migration Toolkit validates migrations; it does not copy content and does not run ShareGate copies. ShareGate is a third-party product, and WorkplaceCloudHub is not affiliated with it.
To go further, open the Smart SharePoint Migration Toolkit page or read the operator guide on GitHub.