First 30 days: discover and stabilize the plan
- ✓Confirm SharePoint farm versions, patch levels, topology, content databases, site collection counts, storage, search dependencies, service applications, custom solutions, and third-party dependencies.
- ✓Create a business-criticality model. Start with systems that would cause operational disruption, compliance exposure, or executive escalation if unavailable.
- ✓Inventory InfoPath forms, Nintex workflows, SharePoint Designer workflows, custom scripts, timer jobs, event receivers, reports, and line-of-business integrations.
- ✓Decide the target path for each major site collection: SharePoint Online, Teams-connected SharePoint, SharePoint Server Subscription Edition, hybrid, archive, or retirement.
Next 60 days: design and remediate
- ✓Build a source-to-target mapping workbook with site owner, business owner, target URL, target hub, permission model, migration wave, dependencies, and validation owner.
- ✓Run pilot migrations for representative site types: publishing-heavy sites, document-heavy libraries, forms-heavy processes, workflow-heavy processes, and sites with complex permissions.
- ✓Define destination information architecture, hub sites, navigation, Teams mapping, retention, labels, external sharing, and ownership responsibilities.
- ✓Start remediation on high-risk issues: orphaned owners, broken inheritance, unsupported templates, oversized libraries, long paths, checked-out files, legacy workflows, and stale forms.
Product accelerator
Move legacy forms with Form Migrator
For organizations with InfoPath or legacy form sprawl, Form Migrator gives the modernization effort a product-led path instead of a one-form-at-a-time rebuild cycle.
Where Form Migrator fits
- ✓Inventory and rationalize forms before rebuilding them in Microsoft-native patterns.
- ✓Prioritize high-value forms by business criticality, usage, data complexity, and owner readiness.
- ✓Support a repeatable migration motion across Power Apps, Power Automate, SharePoint, Dataverse, and governance workstreams.
Product accelerator
Move Nintex workflows with Flow Migrator
For teams moving Nintex and legacy workflow estates into Power Automate, Flow Migrator helps turn discovery, mapping, and rebuild planning into a repeatable migration motion.
Where Flow Migrator fits
- ✓Identify workflow candidates, dependencies, owners, triggers, approvals, and failure points.
- ✓Separate direct rebuilds from processes that need redesign, governance, or integration architecture.
- ✓Accelerate migration planning from Nintex into supportable Power Automate patterns.
Final 30 days before production waves
- ✓Freeze or control source changes for sites entering active migration waves.
- ✓Validate migrated content, metadata, permissions, links, search, workflows, forms, page layouts, owner access, and user instructions.
- ✓Prepare hypercare coverage, issue intake, escalation paths, admin runbooks, and post-migration governance backlog.
- ✓Hold a go/no-go review for each wave with migration lead, technical owner, business owner, support lead, and communications owner.
Where forms and workflows fit
SharePoint end-of-support projects often fail when forms and workflows are treated as edge cases. They are usually the business process. Make them first-class workstreams with owners, product accelerators, and explicit replacement paths.
- ✓Use Form Migrator to create a repeatable path for InfoPath and legacy forms that need to become Power Apps, SharePoint forms, Dataverse apps, or other Microsoft-native experiences.
- ✓Use Flow Migrator to organize Nintex and legacy workflow migration into Power Automate with discovery, prioritization, and rebuild planning.
- ✓Do not migrate forms and workflows last. Their dependencies should shape content wave sequencing and business validation.
Reference notes