SharePoint Online Migration Guide 2026: Enterprise 12-Step Methodology

SharePoint Online Migration: The 2026 Enterprise Guide

SharePoint Online migrations in 2026 typically fall into one of four patterns: on-premises SharePoint to SharePoint Online, tenant-to-tenant consolidation (M&A-driven), file server to SharePoint Online, or competitor migration (Box, Dropbox, Google Drive). Each has distinct planning requirements, tooling choices, and timeline expectations.

This guide walks through every SharePoint Online migration pattern as we deliver them at EPC Group — covering tool selection, permission preservation, content remediation, and the governance framework that determines whether the migrated tenant stays clean.

EPC Group has delivered SharePoint engagements since the original SharePoint Beta Team (Project Tahoe, 2001-2003). We've migrated more than 50 million documents to SharePoint Online across Fortune 500 healthcare, financial services, government, and manufacturing organizations.

TL;DR — Migration Pattern Selection

Source Platform	Recommended Tool	Typical Timeline	Typical Cost (1,000 users)
SharePoint 2013/2016/2019/SE on-premises	ShareGate or Microsoft Native	12-26 weeks	$150K-$450K
SharePoint Online tenant-to-tenant	ShareGate or AvePoint	8-16 weeks	$100K-$350K
File Server (SMB/NFS)	ShareGate or Microsoft Native	8-14 weeks	$80K-$250K
Box / Dropbox	AvePoint or Mover	10-16 weeks	$120K-$300K
Google Drive	ShareGate or Microsoft Native	10-16 weeks	$100K-$300K

Migration Tool Comparison

Microsoft Native Migration Tools

Microsoft 365 Migration Manager (in admin center) covers:

• File server (SMB) → SharePoint Online / OneDrive
• SharePoint Server 2013/2016/2019 → SharePoint Online
• Box → SharePoint Online
• Google Drive → SharePoint Online / OneDrive
• Dropbox → SharePoint Online / OneDrive
• Mailbox migration via Exchange Online migration

Strengths: free, no third-party licensing, integrated with Microsoft 365 admin
Limitations: less granular permission preservation, fewer pre-flight reports, weaker support for complex SharePoint hub-spoke architectures

ShareGate (Most Common for Complex Migrations)

ShareGate is the leading paid migration tool, particularly for:

• SharePoint hub-spoke architectures requiring permission preservation
• M&A tenant-to-tenant consolidations
• Complex content type and metadata migrations
• Organizations with regulated-industry permission audit requirements

Strengths: best-in-class permission preservation, pre-migration reports, content rehydration after migration
Cost: scoped per migration project

AvePoint Migrator

AvePoint is the enterprise-tier paid migration platform, appropriate for:

• Fortune 500 multi-million-document migrations
• Highly regulated tenant-to-tenant consolidations (HIPAA, FedRAMP, FINRA)
• Long-term content management beyond migration (continuous compliance, retention)

Strengths: enterprise scale, regulated-industry compliance reporting, ongoing managed services
Cost: scoped after discovery, depending on data volume and regulatory requirements

Migration Pattern 1: On-Premises SharePoint → SharePoint Online

The most common large-scale migration pattern. Typical sequence:

Phase 1: Discovery (3-4 weeks)

• Site collection inventory (count, size, last-access date, owner)
• Content type and metadata audit
• Custom solution discovery (SPFx, sandboxed solutions, full-trust solutions)
• Workflow inventory (SharePoint Designer 2013 workflows, third-party workflow tools)
• User and group permission analysis
• External sharing audit
• Audit log review

Phase 2: Architecture (2-4 weeks)

• Hub-spoke information architecture design
• Sensitivity label taxonomy
• Content type plan
• Permission group strategy
• Power Automate replacement plan for SharePoint Designer workflows
• External sharing policy

Phase 3: Pilot Migration (3-4 weeks)

• Migrate 5-10 pilot site collections
• Validate content fidelity, permission preservation, workflow conversion
• User acceptance testing
• Pilot retrospective with adjustments

Phase 4: Wave Migrations (8-12 weeks)

• Departmental waves in priority order
• Each wave: 50-200 site collections
• Pre-migration content remediation
• Post-migration validation
• Communications and training per wave

Phase 5: Cutover and Decommissioning (2-4 weeks)

• Final delta migration
• DNS cutover (if custom domains)
• On-premises read-only mode
• 6-month preservation hold for compliance
• Final decommissioning

Total typical timeline: 18-26 weeks for 5,000-user enterprise. Engagement: fixed-fee.

Migration Pattern 2: Tenant-to-Tenant Consolidation

M&A-driven migrations from acquired tenant into acquiring tenant. Critical considerations:

