SharePoint migration is one of those projects that sounds straightforward on paper but quickly becomes complex in practice. Whether you're moving from on-premises SharePoint to SharePoint Online, consolidating multiple tenants, or migrating from a different platform entirely, the decisions you make before migration begins will determine whether the project succeeds or stalls.
Having guided hundreds of organisations through SharePoint migrations, we've distilled the critical success factors into fifteen areas that deserve attention before you move a single file.
Strategy and Planning
1. Define what success looks like
Before discussing tools or timelines, establish clear success criteria. Is the goal to reduce infrastructure costs? Improve collaboration? Consolidate content from multiple systems? Meet compliance requirements? The answer shapes every subsequent decision, from information architecture to user training. Organisations that skip this step often end up with a technically complete migration that doesn't deliver the business value they expected.
2. Audit your current environment
You can't plan a migration without understanding what you're migrating. Run a thorough discovery of your existing SharePoint environment: how many sites, how much content, which sites are actively used, which are dormant, and where the most critical business data lives. Pay particular attention to customisations — custom web parts, workflows, InfoPath forms, and third-party integrations that may not have direct equivalents in SharePoint Online.
3. Decide what not to migrate
This is perhaps the most important decision in the entire project. Most SharePoint environments contain significant volumes of outdated, duplicate, or irrelevant content. Migrating everything is the path of least resistance, but it creates a cluttered new environment and wastes migration bandwidth. Establish clear retention policies and work with content owners to identify what should be migrated, what should be archived, and what can be safely deleted.
Information Architecture
4. Redesign your site structure
Migration is a once-in-a-decade opportunity to fix the structural problems in your SharePoint environment. Don't simply replicate the old hierarchy in the new platform. Review how teams actually work, where cross-functional collaboration happens, and how information flows between departments. Design a hub-and-spoke architecture that reflects the current organisation, not the one that existed when the original SharePoint was deployed.
5. Standardise your metadata
Inconsistent metadata is the silent killer of SharePoint usability. Before migration, establish a managed metadata taxonomy that works across the organisation. Define the content types, site columns, and term sets that will be used consistently. This investment pays dividends in search accuracy, content findability, and compliance reporting for years after the migration is complete.
6. Plan your permissions model
Permission structures in mature SharePoint environments tend to become complex over time — inheritance breaks, direct permissions, orphaned groups, and access that no longer aligns with roles. Migration is the right moment to simplify. Design a clean permissions model based on security groups that align with your identity management system. Document the model clearly so it can be maintained consistently after go-live.
Technical Preparation
7. Assess your network capacity
Migrating large volumes of content to SharePoint Online requires sustained upload bandwidth. Assess your internet connectivity and plan migration windows accordingly. For organisations with terabytes of content, consider running migration out of hours or using migration tools that can throttle bandwidth usage during business hours to avoid impacting day-to-day operations.
8. Choose your migration tooling
Microsoft provides the SharePoint Migration Tool for basic migrations, but most enterprise migrations benefit from third-party tools that offer more control over scheduling, error handling, and incremental migration. Evaluate tools based on your specific requirements: content volume, source platform, customisation handling, and reporting capabilities. Run proof-of-concept migrations with representative content before committing to a tool.
9. Plan for authentication changes
Moving to SharePoint Online means moving to Azure Active Directory authentication. Ensure your identity infrastructure is ready — hybrid Azure AD configuration, conditional access policies, multi-factor authentication settings. Users who can't log in on day one will lose confidence in the new platform immediately.
Content and Compliance
10. Map your compliance requirements
If your organisation operates in a regulated industry, your SharePoint environment likely supports compliance obligations — document retention, legal hold, audit trails, data residency. Map these requirements explicitly and verify that they can be met in the target environment. SharePoint Online offers robust compliance features through Microsoft Purview, but they need to be configured correctly before content arrives.
11. Handle large files and special content
SharePoint Online has file size limits, path length restrictions, and character limitations that differ from on-premises. Identify content that exceeds these limits before migration and decide how to handle it. This includes large media files, deeply nested folder structures, files with special characters in their names, and OneNote notebooks that may need separate migration handling.
People and Change
12. Identify your champions
Technical migration is only half the project. The other half is getting people to use the new environment effectively. Identify champions in each department — people who are influential, tech-comfortable, and willing to support their colleagues through the transition. Invest in training these champions early so they can provide peer support from day one.
13. Plan your communication cadence
Users need to know what's changing, when it's changing, and what they need to do. Start communicating well before the migration begins. Explain the reasons for the change, the benefits they'll experience, and the timeline. Continue communicating throughout the migration with updates on progress, known issues, and where to get help. Silence breeds anxiety and resistance.
14. Design your training programme
Training should be role-based and practical, not generic overviews of SharePoint features. Show users how to do the specific tasks they perform daily — finding documents, sharing with external parties, managing approvals, searching across sites. Record short video walkthroughs that users can reference after the live training sessions. Plan refresher sessions for one month and three months after go-live.
15. Plan for post-migration support
The first 90 days after migration are critical. Establish a clear support structure — a dedicated Teams channel, a known email address, regular drop-in sessions — where users can get quick answers to their questions. Monitor adoption metrics and usage patterns. Address issues promptly. The organisations that sustain migration success are the ones that treat go-live as the beginning of the adoption journey, not the end of the project.
The Bottom Line
SharePoint migration is a significant undertaking, but it doesn't have to be painful. The organisations that invest in proper planning — strategic clarity, information architecture, technical readiness, and change management — consistently achieve better outcomes than those that rush to migration. Every hour spent on preparation saves multiple hours of remediation after go-live.
If you're starting to plan a migration, use this checklist as a conversation starter with your project team. The items that generate the most debate are usually the ones that need the most attention.
