Organizations move to Microsoft 365 to cut costs and boost collaboration. Yet many migrations stall or fail due to messy data. Up to 40% of content in typical file shares is stale, duplicate, or orphaned. Path length issues and broken permissions block up to 15% of files during migration. Inactive users and groups add 20–30% to license and storage costs.
A clean source environment cuts migration time by half and reduces post-migration support tickets by 60%. This checklist shows how to prepare your data for a smooth move. It covers Exchange, SharePoint, OneDrive, Teams, and identity. Use these steps with Microsoft 365 Consulting Services or your internal team.
Why Cleanup Matters Before Migration
Cleanup work before migration saves time and money. It reduces the data volume you must move. It lowers the risk of errors and rework. It also improves security and compliance in the new tenant.
-
Smaller data sets migrate faster and cost less.
-
Fewer errors mean less downtime and fewer rollbacks.
-
Clean permissions reduce data exposure and audit findings.
-
Clear ownership speeds up support and change requests.
Step 1: Inventory and Scope Your Data
Start with a full inventory. Know what you have before you move anything.
Mailboxes and Groups
-
Count active mailboxes, shared mailboxes, and archive mailboxes.
-
List distribution groups and Microsoft 365 Groups.
-
Note mailbox sizes and item counts.
-
Flag mailboxes with no sign-in for 90+ days.
SharePoint and OneDrive
-
List all site collections and hub sites.
-
Count sites, libraries, folders, and files.
-
Measure total storage per site and per user.
-
Find sites with no owners or no activity for 180+ days.
Teams and Channels
-
List all teams and channels.
-
Count members and owners per team.
-
Flag teams with no posts or files for 180+ days.
-
Note teams with external guests and their access levels.
File Shares and On-Prem Data
-
Map all file shares that feed into M365.
-
Measure total GB and file count per share.
-
Run path-length reports and flag paths over 350 characters.
-
Identify blocked file types and special characters in names.
Step 2: Remove Unused Users, Groups, and Licenses
Unused identities add risk and cost. Remove them before migration.
-
Delete inactive user accounts with no sign-in for 90+ days.
-
Remove empty or legacy distribution groups.
-
Clean up Microsoft 365 Groups with no members or owners.
-
Revoke licenses for departed users and unused service accounts.
-
Document exceptions for compliance or legal hold.
This step often cuts license costs by 10–20% and reduces identity mapping errors.
Step 3: Archive or Delete Stale Content
Not all data needs to move. Apply retention rules and archive policies.
SharePoint and OneDrive
-
Find content untouched for 5+ years.
-
Archive old project sites to cold storage or PST.
-
Delete draft files, personal test folders, and temp uploads.
-
Remove duplicate files and old versions beyond policy limits.
File Shares
-
Move cold data to archive storage before migration.
-
Delete system logs, installers, and local backups.
-
Remove personal folders that do not meet business needs.
-
Keep a read-only copy of the source for 30 days post-cutover.
Archiving 30–50% of cold data can cut migration time and storage costs in half.
Step 4: Fix Path Lengths and File Names
Long paths and bad names break migrations. Fix them early.
-
Run a path-length report across all shares and sites.
-
Shorten paths over 350 characters to leave headroom for destination URLs.
-
Rename files with blocked characters: * " < > ? | \ / :.
-
Strip trailing spaces and periods from file and folder names.
-
Replace reserved names like CON, PRN, AUX, NUL.
Teams that fix path issues before migration see 90% fewer file-level errors.
Step 5: Clean Up Permissions and Ownership
Broken or excessive permissions cause security and access issues.
SharePoint and OneDrive
-
Assign a business owner to every site and library.
-
Remove direct user permissions where possible.
-
Use Microsoft 365 Groups or security groups for access.
-
Audit external sharing links and remove stale ones.
-
Simplify inheritance where custom permissions block migration.
Teams
-
Ensure every team has at least two owners.
-
Remove guest accounts that no longer need access.
-
Align channel permissions with current roles.
-
Document private channels and their membership.
Exchange
-
Review delegate permissions on shared mailboxes.
-
Remove full access for departed users.
-
Confirm archive mailbox links and retention tags.
Clean permissions reduce post-migration access tickets by 40–60%.
Step 6: Remove Orphaned and Shared Mailboxes
Orphaned mailboxes add risk and cost. Review each one.
-
List shared mailboxes with no active owner.
-
Decide to migrate, archive, or remove each mailbox.
-
Convert large shared mailboxes to Microsoft 365 Groups if needed.
-
Remove delegate access for departed users.
-
Apply retention policies to shared mailboxes before migration.
This step often removes 10–15% of mailbox objects and reduces migration scope.
Step 7: Remove Deprecated Apps and Workflows
Old apps and flows break in new tenants. Remove them before the move.
-
List unused Teams apps, tabs, and connectors.
-
Remove Power Automate flows with no runs in 90+ days.
-
Decommission legacy SharePoint workflows and InfoPath forms.
-
Update or remove third-party integrations that point to old endpoints.
-
Document custom apps that need rebuild or replacement.
Removing deprecated apps cuts post-migration support tickets by 25–35%.
Step 8: Apply Retention Labels and DLP Policies
Set governance rules before migration. This protects data in transit and at rest.
-
Publish sensitivity labels for confidential, internal, and public data.
-
Apply retention labels to sites, libraries, and mailboxes.
-
Enable DLP policies for PII, financial, and health data.
-
Set retention for Teams chats and channel messages.
-
Configure audit logging and eDiscovery cases for legal holds.
These steps reduce compliance risk and speed up audit responses.
Step 9: Validate Data Quality and Readiness
Run final checks before migration waves.
Mailbox Validation
-
Confirm item counts match source within 5% variance.
-
Check that contacts and groups transferred with custom attributes.
-
Verify shared mailbox permissions and delegate access.
-
Ensure archive mailboxes link correctly to primary mailboxes.
SharePoint and OneDrive Validation
-
Match file counts and folder structures to source.
-
Confirm permissions at site, library, and item levels.
-
Check that version history and metadata preserved where required.
-
Test user access for sample accounts in each role.
Teams Validation
-
Confirm team and channel membership matches source.
-
Check that files and posts migrated with correct timestamps.
-
Validate guest access and external sharing settings.
-
Test calling, meetings, and app tabs for pilot users.
Teams that validate after each batch see 80% fewer rollback events.
Step 10: Plan Cutover, Rollback, and Hypercare
A clean cutover plan reduces downtime and stress.
Cutover Steps
-
Lower DNS TTL on MX and Autodiscover to 300 seconds 48 hours before.
-
Run a final delta sync of mailbox data while mail still flows to old system.
-
Change MX records to Microsoft and verify propagation from multiple resolvers.
-
Update Autodiscover and confirm Outlook profiles resolve to the new tenant.
-
Publish or update SPF, DKIM, and DMARC records for the new mail path.
Rollback Triggers
-
Define clear triggers for rollback (e.g., >5% mail flow failure, critical app break).
-
Keep source systems read-only for 30 days post-cutover.
-
Document steps to revert DNS and re-enable hybrid if needed.
-
Test rollback in pilot before full cutover.
Hypercare Support
-
Staff a dedicated support team for 2–4 weeks post-cutover.
-
Track top issues and publish daily status reports.
-
Run quick training sessions for common tasks (Teams, OneDrive, SharePoint).
-
Close hypercare only after ticket volume drops to baseline.
How Microsoft 365 Consulting Services Help
Many firms use Microsoft 365 Consulting Services to lead cleanup and migration. These teams bring tools, playbooks, and experience.
-
They run automated scans for path lengths, permissions, and stale content.
-
They design destination structures for SharePoint, Teams, and OneDrive.
-
They set up governance (labels, DLP, retention) before migration.
-
They manage cutover, rollback, and hypercare with clear SLAs.
Engaging M365 consulting services early reduces risk and speeds up time-to-value. They also help with tenant-to-tenant moves, domain changes, and hybrid decommissioning.
Conclusion
A clean source environment makes Microsoft 365 migration faster, safer, and cheaper. Follow this checklist to remove stale data, fix permissions, and set governance before you move. Use Microsoft 365 Consulting Services or M365 consulting services to lead the work if you lack in-house capacity. The result is a smooth migration, lower costs, and a secure, compliant tenant ready for growth.