SharePoint Migration: Complete Enterprise Guide (2026)

Why SharePoint Migration Is an Enterprise Priority in 2026

Every enterprise running SharePoint on-premises faces the same reality in 2026: Microsoft is systematically deprecating Server features, Copilot only works with SharePoint Online, and the gap between what your on-prem environment can do and what Microsoft 365 delivers is widening every quarter. Migration is no longer optional — it is a strategic imperative.

In our 25+ years managing enterprise SharePoint for Fortune 500 companies, we have led over 300 large-scale migrations. The difference between a migration that finishes on time and on budget versus one that derails into a multi-year project comes down to planning discipline, tooling decisions, and organizational change management. This guide covers all three.

---

Types of SharePoint Migration

On-Premises to SharePoint Online

This is the most common migration scenario. Organizations running SharePoint 2013, 2016, or 2019 on-premises move their content, sites, and workflows to SharePoint Online within Microsoft 365.

Key challenges:

• Custom solutions (farm solutions, sandbox solutions) that have no cloud equivalent
• InfoPath forms that must be rebuilt in Power Apps
• Workflow dependencies on SharePoint 2010/2013 workflows that need Power Automate replacements
• Large content databases exceeding 100 GB that require throttling-aware migration tools
• Authentication changes from NTLM/Kerberos to Azure AD/Entra ID

Tenant-to-Tenant Migration

Common during mergers, acquisitions, and divestitures. Content moves between two Microsoft 365 tenants. This involves not just SharePoint but also Exchange, OneDrive, Teams, and Azure AD identities. See our dedicated [tenant-to-tenant migration guide](/services/sharepoint-migration) for the full playbook.

Hybrid Configuration

Some enterprises maintain a hybrid state where on-premises SharePoint coexists with SharePoint Online. This is appropriate for organizations with regulatory requirements that prevent certain data from residing in the cloud, or those executing a phased migration over 12-24 months.

---

Phase 1: Discovery and Assessment (Weeks 1-4)

Environment Inventory

Before migrating a single document, you must know exactly what you have. This means scanning every site collection, subsite, list, library, workflow, custom solution, and content database in your environment.

Discovery deliverables:

• Complete site collection inventory with sizes, last modified dates, and owner identification
• Custom solution inventory (WSPs, sandbox solutions, SPFx web parts, add-ins)
• Workflow inventory with complexity ratings (simple approval vs. multi-stage state machines)
• Content type and metadata analysis across all site collections
• External data connections (BCS, BDC, custom web services)
• User and permission mapping from Active Directory to Azure AD

Migration Readiness Score

We use a proprietary readiness scoring model that evaluates five dimensions:

| Dimension | Weight | Factors |

|-----------|--------|---------|

| Content Complexity | 25% | Volume, content types, metadata consistency |

| Custom Solutions | 25% | Farm solutions, InfoPath, custom code |

| Workflow Dependency | 20% | Legacy workflows, complexity, business criticality |

| User Readiness | 15% | Training needs, change resistance, executive sponsorship |

| Infrastructure | 15% | Network bandwidth, Azure ExpressRoute, hybrid DNS |

Organizations scoring below 60% need remediation before migration begins. Attempting to migrate an environment that is not ready leads to rework, data loss, and user frustration.

Content Audit and Cleanup

This is the most underestimated phase. Every enterprise migration we have led has reduced total content volume by 30-50% during the cleanup phase. Migrating garbage to the cloud costs more (storage fees), takes longer (migration throughput), and pollutes the new environment from day one.

Cleanup priorities:

• Delete orphaned sites with no owner and no activity in 24+ months
• Archive completed project sites to cold storage before migration
• Deduplicate documents (we routinely find 15-30% duplication in enterprise environments)
• Standardize metadata and content types before migration, not after
• Remove broken permissions and re-inherit where possible

---

Phase 2: Architecture and Planning (Weeks 3-6)

Target Architecture Design

Your SharePoint Online architecture should not mirror your on-premises structure. This is the single most common mistake enterprises make: lift-and-shift of a messy on-prem environment into the cloud.

Design principles for SharePoint Online:

• Flat site structure using hub sites instead of deep subsite hierarchies
• One site collection per functional unit (department, project, community)
• Consistent metadata taxonomy enforced through content type hub
• Modern pages and web parts exclusively — no classic experience
• Integration patterns using Power Platform instead of custom code

Migration Wave Planning

Never migrate everything at once. Wave-based migration reduces risk, allows learning, and gives IT support teams manageable workloads.

Recommended wave structure:

• Wave 0 (Pilot): 2-3 non-critical sites with friendly users, 2 weeks
• Wave 1: IT department and early adopters, 3 weeks
• Wave 2-4: Business departments in order of complexity (simplest first), 3-4 weeks each
• Wave 5: Complex sites with heavy customization, 4-6 weeks
• Wave 6: Final cutover of remaining content and decommission planning

Tool Selection

The migration tool you choose has an outsized impact on project success. We have used every major tool on the market and our recommendations for 2026 are:

| Tool | Best For | Limitations |

|------|----------|-------------|

| SharePoint Migration Tool (SPMT) | Small to mid-size, budget-conscious | No scheduling, limited reporting |

| ShareGate Migrate | Mid-size, IT-led migrations | Per-seat licensing cost |

| Quest Metalogix | Large enterprise, complex environments | Steep learning curve |

| AvePoint | Regulated industries, compliance-heavy | Higher cost, complex setup |

| BitTitan MigrationWiz | Tenant-to-tenant, Exchange + SharePoint | Content transformation limited |

