SharePoint migration readiness checklist

Project / scopeAccountable ownerTarget cutover date

01 Define the destination

Name an owner for each sourceRecord who decides what to keep, archive or leave behind. Resolve unsupported mapped-drive application dependencies before choosing SharePoint.
Map sources to sites and librariesList each source, its destination, its owner and the people who need access. Review the information architecture with those owners.
Record exclusions and retention decisionsAgree what will not move and how it will remain available where required. Do not delete the source as part of this worksheet.

Run a scan and keep the reportUse the assessment mode of the chosen migration tool. Assign owners to blocked files, invalid names and destination-path issues.
Check current service and tool limitsRecord the documentation URL, check date and constraints relevant to this estate. Test large files and deep paths in the pilot.
Validate identity and permission mappingTest representative users, restricted folders and explicit Deny rules. Document the intended destination access and verify it with both allowed and excluded users.

Choose difficult content as well as easy filesInclude realistic volumes, special permissions, long paths and the workflows people use every day.
Reconcile the pilot resultsCompare source and destination counts, review failed and skipped items, open representative files and verify access. Keep exceptions visible.
Have owners accept the resultAsk users to complete their real tasks in the destination. Record unresolved issues and the owner of each decision.

Agree the change window and final passDocument the write freeze, incremental migration approach, user communications and where people should work after cutover.
Document stop and recovery conditionsName the decision-maker, the conditions that stop the move, and how access to the original environment will be restored if needed.
Sign off the handoverKeep reconciliation reports, access results, exclusions and support instructions together. Decide source retirement separately after acceptance.

Use evidence references rather than passwords, tokens or personal records.

Open issues, evidence links and ownersGo / no-go decision, approver and date