SharePoint Migration Tool: Complete Enterprise Guide for 2026

Why Enterprise SharePoint Migration Is Different

Migrating SharePoint at enterprise scale -- 10,000 users, 50TB+ of content, hundreds of site collections -- is fundamentally different from migrating a small business. The challenges multiply exponentially: permission inheritance chains spanning five levels deep, custom workflows that touch 30+ document libraries, managed metadata term stores with 10,000+ terms, and compliance requirements that mandate chain-of-custody documentation for every file moved.

At EPC Group, we have executed over 500 SharePoint migrations since 2001, including some of the largest in the Microsoft ecosystem. The most common failure pattern we see is organizations selecting a single migration tool and assuming it will handle everything. It will not. Enterprise migrations require a tool strategy, not just a tool selection.

This guide provides the technical depth that enterprise IT decision-makers need: real throughput benchmarks, licensing cost comparisons, limitation matrices, and the methodology we use for migrations involving 10K+ users across healthcare, financial services, and government organizations.

SharePoint Migration Tool (SPMT): Microsoft's Free Option

What SPMT Actually Does Well

Microsoft's SharePoint Migration Tool (SPMT) is a free, downloadable application that migrates content from file shares, SharePoint Server 2010/2013/2016/2019, and SharePoint Server Subscription Edition to SharePoint Online. For organizations already invested in the Microsoft 365 ecosystem, SPMT is the logical starting point -- but understanding its boundaries is critical.

SPMT's strongest use case is file share to SharePoint Online migration. It handles bulk document migration with metadata preservation, supports incremental migration (delta sync), and integrates with the Migration Manager in the SharePoint admin center for centralized scheduling and monitoring. For file share migrations under 100TB, SPMT delivers reliable throughput of 1-2TB per 24-hour migration window using a single migration agent.

SPMT Performance Benchmarks

Based on our testing across enterprise environments:

• File share migration: 1-2TB per 24 hours per agent (depends on file size distribution; many small files reduce throughput by 60-70%)
• SharePoint Server to Online: 500GB-1TB per 24 hours per agent
• Concurrent agents: Microsoft supports up to 50 agents, but throttling typically kicks in at 10-15 concurrent agents per tenant
• File size limit: 250GB per file (SharePoint Online limit)
• Path length: 400 characters maximum (including site URL)
• Scan speed: 10,000-50,000 items per hour during assessment phase

SPMT Limitations That Matter at Enterprise Scale

The limitations that rarely appear in Microsoft's documentation but consistently impact enterprise migrations:

