A SharePoint migration starts with a decision: which content should move at all? Copying old versions, orphaned sites and overly broad permissions does not improve them.
Five steps to a sound plan
- 1Take inventory: List sites, data volumes, owners, last use, sensitive content, workflows and integrations.
- 2Define the target: Decide what is archived, deleted or migrated. Define sites, navigation, retention and external sharing for the target environment.
- 3Clean up permissions: Review groups and direct sharing before the transfer. Afterwards, test with user accounts that have no administrator rights.
- 4Migrate a pilot: Choose a small, representative site with typical file types, links and metadata. Measure errors, not just the number of files copied.
- 5Cut over: Plan a write freeze, delta pass, communication, rollback window and owners. Release the site only after business sign-off.
Microsoft's documentation on SharePoint Migration Manager describes the tools and prerequisites. The time required depends on data volume, source system, network and the state of permissions, so a reliable time estimate is only possible once the inventory exists.
Data location
For Swiss requirements, review the Microsoft 365 data residency commitments for each service and data type, together with your own contracts. An Azure region in Switzerland does not automatically determine where every SharePoint feature stores its data.
Further reading: SharePoint Online and on-premises compared · SharePoint Online in detail

