SharePoint to SharePoint Online Migration
Enterprise guide to migration tools, assessment, content audit, site mapping, incremental migration, cutover planning, and post-migration validation.
This guide covers migrating from SharePoint Server (2013, 2016, 2019) to SharePoint Online — assessment, content audit, site mapping, identity migration, tool selection, wave-based migration, cutover, and post-migration validation. EPC Group has completed 6,500+ SharePoint migrations. Free migration assessment available.
Key Facts
- SharePoint 2013 extended support ends in April 2026 — migrate now to avoid running unsupported software.
- Content rationalization removes 30–50% of migration volume (ROT content) before migration begins.
- SharePoint 2010 and 2013 workflows cannot be migrated — they must be rebuilt in Power Automate.
- InfoPath forms cannot be migrated — they must be converted to Power Apps.
- Migration tools: Microsoft SPMT (free), ShareGate (permissions), AvePoint Migrator (compliance reporting).
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Why Migrate from SharePoint Server to SharePoint Online Now
How do you migrate from SharePoint Server to SharePoint Online? Migrating to SharePoint Online involves a 6-phase process:
- Assessment: Inventory sites, customizations, and workflows.
- Content Audit: Identify and remove ROT content, which typically leads to a 30-50% reduction.
- Site Mapping: Design the target information architecture.
- Pilot Migration: Validate tools and benchmark throughput.
- Incremental Migration: Perform bulk copy with delta syncs to reduce downtime.
- Cutover with Validation: Execute final sync, URL redirect, and comprehensive testing.
EPC Group utilizes various tools for migrations:
- SPMT for small migrations
- ShareGate for most enterprise migrations
- Metalogix for complex environments
We have successfully migrated over 500 SharePoint environments, achieving 99.9% content integrity and minimal user downtime.
The time is running out for on-premises SharePoint. Support for SharePoint Server 2016 and 2019 ends in July 2026. After this date, Microsoft will not provide:
- Security patches
- Bug fixes
- Support
Using unsupported SharePoint can result in compliance issues for regulated industries. It is essential to adhere to standards like:
- HIPAA
- SOC 2
- PCI DSS
- FedRAMP
These standards require software that is supported and has up-to-date security patches.
Beyond compliance, the feature gap between SharePoint Server and SharePoint Online increases each month. SharePoint Online now offers:
- Copilot integration
- SharePoint Premium (formerly Syntex) for document intelligence
- Loop components for collaborative content
- Modern web parts that are years ahead of on-premises capabilities
Organizations that remain on-premises are falling behind in productivity and collaboration.
EPC Group has executed 500+ SharePoint migrations from versions 2007, 2010, 2013, 2016, and 2019 to SharePoint Online. This guide shares our complete enterprise migration methodology.
Migration Tools Comparison
Choosing the right migration tool depends on data volume, customization complexity, budget, and migration timeline requirements.
| Feature | SPMT (Free) | ShareGate | Metalogix (Quest) |
|---|---|---|---|
| Cost | Free | $10K-25K/year | $15K-40K+ |
| Source Versions | 2013, 2016, 2019 | 2007, 2010, 2013, 2016, 2019, SE | 2007, 2010, 2013, 2016, 2019, SE |
| Incremental Migration | Yes | Yes (excellent) | Yes |
| Pre-Migration Reports | Basic | Comprehensive | Comprehensive |
| Content Mapping | Basic (CSV) | Advanced (GUI + CSV) | Advanced (GUI) |
| Scheduling | Limited | Full scheduling | Full scheduling |
| Metadata Preservation | Good | Excellent | Excellent |
| Permission Migration | Basic | Full (with mapping) | Full (with mapping) |
| Workflow Migration | No | No (provides inventory) | Partial (Nintex only) |
| Throughput | Moderate | High (parallel streams) | High (parallel streams) |
| Best For | Small/medium, budget | Most enterprise migrations | Complex, highly customized |
EPC Group recommends ShareGate for 80% of enterprise migrations. It offers the best balance of capability, usability, and cost.
For smaller migrations or tight budgets, SPMT is a suitable choice. Metalogix is ideal for environments with heavy Nintex workflow usage or complex content mapping needs.
Phase 1: Assessment and Discovery
Assessment is crucial for a successful migration. If you skip this step, you may face migration blockers during the project. This can lead to weeks of rework and delays.
A thorough assessment typically takes 1-2 weeks. It helps avoid months of issues later on.
Site Collection Inventory
Document every site collection: URL, template type, owner, size, last modified date, number of sites and subsites, and content database. Generate a complete map of the source environment. For SharePoint 2013/2016/2019, use PowerShell with Get-SPSite and Get-SPWeb cmdlets. For older versions, use STSADM or third-party scanning tools. Typical enterprise environments have 50-500 site collections with 500-5,000 sites.
Customization Audit
Identify all customizations that will need special handling: farm solutions (WSP packages), sandboxed solutions, custom master pages, custom page layouts, SharePoint Designer workflows, InfoPath forms, custom web parts, BCS connections, and custom content types. Each customization must be categorized: migrate as-is (if supported), rebuild for SharePoint Online (SPFx, Power Automate, Power Apps), or retire (if no longer needed).
Content Analysis
Analyze content by: total size, file count, file types (identify unsupported types like .exe), large files (over 250 GB — SharePoint Online file size limit is 250 GB), long file paths (URL limit is 400 characters), special characters in file names that are not supported in SharePoint Online, and version history depth. Content analysis informs cleanup priorities and migration scheduling.
User and Permission Mapping
Map source Active Directory accounts to Azure AD accounts in the target tenant. Identify: accounts that exist in both AD and Azure AD (direct mapping), accounts only in AD (need Azure AD creation or hybrid sync), external accounts (need guest invitation in Azure AD), and service accounts used for automated processes (need Azure AD app registrations or managed identities). Permission mapping is the most tedious but most critical assessment task.
Phase 2: Content Audit and Cleanup
Before migration, cleaning up your content is crucial. Many organizations have years of accumulated ROT (Redundant, Obsolete, Trivial) content. Migrating this ROT can waste time and money.
Addressing this issue before migration is essential. If not, it can lead to a disorganized target environment.
Redundant Content
Typical: 15-25% of total content
- Duplicate files across multiple sites
- Multiple versions of the same document in different locations
- Copied team sites from old projects
- Exported reports that exist in the source system
Obsolete Content
Typical: 20-35% of total content
- Documents not accessed in 3+ years
- Content from departed employees
- Old project sites with no active stakeholders
- Superseded policies and procedures
- Archived sites that were never actually archived
Trivial Content
Typical: 5-15% of total content
- Temporary files and drafts
- Meeting notes for meetings held years ago
- Test sites and sandbox content
- Placeholder documents with no real content
- Screenshots and one-off images
EPC Group conducts content audits using automated scanning tools. These tools categorize each file based on:
- Freshness
- Owner status
- Duplication
- Usage patterns
Business owners receive a detailed report to support their decision-making. This process typically results in a 30-50% reduction in content.
As a result, the following benefits occur:
- Reduced migration duration
- Lower costs
- Decreased SharePoint Online storage usage
Phase 3: Site Mapping and Information Architecture
Migration is a chance to correct past mistakes in information architecture. Many on-premises SharePoint environments have developed over 10-15 years. This has led to:
- Deeply nested subsite hierarchies (5+ levels deep)
- Inconsistent navigation
- Duplicate sites for the same purpose
- No hub site structure
It is important to redesign the architecture for SharePoint Online before migrating content.
Flatten Subsite Hierarchies
SharePoint Online best practice is flat architecture: hub sites connect related sites through association, not through subsite nesting. Convert deep subsite trees into standalone sites associated with a hub. This improves performance, simplifies permissions, and enables modern site features that are not available on classic subsites.
Hub Site Design
Organize sites into hub site families: departmental hubs (HR Hub, Finance Hub, IT Hub), project portfolio hubs (all active project sites), and topic hubs (Compliance Hub, Training Hub). Hub sites provide: shared navigation across associated sites, cross-site search, consistent branding, and aggregated news and content. Plan 5-15 hub sites for a typical enterprise.
URL Planning
Design clean, consistent URLs for the target environment. Source: https://sharepoint.contoso.com/sites/HR/Benefits/2024/OpenEnrollment. Target: https://contoso.sharepoint.com/sites/HR-Benefits. Shorter URLs are easier to share, bookmark, and remember. Document the complete URL mapping for every source-to-destination site pair. This mapping drives the migration tool configuration.
Metadata and Content Type Strategy
Review and standardize managed metadata term sets before migration. Consolidate duplicate term sets. Plan content type inheritance from the content type hub. Decide which custom content types to migrate versus retire. Ensure column names and types are consistent across sites that will share content types in SharePoint Online.
Phases 4-5: Incremental Migration and Cutover
Incremental migration greatly reduces downtime. Instead of a large, single migration that takes days, this approach stages content over several weeks. It only needs a small delta sync during the cutover window.
Pilot Migration
Migrate 2-3 representative sites first: one simple team site, one complex site with custom content types, and one large document library. Validate: content integrity (file counts, metadata, versions), permission accuracy, migration throughput (GB per hour), and error handling. Use pilot results to estimate the full migration timeline and identify issues before scale.
Wave Planning
Organize sites into migration waves of 10-20 sites each. Wave criteria: department grouping (migrate entire departments together), dependency grouping (sites that link to each other migrate together), complexity grouping (simple sites first, complex sites later). Schedule waves 1-2 weeks apart to allow validation between waves.
Incremental Sync
After initial bulk copy, run daily incremental syncs that migrate only changed content. This ensures the target stays nearly current with the source. On cutover day, the final delta sync processes only changes since the last incremental run — typically completing in minutes for most sites. Configure migration tools to run incremental syncs during off-hours to avoid impacting source server performance.
Cutover Execution
Cutover checklist: 1) Set source sites to read-only, 2) Run final incremental sync, 3) Validate content integrity (automated comparison scripts), 4) Update DNS/URL redirects from old URLs to new URLs, 5) Send user communication with new URLs and training resources, 6) Monitor for 48 hours post-cutover with dedicated support team, 7) Decommission source after 30-day parallel run period.
Phase 6: Post-Migration Validation
Post-migration validation is essential. It determines whether a migration is successful or if it leads to more issues. This process must be systematic, documented, and include business users.
| Validation Area | What to Check | Method | Pass Criteria |
|---|---|---|---|
| Content Integrity | File counts, folder structure, metadata | Automated comparison scripts | 100% match (with documented exceptions) |
| Version History | Version count and content per version | Random sample (10% of files) | All sampled files match source versions |
| Permissions | Group membership, permission levels, inheritance | Test with users from each security group | Correct access for all tested roles |
| Metadata | Managed metadata, custom columns, content types | Automated metadata comparison | 100% metadata values match source |
| Search | Content indexed and searchable | Search for known documents | All searched items found within 24 hours |
| Workflows | Rebuilt Power Automate flows function correctly | End-to-end test for each workflow | All workflows complete successfully |
| User Acceptance | Business users can find and use content | Structured UAT with checklist | Stakeholder sign-off per department |
EPC Group post-migration validation includes automated comparison scripts that verify content integrity across every migrated site, plus structured UAT programs with department-specific checklists. We maintain a 30-day parallel run period where both source and target are available, ensuring a documented 5-day cutover average risk. See our complete SharePoint Online vs on-premises decision guide for additional migration planning resources.
Related Resources
SharePoint Consulting Services
Enterprise SharePoint implementation, migration, governance, and managed services from EPC Group.
Read moreSharePoint Online vs On-Premises
Decision framework for evaluating SharePoint Online versus on-premises deployment for your organization.
Read moreSharePoint Migration Services
Enterprise SharePoint migration consulting with proven methodology and 500+ successful migrations.
Read moreFrequently Asked Questions
How do you migrate from SharePoint Server to SharePoint Online?
SharePoint Server to SharePoint Online migration follows a 6-phase process: 1) Assessment — inventory all site collections, content databases, customizations, and workflows. Identify what migrates cleanly, what needs remediation, and what must be rebuilt. 2) Content audit — analyze content freshness, identify ROT (Redundant, Obsolete, Trivial) content for cleanup before migration. 3) Site mapping — design the target SharePoint Online information architecture, mapping source sites to destination sites with URL planning. 4) Pilot migration — migrate 2-3 representative sites to validate the migration tool, identify issues, and benchmark throughput. 5) Incremental migration — migrate content in waves using incremental (delta) sync to minimize cutover downtime. 6) Cutover and validation — final sync, DNS/URL redirect, and comprehensive post-migration testing. EPC Group has migrated 500+ enterprise SharePoint environments, from 2010 through 2019, to SharePoint Online.
What tools are available for SharePoint to SharePoint Online migration?
Three primary migration tools: 1) SharePoint Migration Tool (SPMT) — free Microsoft tool, good for small to medium migrations (under 100 GB), supports file shares and SharePoint 2013/2016/2019. Limited scheduling and reporting. 2) ShareGate (Migrate) — leading third-party tool, excellent for enterprise migrations, supports all SharePoint versions, provides detailed pre-migration reports, incremental migration, and scheduling. $10,000-25,000 annual license. 3) Metalogix (Quest Migration Manager) — enterprise-grade tool with advanced content mapping, workflow migration, and scheduling. Best for complex migrations with heavy customization. $15,000-40,000+. Also: Migration Manager in SharePoint Admin Center (cloud-based, good for file shares), and PowerShell with PnP Provisioning for template-based migrations. EPC Group typically uses ShareGate for 80% of enterprise migrations due to its balance of capability and usability.
How long does a SharePoint to SharePoint Online migration take?
Migration duration depends on data volume, complexity, and migration approach. Small environment (under 100 GB, 10-20 sites): 4-6 weeks. Medium environment (100 GB - 1 TB, 20-100 sites): 8-12 weeks. Large environment (1-10 TB, 100-500 sites): 12-24 weeks. Enterprise environment (10+ TB, 500+ sites): 6-12 months. Key timeline factors: content volume (migration throughput is typically 1-5 TB per week depending on throttling), customization complexity (custom solutions and workflows require rebuilding), content cleanup scope (ROT content removal can add weeks), user training and change management, and business availability windows for cutover. EPC Group accelerates timelines by 30-40% using parallel migration streams and pre-built migration automation scripts.
What cannot be migrated from SharePoint Server to SharePoint Online?
Items that cannot migrate directly and require rebuilding: 1) Server-side code (farm solutions, sandboxed solutions with code, custom timer jobs) — must be replaced with SPFx web parts, Power Automate flows, or Azure Functions. 2) InfoPath forms — must be replaced with Power Apps or SPFx solutions. 3) SharePoint Designer workflows — must be rebuilt in Power Automate. 4) Custom master pages — SharePoint Online uses modern experience; custom branding requires SPFx extensions. 5) BCS (Business Connectivity Services) connections — must be replaced with Power Automate connectors or custom SPFx solutions. 6) Access Services web databases — discontinued, must be migrated to Power Apps + Dataverse. Items that migrate with limitations: managed metadata (term store structure migrates, but term IDs change), content types (migrate but may need re-association), and alerts (do not migrate — users must re-subscribe).
Should we clean up content before or after migration?
Always clean up BEFORE migration. Migrating ROT (Redundant, Obsolete, Trivial) content wastes migration time, storage costs, and creates a messy target environment. Pre-migration cleanup process: 1) Run content analysis reports to identify: files not accessed in 3+ years, duplicate documents, empty sites with no content, versioning bloat (sites with 500+ versions per document), and orphaned content from departed employees. 2) Present findings to business owners for review and disposition decisions. 3) Archive or delete approved content before migration begins. Typical ROT reduction: 30-50% of content is unnecessary and can be archived or deleted. This means a 5 TB migration becomes a 2.5-3.5 TB migration — faster, cheaper, and cleaner. EPC Group content audits use automated scanning tools that categorize content by freshness, owner status, and usage patterns.
Why should we migrate from SharePoint Server now?
Three urgent reasons to migrate in 2026: 1) End of support — SharePoint Server 2016 mainstream support ended in 2021 (extended support ends July 2026). SharePoint 2019 mainstream support ends in 2024 (extended support ends July 2026). Running unsupported software means no security patches, no bug fixes, and audit/compliance risk. 2) Feature gap — SharePoint Online receives monthly feature updates including Copilot integration, SharePoint Premium (Syntex), Loop components, and modern web parts. On-premises versions receive no new features and fall further behind every month. 3) Cost — maintaining on-premises SharePoint farms requires: server hardware (refreshed every 4-5 years), SQL Server licenses, Windows Server licenses, backup infrastructure, disaster recovery infrastructure, and IT staff for patching and maintenance. SharePoint Online eliminates all of these with a per-user subscription model. EPC Group migration ROI analyses typically show 30-50% TCO reduction over 3 years.
What is incremental migration and why does it matter?
Incremental (delta) migration is a technique where the migration tool first copies all content to the destination, then on subsequent runs, only migrates items that have changed since the last run. This is critical for minimizing cutover downtime. Without incremental migration: all content must be migrated in a single pass during the cutover window, which could take days or weeks for large environments. With incremental migration: the initial bulk copy runs over days or weeks while users continue working on the source. On cutover day, only the delta (changes since the last sync) needs to migrate — typically completing in minutes to hours. Example: 5 TB environment, initial bulk copy takes 5 days. Daily incremental syncs take 1-2 hours. On cutover day, the final delta sync takes 30 minutes. Users experience less than 1 hour of downtime versus 5+ days without incremental migration. All three major tools (SPMT, ShareGate, Metalogix) support incremental migration.
How do you handle SharePoint workflows during migration?
SharePoint workflow migration is the most complex aspect of most migrations because workflows cannot migrate directly. Strategy by workflow type: 1) SharePoint 2010 workflows — must be rebuilt in Power Automate. These are the oldest and most common. Document the workflow logic, inputs, outputs, and triggers, then recreate using Power Automate cloud flows. 2) SharePoint 2013 workflows — also must be rebuilt in Power Automate. More complex than 2010 workflows but same migration approach. 3) SharePoint Designer workflows — cannot migrate. Rebuild in Power Automate with equivalent triggers and actions. 4) Nintex workflows — Nintex offers a migration tool (Nintex Automation Cloud) that can convert some on-premises Nintex workflows to cloud workflows, but complex workflows still require manual rebuilding. Best practice: inventory all workflows, categorize by complexity (simple approval, multi-stage, integration-heavy), prioritize by business criticality, and rebuild the most critical workflows first in Power Automate before cutover. EPC Group workflow migration teams typically rebuild 80% of workflows in Power Automate with improved functionality.
What post-migration validation should be performed?
Post-migration validation covers five areas: 1) Content integrity — verify file counts, folder structures, and metadata match between source and destination. Run checksums on a random sample of files. Verify version history migrated correctly. 2) Permission validation — confirm that SharePoint groups, permission levels, and individual permissions match the migration plan. Test access with representative users from each security group. 3) Functionality testing — verify document libraries, lists, views, content types, managed metadata, search, and navigation work correctly in SharePoint Online. 4) Workflow validation — test all rebuilt Power Automate flows with end-to-end scenarios. Verify triggers fire correctly and approvals route to the right people. 5) User acceptance — conduct structured UAT with business users from each department. Provide a checklist of items to verify and a feedback mechanism. Allow 1-2 weeks for UAT before decommissioning the source environment. EPC Group post-migration validation includes 100+ test cases per site collection and automated comparison scripts.
Plan Your SharePoint Migration
EPC Group migration assessments evaluate your on-premises SharePoint environment. We identify migration blockers and estimate both the timeline and cost. Our team also provides a clear migration roadmap.
With over 500 successful migrations, we know how to achieve success on the first attempt.
SharePoint to SharePoint Online Migration: Enterprise Guide 2026
This guide explains how to migrate from SharePoint Server (2013, 2016, 2019) to SharePoint Online. It includes:
- Assessment
- Content audit
- Site mapping
- Identity migration
- Tool selection
- Wave-based migration
- Cutover
- Post-migration validation
EPC Group has completed over 6,500 SharePoint migrations. A free migration assessment is available.
Migration Methodology: 6 Phases
EPC Group follows a 6-phase methodology for every SharePoint Server to SharePoint Online migration.
- Assessment — inventory all sites, customizations, and workflows using SMAT. Identify migration blockers: classic web parts, farm solutions, InfoPath forms, and 2010/2013 workflows.
- Content Audit — remove ROT content: redundant, obsolete, and trivial files. Most organizations have 30–50% ROT. Reduce migration scope before moving a single file.
- Site Mapping — design the target SharePoint Online information architecture. Map source site collections to SharePoint Online sites and Microsoft 365 Groups using the hub-spoke model.
- Pilot Migration — validate tools and benchmark throughput on 2–3 representative sites. Confirm permission mapping is correct before full execution.
- Incremental Migration — bulk copy in waves with delta syncs to capture changes during multi-week migrations. Execute 5–10 TB per wave.
- Cutover and Validation — final sync, URL redirects, comprehensive testing, and 30-day parallel run before decommissioning the on-premises farm.
Content Audit and Rationalization
Analyze existing content before migration. Migrate only what is needed — removing ROT saves time, money, and tool costs (migration tools charge per GB).
What to analyze
- Total size and file count per site collection.
- File types — identify unsupported types (.exe, .pst) and large file categories.
- Large files — SharePoint Online file size limit is 250 GB; files above this cannot be migrated directly.
- Long file paths — URL limit is 400 characters. Shorten deep folder paths before migration.
- Files with unsupported characters (# % & * : < > ? / \ |) — rename before migration.
- Version history depth — excessive versions inflate migration size; trim to 10–15 versions per document.
Content to remove before migration
- Content older than 3 years with no recent access — archive to SharePoint Server file share or delete.
- Duplicate files (typically 15–30% of total volume).
- Orphaned sites with no active owners — decommission before migration.
- Temporary and personal files that should be in OneDrive, not SharePoint.
Identity and Permissions Migration
Map on-premises Active Directory identities to Azure AD before migration begins. Permissions cannot be preserved without this step.
Identity mapping categories
- Direct mapping — accounts that exist in both on-premises AD and Azure AD via Azure AD Connect sync.
- Manual mapping — accounts only in on-premises AD that need Azure AD creation or hybrid sync setup.
- External accounts — need guest invitation in Azure AD before migration.
- Service accounts — used for automated processes; need corresponding Azure AD app registrations or managed identities.
Permission migration steps
- Export all SharePoint permission assignments from the source farm using PowerShell or a migration tool report.
- Map source user accounts and AD groups to their Azure AD equivalents.
- Configure Azure AD security groups to replace on-premises AD groups for SharePoint permissions.
- Validate permission mapping on the pilot migration sites before proceeding to full execution.
Customization Assessment
Classic SharePoint customizations cannot be directly migrated. Identify all of these before migration planning — each requires a separate remediation workstream.
- SharePoint 2010 workflows — must be rebuilt in Power Automate. Cannot be migrated directly.
- SharePoint 2013 workflows — must be rebuilt in Power Automate. Cannot be migrated directly.
- InfoPath forms — must be converted to Power Apps. Allow 1–2 weeks per complex form.
- Farm solutions and full-trust code — must be rebuilt in SharePoint Framework (SPFx). Allow 2–4 weeks per web part.
- Classic event receivers — replace with Power Automate flows or Azure Functions.
- Custom search configurations — must be manually reconfigured in Microsoft Search.
Cutover Checklist
Run this checklist for every migration wave cutover.
- Set source SharePoint sites to read-only — prevent content changes during final sync.
- Run final incremental sync — capture all changes made during the migration window.
- Validate content integrity — run automated comparison scripts: file counts, sizes, metadata, permissions.
- Update DNS and URL redirects — old SharePoint Server URLs redirect to new SharePoint Online URLs.
- Send user communications — include new URLs, training resources, and support channel information.
- Monitor for 48 hours post-cutover with a dedicated support team available for escalations.
- Decommission source after a 30-day parallel run period — confirm users are working in the new environment.
Post-Migration Validation
Validate across five dimensions before closing out each migration wave.
- Content integrity — file counts, sizes, and checksums match source to target.
- Metadata accuracy — all custom columns, content types, and managed metadata values are present.
- Permission correctness — user and group access matches the intended model, not just a copy of the source.
- Functionality — search returns expected results; Power Automate flows execute correctly; web parts render properly.
- Compliance — retention labels applied, sensitivity labels present, audit logging active.
Frequently Asked Questions
How long does a SharePoint Server to SharePoint Online migration take?
Migrations vary in size and duration. Small migrations, under 1 TB and involving a single site collection, usually take 4–6 weeks.
Mid-size migrations, which range from 1 to 10 TB and involve multiple site collections, usually take 8 to 12 weeks. Large enterprise migrations, exceeding 10 TB and involving over 10,000 users along with multiple compliance frameworks, typically require 12 to 16 weeks.
These large migrations often follow a phased wave rollout.
If significant workflow or InfoPath remediation is needed, add an additional 2–4 weeks to the timeline.
Can I migrate SharePoint workflows to Power Automate?
SharePoint 2010 and 2013 workflows cannot be migrated directly. They must be rebuilt in Power Automate.
To assist with this process, use the Microsoft Workflow Migration Tool. This tool will generate a report of all workflows and their trigger conditions.
Allow 1–4 weeks of rebuild time per workflow depending on logic complexity. EPC Group includes workflow assessment and migration in our SharePoint migration engagements.
What migration tool should I use for SharePoint Server to SharePoint Online?
For basic file migrations, use Microsoft SPMT (free). For migrations that involve many permissions, choose ShareGate. If you require detailed migration reporting in compliance-heavy environments, select AvePoint FLY.
For enterprises with over 10,000 users, EPC Group recommends a combination of all three tools. Each tool is used for the specific scenario it handles best.
What happens to SharePoint Server customizations during migration?
Classic web parts, farm solutions, InfoPath forms, and 2010/2013 workflows do not migrate automatically. They need manual remediation. This includes rebuilding in:
- SPFx for web parts
- Power Apps for InfoPath
- Power Automate for workflows
Identify all customizations during the assessment phase. This is the most common cause of migration timeline delays.
Get a Free Migration Assessment
Talk to a SharePoint migration architect about your source environment, customizations, and compliance requirements. Call (888) 381-9725 or request a free migration assessment.