• No workflow migration: SharePoint 2010/2013 workflows, Nintex workflows, and Power Automate flows are not migrated. They must be re-engineered, which typically costs $50K-$150K for organizations with 100+ workflows.
• Limited metadata mapping: SPMT migrates standard columns but struggles with complex managed metadata term sets, especially those with 5,000+ terms or multi-level hierarchies.
• No custom web part migration: Custom-developed web parts, InfoPath forms, and sandbox solutions are flagged but not migrated.
• Permission flattening: Complex permission inheritance chains (especially those with broken inheritance at multiple levels) can result in permission loss or over-permissioning.
• No pre-migration content analysis: SPMT does not identify duplicate content, ROT (Redundant, Outdated, Trivial), or content that violates SharePoint Online limits before migration begins.
• Throttling unpredictability: Microsoft 365 throttling is dynamic and can reduce migration throughput by 50-80% during peak hours (8 AM - 6 PM in your tenant's region).

ShareGate (Workleap): The Mid-Market Champion

ShareGate, now part of Workleap, has been the go-to migration tool for SharePoint consultants since 2012. Its desktop-based interface makes ad-hoc migrations straightforward, and its permission mapping engine is the most intuitive in the market. For organizations migrating from SharePoint Server to SharePoint Online with 5,000-20,000 users, ShareGate is often the most cost-effective choice.

ShareGate Strengths

• Permission mapping: Granular control over permission migration with conflict resolution rules. Supports Azure AD group mapping, which is critical for organizations consolidating Active Directory domains during migration.
• Incremental migration: Robust delta sync that handles content changes during multi-week migration windows. Conflict resolution policies (source wins, destination wins, merge) work reliably.
• Pre-migration assessment: Built-in site collection scanner identifies customizations, large lists, checked-out files, and other migration blockers before you start.
• Real-time reporting: Dashboard shows migration progress, errors, and warnings as they occur. Reports export to CSV for compliance documentation.
• PowerShell integration: Every GUI action has a PowerShell equivalent, enabling scripted batch migrations for large environments.

ShareGate Limitations

• Desktop-based architecture: Migration runs from a single workstation, which creates a bottleneck for very large migrations (50TB+). You can run multiple instances, but coordination becomes manual.
• No cloud-hosted migration: Unlike AvePoint, ShareGate does not offer a SaaS-based migration engine. All processing happens on-premises.
• Workflow migration is assessment-only: ShareGate identifies workflows but does not migrate or convert them. It provides an inventory report, which is valuable for planning but not execution.
• Pricing scales with seats: At $15,000-$30,000/year for enterprise licensing, costs can escalate quickly for large organizations needing multiple concurrent licenses.

ShareGate Performance Data

• SharePoint-to-SharePoint: 500GB-1.5TB per 24 hours per instance
• Permission migration: Adds 15-25% overhead compared to content-only migration
• Metadata-heavy libraries: 30-40% throughput reduction when migrating libraries with 20+ custom columns
• Optimal file size: Best performance with files between 1MB-100MB. Very small files (<100KB) reduce throughput significantly.

AvePoint FLY: Enterprise-Grade Migration at Scale

AvePoint's FLY Migration platform is purpose-built for large-scale enterprise migrations. Its cloud-hosted architecture, API-driven workflow engine, and compliance features make it the strongest choice for Fortune 500 organizations, especially those in regulated industries. If you are migrating 50,000+ users with HIPAA, SOC 2, or FedRAMP requirements, AvePoint is typically the right foundation.

AvePoint Strengths

• Cloud-hosted migration engine: No on-premises infrastructure required for migration processing. AvePoint's cloud agents handle the heavy lifting, which eliminates the desktop bottleneck that limits ShareGate at very large scale.
• Multi-geo support: Native support for Microsoft 365 Multi-Geo, which is critical for organizations with data residency requirements across multiple countries.
• Compliance documentation: Built-in chain-of-custody reporting, audit trails, and compliance templates for HIPAA, SOC 2, and FedRAMP migrations.
• API-driven automation: RESTful API enables integration with ServiceNow, Jira, or custom orchestration platforms for fully automated migration workflows.
• Content analysis and cleanup: Pre-migration content analysis identifies ROT, duplicate content, and compliance-sensitive data (PII, PHI) before migration begins.
• Tenant-to-tenant migration: Strong support for M&A scenarios where two Microsoft 365 tenants must be consolidated.

AvePoint Limitations

• Complexity: AvePoint's feature depth creates a steeper learning curve. Organizations without dedicated migration engineers typically need professional services to configure and operate the platform effectively.
• Cost: Starting at $25,000-$50,000/year for enterprise licensing, AvePoint is 2-3x more expensive than ShareGate. However, for migrations over 20,000 users, the per-user cost often equalizes.
• Overkill for small migrations: If you are migrating under 5,000 users with straightforward content, AvePoint's complexity adds unnecessary overhead.

PowerShell and PnP Migration: The Custom Approach

For organizations with strong in-house development teams, the SharePoint PnP (Patterns and Practices) PowerShell module combined with the Microsoft Graph API provides maximum flexibility. This approach is not a "tool" in the traditional sense -- it is a framework for building custom migration scripts tailored to your specific environment.

When PowerShell Makes Sense

• Highly customized environments: When your SharePoint deployment uses extensive custom solutions that no commercial tool handles out of the box.
• Selective migration: When you need to migrate specific content based on complex business rules (e.g., only documents modified in the last 3 years, only files tagged with specific metadata values).
• Integration requirements: When migration must integrate with existing CI/CD pipelines, ITSM platforms, or custom workflow engines.
• Budget constraints with technical capability: When the organization has senior SharePoint developers but limited budget for commercial tools.

PowerShell Risks at Enterprise Scale

We have been called in to rescue over 40 migrations that started with a "we will just script it" approach and hit walls. The common failure patterns:

• Throttling management: Custom scripts frequently hit Microsoft 365 API throttling limits. Commercial tools implement exponential backoff and retry logic; custom scripts often do not.
• Error handling gaps: A single failed file in a batch of 100,000 can halt the entire migration if error handling is not comprehensive.
• No incremental sync: Building reliable delta sync (tracking changes since last migration pass) is complex and error-prone without a commercial tool's change tracking engine.
• Permission mapping complexity: Programmatically mapping permissions across domains, resolving SID mismatches, and handling broken inheritance requires significant development effort.
• Maintenance burden: Microsoft regularly updates SharePoint Online APIs. Scripts that work today may break after a service update.

Enterprise Migration Tool Comparison Matrix

EPC Group's Enterprise Migration Methodology

After 25 years and 500+ migrations, we have refined a six-phase methodology that eliminates the failure modes we see in the field. This approach is tool-agnostic -- it works regardless of which migration platform you select.

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

The most frequently skipped phase is also the most critical. Discovery identifies the true scope of your migration -- and scope is where 80% of failed migrations go wrong.

• Content inventory: Automated scanning of all site collections, document libraries, and lists. We quantify total data volume, file count, file size distribution, and content age. A typical 50TB environment contains 30-40% ROT content that should not be migrated.
• Customization audit: Identification of all custom web parts, workflows, event receivers, timer jobs, and sandbox solutions. Each customization gets a disposition: migrate, re-engineer, retire, or replace with out-of-the-box.
• Permission analysis: Mapping of all permission levels, groups, and broken inheritance. We identify over-permissioned content and recommend permission cleanup before migration.
• Compliance mapping: For healthcare and financial services clients, we map content classification to regulatory requirements and document chain-of-custody procedures.
• User impact assessment: Identification of power users, content owners, and business processes that depend on SharePoint. This drives the communication and training plan.

Phase 2: Architecture Design (2-4 Weeks)

The target SharePoint Online architecture is designed based on discovery findings, not retrofitted after migration. Key decisions include:

• Hub site structure and navigation taxonomy
• Information architecture (content types, metadata, term store)
• Security model (Azure AD groups, sensitivity labels, conditional access)
• Governance policies (site provisioning, lifecycle management, storage quotas)
• Integration architecture (Power Platform, Teams, third-party systems)

Phase 3: Tool Selection and Configuration (2-3 Weeks)

Tool selection happens after discovery, not before. Based on the assessment data, we select the optimal tool combination and configure migration agents, scheduling windows, and error handling policies.

For most enterprise clients, we deploy a hybrid approach:

• SPMT + Migration Manager for file share content (typically 40-60% of total data volume)
• ShareGate or AvePoint for SharePoint-to-SharePoint content with complex permissions and metadata
• Custom PowerShell scripts for edge cases (custom list data transformation, metadata normalization, content cleanup automation)

Phase 4: Pilot Migration (4-6 Weeks)

We migrate 500-1,000 users across 3-5 representative site collections. The pilot validates:

• Migration throughput against planned timelines
• Permission accuracy (100% validation against source)
• Metadata integrity (spot checks on 10% of migrated content)
• User experience (pilot users provide structured feedback)
• Rollback procedures (tested and documented)
• Help desk readiness (common issues documented, runbooks created)

Phase 5: Production Migration (3-12 Months)

Production migration follows a wave-based approach. Each wave migrates 1,000-5,000 users over a 2-4 week cycle. Waves are sequenced based on business priority, complexity, and interdependencies between site collections.

Critical production migration practices:

• Migration windows: Off-peak hours (10 PM - 6 AM) for bulk content transfer; metadata and permission sync during business hours at reduced throughput.
• Incremental sync: Run delta sync 24-48 hours before cutover to minimize final migration window.
• Cutover validation: Automated scripts verify content count, permission accuracy, and metadata integrity before DNS/redirect cutover.
• Rollback triggers: Defined criteria (e.g., >5% permission errors, >1% content loss) that automatically pause migration and trigger rollback.

Phase 6: Post-Migration Optimization (Ongoing)

Migration completion is not project completion. Post-migration activities include:

• Search configuration and tuning (2-4 weeks for crawl completion and relevance optimization)
• Governance enforcement (automated policies via Microsoft 365 compliance center)
• User adoption monitoring (usage analytics, support ticket trends)
• Performance baseline (page load times, search response times, storage growth)
• Source environment decommissioning (after 90-day parallel operation period)

Compliance Considerations for Regulated Industries

SharePoint migrations in regulated industries carry additional requirements that generic migration guides ignore. These are non-negotiable for organizations subject to HIPAA, SOC 2, FedRAMP, or financial services regulations.

Healthcare (HIPAA)

• PHI identification: All content must be scanned for Protected Health Information (PHI) before migration. PHI-containing documents require encrypted transfer and audit logging.
• Business Associate Agreements: If using a commercial migration tool with cloud components (AvePoint), ensure a BAA is in place with the vendor.
• Access controls: Post-migration permission validation must confirm that PHI access is restricted to authorized personnel only.
• Audit trail: Complete chain-of-custody documentation showing every file's source, destination, transfer method, and validation status.

Financial Services (SOC 2 / SEC)

• Data classification: Financial documents must maintain classification labels through migration. Sensitivity labels in Microsoft 365 must be configured pre-migration.
• Retention policies: SEC Rule 17a-4 and FINRA requirements mandate specific retention periods. Migration must not reset document timestamps or break retention policy assignments.
• Segregation of duties: Migration administrators should not have access to production content post-migration.

Government (FedRAMP / GCC)

• GCC/GCC High tenants: Migration tools must support Government Community Cloud endpoints. Not all commercial tools do -- verify before purchasing.
• ITAR/EAR compliance: Content subject to export controls requires additional handling procedures during migration.
• Controlled Unclassified Information (CUI): CUI markings must be preserved through migration and mapped to Microsoft 365 sensitivity labels.

Common Enterprise Migration Failures (and How to Avoid Them)

Failure 1: Underestimating Scope by 40-60%

The most common failure. Organizations estimate data volume but forget to account for: version history (which can triple effective data volume), workflow re-engineering, custom solution replacement, user training, and post-migration optimization. Our discovery phase eliminates this by providing a comprehensive scope document before any migration begins.

Failure 2: Migrating Everything

Organizations that migrate all content without cleanup migrate 30-40% ROT (Redundant, Outdated, Trivial) content. This wastes migration time, inflates SharePoint Online storage costs ($0.20/GB/month beyond quota), and creates a cluttered user experience. We recommend aggressive content cleanup before migration -- it typically reduces data volume by 30-40% and migration duration by 25-30%.

Failure 3: Ignoring Change Management

A technically perfect migration fails if users cannot find their content or understand the new environment. Budget 15-20% of total project cost for change management: communication campaigns, role-based training, champion networks, and post-migration support.

Failure 4: No Rollback Plan

Every migration wave must have a documented, tested rollback procedure. If permission errors exceed 5%, if content loss exceeds 0.1%, or if business-critical workflows break -- you need to be able to roll back to the source environment within 4 hours. Organizations without rollback plans face extended outages when issues arise.

Migration Tool Decision Framework

Use this framework to select the right tool combination for your environment:

• Under 5,000 users, primarily file shares: SPMT + Migration Manager. Total tool cost: $0. Engagement with professional migration services recommended for planning and validation.
• 5,000-20,000 users, SharePoint Server source: ShareGate + SPMT for file shares. Total tool cost: $15K-$30K/year. Professional services recommended for architecture design and pilot.
• 20,000+ users, regulated industry: AvePoint FLY + SPMT for file shares + custom PowerShell for edge cases. Total tool cost: $25K-$50K+/year. Full professional services engagement strongly recommended.
• Tenant-to-tenant (M&A): AvePoint or ShareGate with tenant-to-tenant licensing. Additional Azure AD migration tooling required. Budget $200K-$500K+ for full tenant consolidation.
• Hybrid/multi-cloud: AvePoint is the strongest option for environments spanning multiple cloud platforms (SharePoint Online + Box + Google Drive + on-premises).

Why Organizations Choose EPC Group for SharePoint Migration

EPC Group brings 25+ years of SharePoint expertise to every migration engagement. Our team has executed 500+ migrations across healthcare, financial services, government, and Fortune 500 enterprises. What differentiates our approach:

• Tool-agnostic methodology: We select the right tools for your environment, not the tools we have a reseller agreement with.
• Compliance-first approach: Every migration includes compliance mapping, chain-of-custody documentation, and regulatory validation for HIPAA, SOC 2, and FedRAMP environments.
• Fixed-price engagements: After discovery, we provide a fixed-price proposal. No scope creep, no surprise invoices.
• Post-migration support: 90-day post-migration support included in every engagement to ensure adoption and resolve issues.
• Author-led expertise: Our CEO, Errin O'Connor, is a Microsoft Press bestselling author on SharePoint and Azure. The strategies in this guide come from hands-on enterprise experience, not theoretical knowledge.

Frequently Asked Questions