Workflow facts to capture
- Workflow name, site URL, list or library, trigger type, owner, process owner, validation owner, and last successful run.
- Core actions: approvals, emails, tasks, status updates, item creation, document generation, permission changes, or external calls.
- Inputs and outputs: fields used, documents touched, forms involved, reports fed, and notifications produced.
- Failure behavior: who is alerted, what users see, whether retries exist, and what business impact occurs.
Complexity signals
- Multiple approval branches, escalations, reassignments, reminders, or approval outcome dependencies.
- External system calls, custom web services, on-prem data, credentials embedded in actions, or third-party connectors.
- Long-running state, pause-until logic, parallel branches, custom code, or document generation requirements.
- Regulated records, finance approvals, HR decisions, customer commitments, or audit requirements.
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.
How to prepare for Flow Migrator
- Group workflows by process family so similar patterns can be migrated together.
- Mark workflow candidates as direct rebuild, redesign, retire, consolidate, or exception.
- Prioritize workflows that block SharePoint Online migration or create support risk if left behind.