File server to SharePoint and OneDrive migration checklist

0 of 28 done

Part 1

Assess the file server

List every share with its ownerEach share needs a business owner who can sign off the move.
Record size and file counts per shareYou need these numbers to plan waves and libraries.
Find files larger than the supported sizeMigration Manager supports files up to 250 GB for file share migrations.
Check for unsupported files and charactersCompare your content against Microsoft's unsupported files list.
Find long pathsDeep folder trees can break once the SharePoint URL is added in front of them.
Export current NTFS permissionsKeep a record of who can access what before you change anything.

Part 2

Archive or delete stale dataAgree with owners what does not need to move.
Decide what goes to OneDrive and what goes to SharePointPersonal home drives usually suit OneDrive. Team shares usually suit SharePoint sites.
Design sites and librariesMap each share or top-level folder to a site and library.
Simplify permissionsPlan site-level groups rather than copying every folder-level exception.
Choose version settingsSet how many file versions Migration Manager brings across.
Pre-provision OneDrive for usersEach user needs a OneDrive before home drives can migrate to it.

Part 3

Pick agent machines that meet the requirementsWindows Server 2016 or later, or Windows 10, 64-bit, with at least 8 GB RAM. Microsoft recommends 16 GB.
Give each agent fast local diskMicrosoft lists 150 GB of free solid-state disk space.
Install .NET Framework 4.6.2 or laterThe agent will not run without it.
Allow the required outbound endpointsThe agent only makes outbound requests. Allow the endpoints listed on Microsoft Learn.
Check SMB on the source serverThe server hosting the source data must support SMB 2.0 or higher.
Review antivirus on agent machinesMicrosoft notes antivirus can slow migration. Assess the risk before changing it.
Install agents and group themTasks are assigned to the next available agent in the agent group.

Part 4

Run scans firstFix the issues the scan reports before the real copy.
Pilot one share with its ownerCheck permissions, metadata and how users open files from Teams and File Explorer.
Migrate in waves by departmentKeep each wave small enough to support on the day after.
Review task reportsCheck failed and skipped items in each task report.
Run a final incremental pass before cutoverPick up files changed since the first copy.

Part 5

Set source shares to read-onlyStop changes landing on the old server after the final pass.
Remove or redirect mapped drivesUpdate Group Policy or Intune so users stop opening the old paths.
Tell users where their files areSend each team a short note with the new site link.
Keep the file server for an agreed periodKeep it read-only until owners confirm nothing is missing.

Sources