# Nintex Workflow Complexity Calculator

Score the relative complexity of moving Nintex workflows into Power Automate and identify when a Flow Migrator-assisted path makes sense.

## How many workflows are in scope?
Include production workflows, retired-but-referenced workflows, and variations across sites.

- 1-10 workflows
- 11-50 workflows
- 50+ workflows

## How complex are the workflow actions?
Review branches, loops, approvals, escalations, item updates, and custom actions.

- Simple notifications or updates
- Approvals and branching
- Complex state, escalations, or integrations

## How many external dependencies exist?
Look for service accounts, mailboxes, APIs, SQL, external systems, webhooks, and file operations.

- Mostly SharePoint-native
- Several Microsoft 365 dependencies
- External systems or unclear credentials

## How business-critical are the workflows?
Assess operational impact if a workflow fails after migration.

- Low disruption
- Department-level disruption
- Operational, compliance, or executive escalation risk

## How clear is ownership?
Unowned workflows increase validation and support risk.

- Owners and validators known
- Some owners unclear
- Many orphaned workflows

## Is Power Platform governance ready?
Review environments, DLP, service accounts, monitoring, ALM, and support ownership.

- Governance in place
- Some standards missing
- No clear standards yet

## 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.