• Identity migration: source tenant Microsoft Entra ID → target tenant. SAML/OIDC reconfiguration for connected SaaS apps.
• Email migration: Exchange Online tenant-to-tenant via Microsoft Native or BitTitan.
• SharePoint migration: ShareGate or AvePoint with permission re-mapping (source group SIDs → target group SIDs).
• OneDrive migration: per-user OneDrive migration with content fidelity.
• Teams migration: Teams chat history, channels, and tabs preservation.
• Power Platform migration: Power Apps, Power Automate, Dataverse environments.

Typical timeline: 12-20 weeks for 2,000-5,000 user acquisition.

Migration Pattern 3: File Server → SharePoint Online

Common modernization pattern for organizations replacing legacy SMB file shares:

• Pre-migration cleanup: identify duplicate files, stale content, abandoned folders. Typical 30-50% file count reduction during cleanup.
• Folder structure → Site architecture mapping: file server folders → SharePoint document libraries with metadata enrichment.
• Permission flattening: NTFS permissions → SharePoint permission groups. Typical permission complexity reduction from 100+ unique ACLs per file to 5-10 SharePoint groups per site.
• Search migration: file server search → Microsoft Search.

Typical timeline: 8-14 weeks for 1-3 TB of file server content.

Migration Pattern 4: Competitor Platform → SharePoint Online

Box, Dropbox, Google Drive migrations follow similar patterns:

• Content inventory via API
• User and shared-link mapping
• Content migration with permission preservation where possible
• Embedded asset migration (Google Forms → Microsoft Forms, Apps Script → Power Automate)
• Cutover communications

Typical timeline: 10-16 weeks for 2,000-5,000 user organization.

Frequently Asked Questions

How long does a SharePoint Online migration take?

Discovery: 3-4 weeks. Architecture: 2-4 weeks. Pilot migration: 3-4 weeks. Wave migrations: 8-12 weeks. Cutover and decommissioning: 2-4 weeks. Total: 18-26 weeks for 5,000-user enterprise.

What's the best SharePoint migration tool?

For complex on-premises migrations with hub-spoke architectures, ShareGate is the leading choice. For Fortune 500 scale and regulated-industry compliance, AvePoint Migrator. For straightforward file-server or Google Drive migrations, Microsoft 365 Migration Manager (free, native).

How much does a SharePoint Online migration cost?

EPC Group fixed-fee SharePoint migration accelerators are sized for 1,000-3,000 user organizations; Fortune 500 migrations (5,000+ users) are scoped fixed-fee.

Can SharePoint migrations preserve permissions?

Yes, with the right tools. ShareGate and AvePoint preserve granular SharePoint permissions including custom permission levels, security groups, and broken inheritance. Microsoft Native tools preserve site-level permissions but flatten document-level permissions during file server migrations.

What is hub-spoke information architecture?

Modern SharePoint information architecture replaces classic flat-IA designs with hub sites (top-level navigation containers) and spoke sites (departmental or topical sites associated with hubs). Hub-spoke enables consistent navigation, news rollup, and search scope without rigid sub-site hierarchies. EPC Group standard hub design: 1 root hub per business unit, 5-15 spoke sites per hub.

How do I migrate SharePoint Designer workflows?

SharePoint Designer 2013 workflows are deprecated and must be migrated to Power Automate. EPC Group typical migration: 80-95% of workflows convert via Power Automate's built-in SharePoint Designer migration assistant; the remaining 5-20% require manual rebuild. For complex workflows with custom code, evaluate Power Apps custom solutions.

Can I migrate during business hours?

Most SharePoint migration tooling supports incremental migrations with read-only / read-write phases. EPC Group typical migration runs business-hours read-write on the source tenant with overnight delta migrations until final cutover. Final cutover is typically scheduled for a weekend window.

What's the role of OneDrive in SharePoint migration?

OneDrive for Business is the per-user storage layer of Microsoft 365. SharePoint migrations typically include parallel OneDrive migration for personal files and folders. EPC Group typical migration: SharePoint document libraries (team content) and OneDrive (personal content) migrate in parallel waves with separate user training.

How EPC Group Delivers SharePoint Migrations

EPC Group has delivered SharePoint engagements since the original SharePoint Beta Team (Project Tahoe, 2001-2003). Errin O'Connor's Microsoft Press book Microsoft SharePoint 2013 Plain & Simple is referenced in Microsoft Learn-recommended reading lists.

Every SharePoint migration we deliver includes Microsoft Purview information protection planning, modern hub-spoke information architecture, Power Platform extension scope (Power Automate workflows, Power Apps custom apps), Microsoft 365 Copilot readiness assessment, and post-go-live managed services with monthly governance reviews.

Next Steps

Schedule a 30-minute discovery call at /schedule or call (888) 381-9725. We'll discuss your current SharePoint footprint, evaluate migration approach, and outline next steps.

Related reading: SharePoint vs Google Drive Enterprise, HIPAA-Compliant Microsoft 365, and Microsoft 365 Copilot Enterprise Guide.