01
SharePoint 2013 to SharePoint Online
Discovery should identify unsupported legacy patterns, customizations, workflows, forms, and upgrade constraints before migration planning.
SharePoint Server migration
SharePoint Server to SharePoint Online Migration
Move from on-premises SharePoint to Microsoft 365 with a structured approach covering discovery, migration planning, legacy dependencies, validation, and modernization.
Architecture path
SharePoint Server
Assess
Plan
Migrate
Validate
SharePoint Online
Modernize
Why Organizations Migrate
SharePoint Online can be part of a broader Microsoft 365 strategy, but the right migration path depends on business, compliance, architecture, licensing, and technical requirements. Not every organization has the same target state.
Microsoft 365 cloud adoption
SharePoint Server lifecycle planning
reducing legacy infrastructure dependencies
modern collaboration
integration with Microsoft Teams
Power Platform integration
modern SharePoint experiences
governance modernization
legacy application remediation
Supported Source Scenarios
02
SharePoint 2016 to SharePoint Online
Assess farms, site collections, permissions, custom solutions, integrations, and migration tooling fit before moving production content.
03
SharePoint 2019 to SharePoint Online
Review modern/classic mix, customizations, authentication, Power Platform opportunities, and validation requirements.
04
Hybrid / Multiple SharePoint Environments to SharePoint Online
Plan tenant architecture, content grouping, identity mapping, migration waves, and validation across multiple sources.
Each SharePoint version can require a different migration path. Assessment should confirm constraints before a tooling decision.
Before migration
Assess the Environment Before Moving Content
A SharePoint Server to SharePoint Online migration should start with inventory, dependency analysis, risk identification, and a migration strategy.
Inventory
Dependency Analysis
Risk Identification
Migration Strategy
Farm/environment structure
Web applications where applicable
Site collections
Sites
Libraries
Lists
Storage
File counts
Versions
Metadata
Content types
Managed metadata
Permissions
External users
Authentication dependencies
Large lists/libraries
Custom solutions
Third-party solutions
Integrations
Classic sites
Publishing sites
InfoPath
SharePoint Designer workflows
Custom JavaScript
Script Editor
Content Editor
Custom master pages
Legacy web parts
Farm solutions
Sandbox solutions
SPFx where present
Legacy dependencies
Migration Is More Than Moving Content
Legacy components may need to be assessed, retained, replaced, modernized, rebuilt, or retired. Do not assume automatic one-to-one conversion.
Content
Migrate
Classic experience
Modernize
InfoPath
Evaluate for Power Apps / alternative modern solution
SharePoint Designer workflows
Evaluate for Power Automate / modern workflow
Legacy JavaScript
Evaluate for SPFx
Custom solutions
Assess / Replace / Rebuild / Retire
Integrations
Validate / Redesign where required
Target Architecture
On-Premises
SharePoint ServerLegacy CustomizationsWorkflowsFormsPermissionsBusiness Data
Migration & Modernization
AssessmentMigration ToolingRemediationValidation
Microsoft 365
SharePoint OnlineMicrosoft TeamsPower AppsPower AutomateSPFxMicrosoft Graph
Migration Process
01
Discover
Map environments, stakeholders, content scope, usage patterns, and migration constraints.
02
Assess
Inspect content, permissions, customizations, forms, workflows, integrations, and risks.
03
Design
Define target architecture, site mapping, information architecture, permissions, and wave strategy.
04
Remediate
Clean up content, address blockers, rationalize legacy components, and prepare owners.
05
Pilot
Test tooling, mappings, throughput, permissions, metadata, versions, and user experience.
06
Migrate
Execute planned migration waves using the selected tooling and runbook.
07
Validate
Review reports, reconcile content, test permissions, check metadata, and confirm business processes.
08
Cut Over
Coordinate final delta moves, communications, redirects, ownership, and adoption steps.
09
Modernize
Move suitable legacy experiences toward modern SharePoint, Power Platform, SPFx, and APIs.
10
Support
Handle exceptions, user questions, failed items, and post-migration improvement work.
Migration Tooling
Tool selection depends on the source version, content volume, migration complexity, customizations, permissions, reporting, migration waves, and validation requirements. No single tool is always superior.
source versioncontent volumemigration complexitycustomizationspermissionsrequired reportingmigration wavesvalidation requirements
Microsoft SharePoint Migration Tool (SPMT)
Migration Manager where applicable
ShareGate
PnP PowerShell
PowerShell
Microsoft Graph
Custom scripts / validation tooling
Example strategy
Migration Waves
Actual migration waves depend on the customer environment. A wave strategy helps reduce risk by sequencing low-risk, standard, complex, and business-critical sites differently.
Wave 0
Assessment
Wave 1
Pilot / Low-Risk Sites
Wave 2
Standard Business Sites
Wave 3
Complex Sites
Wave 4
Business-Critical / Legacy Sites
Final
Validation & Cutover
Pilot Migration
Pilot migrations test the migration plan before broad rollout. They help verify tooling, mappings, throughput, validation methodology, and user experience with representative sites.
tool validation
migration throughput
metadata behavior
permissions
versions
customizations
user experience
business-process testing
validation methodology
Migration validation
Migration Completion Does Not Automatically Equal Migration Success
Validation should compare source and target results. A migration tool completing without errors is not the same as confirming content, metadata, permissions, versions, links, processes, and user acceptance. No migration should be sold with unsupported guarantees of 100% accuracy.
migration reportsfailed/skipped itemscontent reconciliationmetadata checkspermission checksversion checkslink checks where appropriatebusiness process validationuser acceptance testing
SourceTarget
SitesSites
LibrariesLibraries
ListsLists
FoldersFolders
FilesFiles
MetadataMetadata
VersionsVersions
PermissionsPermissions
Content TypesContent Types
UsersUsers
Modernization after migration
Migration Can Begin Modernization
Migration can be the beginning of modernization rather than reproducing the old environment in the cloud.
SharePoint Server
SharePoint Online
Modern Microsoft 365
Classic PagesModern Pages
InfoPathPower Apps where appropriate
SharePoint DesignerPower Automate where appropriate
Legacy JavaScriptSPFx where appropriate
Manual ProcessesPower Platform
Legacy IntegrationsModern APIs / Microsoft Graph where appropriate
What May Require Special Handling
These areas are not reasons to panic. They are items that should be identified during assessment so the migration plan is realistic and technically credible.
custom farm solutions
custom master pages
legacy web parts
custom JavaScript
InfoPath
SharePoint Designer workflows
unsupported file types
large files
complex permissions
external users
legacy authentication
third-party products
business-critical integrations
Who This Service Is For
Organizations still operating SharePoint Server
Organizations planning Microsoft 365 adoption
Organizations running SharePoint 2013/2016/2019
Organizations dealing with legacy SharePoint customizations
Organizations using InfoPath or SharePoint Designer
Organizations consolidating SharePoint environments
Organizations wanting to modernize while migrating
Organizations needing structured migration validation
Lifecycle awareness
SharePoint Server 2016 / 2019 Planning
Lifecycle planning should be neutral and evidence-based. SharePoint Online may be the right target, but a supported on-premises strategy can also be appropriate where business, compliance, or architecture requirements demand it.
Migration assessment CTA
Not Sure What Will Migrate?
Start with a SharePoint Migration Readiness Assessment.
Request a Migration AssessmentInventory
Dependencies
Risks
Modernization Requirements
Migration Strategy
Validation Plan
Migration enquiry
Discuss Your SharePoint Migration
Share the current version, scale, legacy components, timeline, and project details. Do not submit passwords, credentials, or sensitive tenant information through this form.
Frequently Asked Questions
Can SharePoint 2016 migrate directly to SharePoint Online?
Yes, SharePoint 2016 content can be migrated to SharePoint Online, but the approach depends on content structure, customizations, permissions, workflows, forms, tooling, and validation requirements.
Can SharePoint 2019 migrate to SharePoint Online?
Yes. SharePoint 2019 can be a source for SharePoint Online migration, but modern/classic experiences, custom code, authentication, integrations, and migration waves still need assessment.
What happens to InfoPath forms?
InfoPath should be identified during assessment. Some forms may need to be retained temporarily, replaced, rebuilt, or modernized with Power Apps or another suitable solution.
What happens to SharePoint Designer workflows?
SharePoint Designer workflows should be inventoried and reviewed against business process requirements. Modernization may involve Power Automate or another workflow approach where appropriate.
Can custom JavaScript migrate?
Custom JavaScript can often require special handling. It should be assessed for business value, security, browser behavior, modern SharePoint compatibility, and possible SPFx replacement.
Can farm solutions migrate to SharePoint Online?
Farm solutions do not move as farm solutions into SharePoint Online. They need assessment and may require replacement, rebuild, retirement, or a different architecture.
Can permissions be migrated?
Many permission structures can be mapped or migrated, but complex inheritance, item-level permissions, external users, and orphaned users require validation.
Can versions and metadata be migrated?
Versions and metadata may be migrated depending on the source, tooling, configuration, and limits. They should be included in pilot and validation checks.
Should we modernize before or after migration?
It depends. Some blockers should be remediated before migration, while other modernization work may be better after content lands in SharePoint Online.
Which migration tool should we use?
Tool choice depends on source version, complexity, reporting needs, permissions, customizations, migration waves, and validation requirements. No single tool is best for every scenario.
How do you validate a SharePoint migration?
Validation should compare source and target content, metadata, versions, permissions, reports, failed items, links where appropriate, business processes, and user acceptance.
How long does migration take?
Duration depends on environment size, data volume, customizations, permissions, migration windows, throughput, remediation work, and validation depth.