Governance decisions
- Environment strategy: default environment, departmental environments, dedicated migration environments, production environments, and admin-only environments.
- DLP policies: business connectors, non-business connectors, blocked connectors, premium connector review, and exception handling.
- Ownership model: app owner, flow owner, business owner, technical support owner, service account owner, and backup owner.
- ALM model: unmanaged prototype, managed solution, deployment pipeline, environment variables, connection references, and release notes.
Migration intake standard
- Every replacement should document source process, target process, owner, users, data sources, connectors, permissions, retention, and support expectations.
- Forms should identify target pattern: SharePoint form, Power Apps canvas app, model-driven app, Dataverse, Microsoft Forms, or retire.
- Workflows should identify trigger, actions, approvals, error handling, logging, retry behavior, and escalation path.
- Product-backed migrations should show where Form Migrator or Flow Migrator feeds the backlog and reporting process.
Migration software
Form MigratorInventory and plan legacy form migrations with Form Migrator
Form Migrator helps teams analyze InfoPath and legacy form estates, identify dependencies, and organize which forms should be converted, redesigned, simplified, or retired.
Migration software
Flow MigratorAnalyze and plan Nintex migrations with Flow Migrator
Flow Migrator analyzes Nintex workflow exports, identifies actions and dependencies, and helps teams organize supported conversions and workflows that need redesign.
Operational controls
- Create monitoring for critical flows, expired connections, disabled owners, failed runs, premium connector changes, and orphaned apps.
- Define change management for production apps and flows, including UAT, approvals, rollback, and communications.
- Review security, sharing, and connector use after cutover and on a recurring cadence.