Zero-Loss SharePoint Migration Runbook (2026)

Zero-Loss SharePoint Migration Runbook

The 32-step runbook EPC Group uses for SharePoint on-prem to SharePoint Online migrations. "Zero-loss" means: no content lost, no permission drift, no broken links from the user's perspective. Built from hundreds of Fortune 500 SharePoint migrations since 2003.

Scope. Covers SharePoint 2013/2016/2019 on-prem → SharePoint Online (M365) migrations. Adaptations noted for non-SharePoint source systems (Igloo, Jive, Confluence, custom CMS).

Quick Answer

Zero-loss SharePoint migration requires: (1) full pre-migration content audit + ROT removal, (2) Information Architecture remap (don't lift-and-shift legacy IA), (3) phased migration with parallel-run validation, (4) Purview label deployment BEFORE Copilot-eligible content arrives, (5) URL preservation strategy (redirects + crawl), (6) 60-day hypercare with named EPC Group + client team.

The 32-Step Runbook

Pre-Migration: Discovery + Design (Steps 1-10)

Step 1: Source System Inventory. Run SharePoint 2013/2016/2019 PowerShell Get-SPSite + Get-SPWebApplication for full topology. Capture: site counts, content database sizes, custom solutions (full-trust + sandboxed), workflows, content types.

Step 2: Content Audit + ROT Identification. Use ShareGate Insane Reports or SharePoint Migration Assessment Tool (SMAT). Identify Redundant + Outdated + Trivial content. Target: 30-60% reduction pre-migration.

Step 3: Permission Audit. Export full permission inheritance map. Identify orphaned permissions, broken inheritance, oversharing risks.

Step 4: Customization Audit. List all sandboxed solutions, full-trust solutions, custom workflows (SharePoint Designer + Nintex), branding (master pages + page layouts). Most customizations DO NOT migrate to SharePoint Online — must be re-platformed to SPFx + Power Automate.

Step 5: User + Group Mapping. Map on-prem Active Directory users to Entra ID identities. Resolve mismatches (renamed users, terminated users still referenced in permissions).

Step 6: Information Architecture Design. Don't lift-and-shift legacy IA. Design modern hub-based topology. EPC Group recommendation: 1 hub per business unit + topical hubs + cross-cutting policies.

Step 7: Site Provisioning Standards. Naming convention, URL pattern, default permissions, default sensitivity label, retention label.

Step 8: Branding + Page Templates. Modern SharePoint Online uses theme JSON + SPFx extensions + page templates. Migrate visual identity, not legacy master pages.

Step 9: Search + Findability Plan. Search verticals + result sources + refiners. Modern SharePoint Online search differs from on-prem Search Service Application.

Step 10: Governance + Copilot Readiness Plan. Purview sensitivity labels, retention labels, DLP, oversharing remediation runbook, Restricted SharePoint Search for sensitive content. Required BEFORE Microsoft 365 Copilot turn-on.

Migration Execution: Phased Rollout (Steps 11-22)

Step 11: Tooling Selection. ShareGate Migrate (most common), Microsoft Migration Manager + Mover (good for OneDrive + file shares), AvePoint FLY (high-customization environments). EPC Group reference: ShareGate for SharePoint, Migration Manager for OneDrive, FLY for complex Nintex workflows.

Step 12: Migration Environment Setup. Source connectivity, target tenant prep (sites pre-created, hubs configured, permissions seeded), migration tool licensing.

Step 13: Test Migration Wave. 10-50 sites + 5-25 users. Validate fidelity, performance, edge cases. Learn from this wave; do NOT skip.

Step 14: Test Wave Validation. Compare source vs target: content count, permission inheritance, customization rendering, user notification.

Step 15: Wave Planning. Group sites by business unit + dependency. Each wave 500-2,500 users + 100-500 sites. Pick non-conflicting workloads.

Step 16: Wave 1 Communications. 4-week heads-up + 1-week reminder + day-of cutover comms. Persona-tailored.

Step 17: Wave 1 Pre-Migration Snapshot. Source content + permission snapshot for rollback comparison.

Step 18: Wave 1 Migration Execution. Schedule outside business hours. Monitor migration tool dashboard. Pause + remediate failed items.

Step 19: Wave 1 Validation. Site-by-site walkthrough by named site owner. Sign-off required.

Step 20: Wave 1 Cutover. Source set to read-only, redirect to target, user notification.

Step 21: Wave 1 Hypercare. Named EPC Group + client team. 7-day intensive support. Top 5 issue categories triaged daily.

Step 22: Waves 2-N Iteration. Each subsequent wave benefits from learnings. Wave size can grow (500 → 1,500 → 2,500 → 5,000) as confidence builds.

Post-Migration: Validation + Hypercare (Steps 23-32)

Step 23: Full-Tenant Permission Audit. Compare source vs target permission state. Identify drift. Remediate orphaned permissions.

Step 24: Search + Crawl Validation. Confirm SharePoint Online search indexing complete. Modern Crawler should pick up new content within 24 hours.

Step 25: URL Preservation. Configure redirects for any legacy URL pattern users may have bookmarked. Audit external systems linking to legacy SharePoint.

Step 26: Purview Label Deployment. Apply container labels to all migrated sites. Autolabeling for regulated content. File-level labels propagate over 30-60 days.

Step 27: Copilot Readiness Validation. Oversharing audit + remediation. Restricted Search configuration. DLP for Copilot tested.

Step 28: User Adoption Coaching. Modern SharePoint Online UX differs from on-prem. Persona-based training, champion network, office hours.

Step 29: Custom Solution Re-Platform. SPFx replacements for legacy webparts. Power Automate flows replacing SharePoint Designer workflows. Document by-design changes.

Step 30: Source System Decommission. 90-day read-only retention before decommission. Snapshot + archive per retention policy.

Step 31: 60-Day Stabilization Review. Quantitative (search analytics, page analytics, Viva Insights) + qualitative (user surveys). Identify residual issues.

Step 32: Knowledge Transfer + Operational Handoff. EPC Group handoff to client IT operations team. Runbook for ongoing site provisioning, permission management, label maintenance.

Common Failure Modes

1. Lift-and-shift legacy IA. Modern SharePoint Online is hub-based; legacy SharePoint is top-down. Skipping IA redesign produces 50%+ adoption drop.
2. Custom solution dependency surprises. Sandboxed solutions, full-trust solutions, complex workflows. Inventory + replatform plan must be Phase 1.
3. Oversharing exposed by Modern Search. Modern Search surfaces content faster + broader than legacy. Required: oversharing audit + remediation BEFORE search index rebuilds.
4. Permission drift during migration. Even with disciplined tooling, edge cases create drift. Step 23 audit catches most.
5. Copilot turn-on without readiness. Microsoft 365 Copilot grounded on freshly-migrated content WILL surface oversharing if Step 27 was skipped.
6. No hypercare budget. First 30 days post-cutover are highest-friction. Named EPC Group + client team required.

Microsoft 365 E7 vs E5 for Migration + Copilot

Capability	E5 + Copilot Add-on	M365 E7
SharePoint Online	E5 included	E7 included
Microsoft Purview	E5 included	E7 included
Microsoft 365 Copilot	Add-on $30/user/mo	Bundled
Microsoft Agent 365	Add-on $45/user/mo	Bundled
Per user/month	$90+	$99 ($84.15 CSP promo through Dec 31 2026)

EPC Group recommendation: lock in M365 E7 + CSP promo for post-migration period (Copilot adoption + Agent 365 governance becomes operational).

Bottom Line

Zero-loss SharePoint migration is achievable with disciplined execution across 32 documented steps. Skipping pre-migration audit, IA redesign, or post-migration governance produces measurable adoption + compliance failures. EPC Group has executed this runbook on hundreds of Fortune 500 environments since 2003.

Frequently Asked Questions

Q: How long does a SharePoint migration take?
A: 6-18 months for enterprise (10,000+ users), 3-9 months for mid-market, 2-4 months for small. Multi-geography or regulated industries add 30-50%.

Q: How much does a SharePoint migration cost?
A: Tooling: $50K-$200K per environment (ShareGate, FLY, etc). Consulting: $200K-$1.5M depending on scope. Internal IT time: 1-3 FTEs full-time. Total: $300K-$3M+ for enterprise.

Q: Can we do this in-house?
A: Yes, with experienced SharePoint architects. Most clients combine internal team + EPC Group oversight + complex-customization specialists.

Q: What about Microsoft Teams content?
A: Teams content lives in SharePoint sites (each team = a site). Migrating SharePoint migrates Teams files. Teams chat history migrates separately.

Q: What about OneDrive for Business content?
A: Microsoft Migration Manager + Mover is the standard tool. Less complex than SharePoint sites.

Q: How do we minimize user downtime?
A: Weekend cutovers + read-only source + user comms 4 weeks out. Most users experience zero downtime; power users + admins experience minimal.

Q: Why EPC Group?
A: SharePoint consulting since 1997 (since SharePoint 2003 beta team). Hundreds of Fortune 500 migrations. Microsoft Press author. See /reviews.

Next Steps

• Schedule a SharePoint Migration Discovery: /contact
• Productized assessment: /services/sharepoint-governance-health-check
• Ongoing engagement: /services/sharepoint-governance-consulting
• Copilot-specific governance: /services/copilot-governance-consulting
• Call (888) 381-9725