Sign up / Sign in
Enterprise pilot

Prove the Nintex migration path before committing to a portfolio rollout.

The recommended enterprise motion is a controlled pilot with representative workflows. The pilot validates assessment quality, Power Automate package generation, child workflow strategy, connector and gateway requirements, and the true remediation backlog before broad migration waves.

Start batch assessmentEstimate ROI

Pilot sample selection

Select 5–10 workflows that represent the customer’s real portfolio, not only the easiest cases.

  • One simple SharePoint workflow
  • One approval or task outcome workflow
  • One scheduled workflow
  • One database or API workflow
  • One parent workflow with child workflow dependencies
  • One large or deeply nested workflow
  • One workflow with custom task form or complex value capture, if available

NAC discovery approach

The current recommended model is export-based assessment. Customers provide Nintex Automation Cloud exports or a batch of workflow exports. If the customer wants live NAC tenant inventory, that should be scoped separately with customer-approved NAC API/admin access and security review.

Export-based firstLive NAC inventory optionalSecurity-scoped
DeliverableWhat the customer receives
Assessment evidencePortfolio and workflow-level scoring, supported/partial/unsupported counts, connector risks, Power Automate limit risks, and child workflow dependency findings.
Conversion outputImportable Power Automate packages where the mappings are supportable, plus placeholder/remediation notes for partial patterns.
Remediation backlogA prioritized list of child-flow, task-form, database, API, Nintex Tables, nesting, and runtime-risk items for the partner/customer team.
Packaging guidanceRecommended package model: single workflow package, wave-based solution, parent/child grouped solution, or split/refactor before export.

Partner operating model

  • Implementation partner: customer delivery, architecture, PMO, validation, deployment, and environment strategy.
  • Horton / Flow Migrator: assessment tooling, conversion engine, package support, compatibility guidance, and remediation interpretation.
  • Customer: workflow exports, owners, testing, connector credentials, licensing, and production sign-off.

Engagement options

  • Assessment: portfolio scoring, risk report, wave recommendations.
  • Pilot conversion: 5–10 representative workflows and import validation notes.
  • Migration factory: batch assessment, package generation, remediation support, and partner delivery enablement.

ECIF / SOW outline

  • Objective and pilot scope.
  • Workflow sample list and required inputs.
  • Deliverables and success criteria.
  • Customer, partner, Horton, and Microsoft responsibilities.
  • Timeline, assumptions, and out-of-scope items.