For enterprises with 50,000+ users and complex customizations, we typically recommend Quest or AvePoint. For mid-market (5,000-50,000 users), ShareGate is the best balance of capability and cost. Contact our [migration consulting team](/services/sharepoint-migration) for a tool recommendation based on your specific environment.

---

Phase 3: Execution (Weeks 5-16)

Pre-Migration Testing

Before each wave, run a test migration of representative sites. This validates:

• Migration tool configuration and throttling settings
• Content fidelity (metadata, versions, permissions preserved)
• URL mapping and redirect rules
• User identity mapping accuracy
• Performance baseline for estimating wave duration

Migration Execution Best Practices

Network optimization:

• Use Azure ExpressRoute or VPN with sufficient bandwidth (minimum 1 Gbps for large migrations)
• Schedule large content transfers during off-peak hours (evenings, weekends)
• Configure migration tool throttling to stay within Microsoft 365 API limits
• Monitor SharePoint Online throttling responses and back off appropriately

Content integrity checks:

• Validate item counts pre and post migration for every library
• Spot-check metadata on 5-10% of migrated items
• Verify version history preservation on critical documents
• Test permissions by logging in as users from different security groups
• Validate that managed metadata terms mapped correctly

User communication:

• Send wave-specific communications 2 weeks, 1 week, and 1 day before migration
• Provide step-by-step guides for accessing content in the new location
• Set up a dedicated Teams channel for migration support questions
• Have floor walkers available on migration day for in-person support

Handling Failures

Migrations will have failures. The question is how you handle them. Our standard operating procedure:

• Log every failure with source URL, destination URL, error code, and timestamp
• Categorize failures into retriable (throttling, timeout) vs. structural (unsupported content type, path too long)
• Retry retriable failures in the next migration window automatically
• Remediate structural failures manually — this typically involves renaming files, fixing paths, or converting content
• Report daily to stakeholders with migration progress, failure rates, and remediation status

---

Phase 4: Hypercare and Stabilization (Weeks 16-20)

What Is Hypercare?

Hypercare is the 4-6 week period immediately following migration where dedicated support resources are available to handle migration-related issues. This is not optional — skipping hypercare is the #1 reason migrations are perceived as failures even when the technical execution was successful.

Hypercare activities:

• Dedicated help desk queue for migration-related tickets
• Daily triage of reported issues with same-day resolution targets
• User training sessions (live and recorded) on the new environment
• Performance monitoring of SharePoint Online for the migrated content
• Search validation to ensure migrated content is indexed and findable
• Redirect monitoring to catch broken links and update as needed

Post-Migration Optimization

After hypercare, transition to ongoing optimization:

• Implement governance policies for the new environment
• Configure retention policies and compliance labels
• Enable Copilot features on well-governed sites
• Decommission on-premises infrastructure in stages
• Document lessons learned for future migration waves

---

Common Migration Pitfalls

1. Underestimating Custom Solutions

Every farm solution, every InfoPath form, every SharePoint Designer workflow needs a migration plan. We have seen organizations discover hundreds of custom solutions during migration that were undocumented. Discovery must be exhaustive.

2. Ignoring Change Management

Users do not care about your technical migration milestones. They care that their files are where they expect them, their bookmarks work, and their daily workflows are not disrupted. Invest 20% of your migration budget in change management.

3. Skipping Content Cleanup

Migrating 10 TB of content when 4 TB is obsolete wastes time, money, and storage costs. Clean before you migrate.

4. No Rollback Plan

Every migration wave needs a rollback plan. If the migration fails catastrophically, how do you restore the source environment? Test your rollback procedure before you need it.

5. Insufficient Network Bandwidth

Migrating 5 TB of content over a 100 Mbps connection takes over 4 days of continuous transfer. Plan your network capacity before migration begins.

---

Frequently Asked Questions

How long does an enterprise SharePoint migration take?

For a 10,000-user environment with moderate complexity, plan for 4-6 months from discovery to hypercare completion. Highly complex environments with extensive customization can take 9-12 months. The timeline depends more on organizational readiness than on content volume.

What is the cost of a SharePoint migration?

Enterprise migrations typically cost $5-$25 per user for tooling and $15-$50 per user for consulting services, depending on complexity. A 10,000-user migration ranges from $200K to $750K all-in. Contact our [consulting team](/contact) for a detailed estimate.

Can I migrate SharePoint 2010 directly to SharePoint Online?

Not with most tools. SharePoint 2010 requires an intermediate upgrade to 2013 or 2016 before migrating to Online, or you can use a third-party tool like ShareGate that handles direct 2010-to-Online migration. We recommend the tool-based approach to avoid the intermediate upgrade cost.

What happens to my SharePoint Designer workflows?

They cannot be migrated. SharePoint 2010 and 2013 workflows must be rebuilt in Power Automate. This is typically the most time-consuming part of a migration for organizations with heavy workflow usage. Start the workflow inventory and rebuild planning in Phase 1.

Should I migrate OneDrive at the same time as SharePoint?

Yes. Migrating OneDrive (personal sites) alongside SharePoint team sites reduces the total migration timeline and gives users a complete experience in the new environment. Most migration tools handle both simultaneously.

How do I handle sites with more than 100 GB of content?

Break them into smaller migration batches by library. Most migration tools can target specific libraries within a site. Migrate the largest libraries during off-peak windows and monitor throttling closely. For sites exceeding 1 TB, consider the SharePoint Migration API for bulk transfer.