Partner and ECIF motion
Support the partner-led project without disrupting the delivery model.
Flow Migrator is designed to fit into a Microsoft partner or SI-led migration program. Horton provides the migration assessment and conversion tooling while the partner remains the delivery, architecture, and customer success lead.
Partner operating model
| Role | Responsibilities |
|---|---|
| Microsoft / field team | Customer alignment, Microsoft strategy, ECIF process guidance, Power Platform success motion. |
| Systems integrator / MSP | Customer delivery lead, project management, environment strategy, architecture, testing coordination, cutover. |
| Horton / Flow Migrator | Assessment tooling, compatibility analysis, Power Automate limit-risk reporting, first-pass conversion, remediation guidance. |
| Customer | Workflow exports, owners, validation, target environments, connector credentials, gateway ownership, sign-off. |
Commercial engagement options
| Offer | What it includes |
|---|---|
| Assessment only | Portfolio upload, complexity scoring, compatibility report, Power Automate limit-risk findings, connector/gateway risk, remediation matrix, and wave recommendation. |
| Pilot conversion | 5–10 representative workflows, generated packages where supportable, import validation notes, dependency graph, remediation backlog, and go/no-go rollout recommendation. |
| Migration factory | Wave-based migration support, conversion triage, partner enablement, remediation guidance, and recurring portfolio reporting. |
ECIF-ready SOW outline
Horton can support an ECIF-funded motion when Microsoft and the customer choose that path. Eligibility and routing should be confirmed through Microsoft and the partner, while Horton provides scope, deliverables, and product-specialist support.
| SOW section | Recommended content |
|---|---|
| Objective | Assess and pilot Nintex-to-Power-Platform migration for representative workflows and produce a defendable migration approach. |
| Scope | Workflow export analysis, complexity scoring, Power Automate limit-risk reporting, pilot conversion, connector/gateway review, and remediation planning. |
| Deliverables | Assessment report, compatibility matrix, limit-risk summary, generated packages where supportable, remediation backlog, and migration wave plan. |
| Timeline | Typically 2–3 weeks for a representative pilot, depending on workflow access, validation availability, and customer security review. |
| Success criteria | Customer can understand migration effort, validate generated output, identify blockers, and decide on a broader migration factory motion. |