Assessment only
Portfolio upload, complexity scoring, compatibility report, Power Automate limit-risk summary, connector/gateway review, and remediation matrix.
Partner operating model
Support the migration team already on the account.
Flow Migrator is designed to complement Microsoft partners and SIs. Horton Scientific supplies the migration assessment and conversion tooling while the delivery partner leads architecture, stakeholder management, environment strategy, and implementation.
Roles and responsibilities
| Party | Primary role | Typical responsibilities |
|---|---|---|
| Microsoft | Customer sponsor and platform alignment | Customer introduction, Power Platform guidance, funding/program alignment, and account coordination. |
| Implementation partner / SI / MSP | Delivery owner | Project management, architecture, environment planning, security review, ALM, deployment, UAT, training, and production support. |
| Horton Scientific / Flow Migrator | Migration tooling specialist | Assessment tooling, compatibility analysis, Power Automate package generation, limit-risk reporting, conversion guidance, and remediation recommendations. |
| Customer | Business and technical owner | Nintex exports, workflow owner input, validation scenarios, connector credentials, environment access, and final sign-off. |
Commercial motions
Pilot conversion
Representative 5–10 workflow pilot with generated packages, import validation notes, child-flow dependency review, and production migration estimate.
Migration factory
Wave-based assessment, conversion support, remediation guidance, partner enablement, and ongoing compatibility advisory across the portfolio.
SOW outline
What to include
- Workflow inventory and export intake.
- Assessment report and complexity scoring.
- Power Automate limit-risk and dependency reporting.
- First-pass package generation where supportable.
- Remediation backlog and wave recommendation.
How to measure the pilot
- Customer can see which workflows are simple, medium, complex, or blocker.
- Representative workflows import or produce clear remediation findings.
- Connector/gateway and premium licensing risks are visible.
- Parent/child workflow dependencies are understood before packaging.
- Partner has a repeatable plan for migration waves.