Planning & ROI

How to interpret readiness score, effort, and savings

The readiness score and savings estimate are designed to make migration conversations easier, not to replace a technical assessment. They translate portfolio signals into a simple starting point for sales, scoping, and pilot planning.

6 min readUpdated May 22, 2026readiness scoresavingsestimate

Quick answer

In shortUnderstand how the assessment page turns workflow count, complexity signals, licensing inputs, and labor assumptions into a planning estimate.

Most likely causeThe readiness score combines the workflow estate size, available discovery assets, and complexity indicators such as approvals, state machines, databases, APIs, Nintex Tables, custom task forms, and child workflows.

What to do nextUse the checks below, then revisit the matching screen in Flow Migrator before you try again.

What the readiness score means

The readiness score combines the workflow estate size, available discovery assets, and complexity indicators such as approvals, state machines, databases, APIs, Nintex Tables, custom task forms, and child workflows.

A strong score means the customer is likely ready for a structured assessment and representative pilot. A lower score means the migration may still be attractive, but discovery and remediation planning should come first.

80 to 100: strong candidate for assessment and pilot.
60 to 79: good candidate with review areas.
40 to 59: complex migration that needs discovery first.
Below 40: inventory and remediation planning should lead the engagement.

How effort is positioned

The model is intentionally conservative but no longer treats every supported action as a long manual rebuild task. Supported actions are treated as generated mappings that need quick review. Most work is reserved for partial patterns, unsupported patterns, validation, and remediation.

Tool-assisted effort is lower because Flow Migrator handles the first-pass mapping, analysis report, package generation, and known pattern detection. Customer effort remains for validation, connection setup, owner sign-off, and complex remediation.

How to talk about savings

Use savings as a planning value until actual workflow exports have been analyzed. The strongest customer case usually combines labor savings, avoided or reduced Nintex renewal, better Power Platform standardization, and improved visibility into migration blockers.

If a customer already owns Microsoft 365 or Power Platform capacity, the licensing delta may be smaller. If premium connectors, Dataverse, custom connectors, or process licenses are needed, licensing should be reviewed separately.