Enterprise pilot plan
Prove the migration path before committing to a full rebuild.
A good pilot does not only test a simple workflow. It should include the patterns most likely to affect enterprise delivery: approvals, child workflows, database/API dependencies, deep nesting, scheduled runs, and custom task forms.
Recommended pilot sample
Select 5–10 workflows that represent both ordinary work and the hardest edge cases.
| Workflow type | Why include it |
|---|---|
| Simple SharePoint workflow | Prove baseline trigger/action conversion, list mapping, and export/import workflow. |
| Approval or Flexi Task workflow | Validate approvers, outcomes, reminders, escalation assumptions, and task behavior. |
| Scheduled workflow | Validate recurrence, time zones, date/time expressions, and long-running behavior. |
| Database/API workflow | Validate premium connector, gateway, HTTP/custom connector, and remediation patterns. |
| Child workflow chain | Validate parent/child dependencies, callable-flow strategy, and packaging model. |
| Large or deeply nested workflow | Validate Power Automate platform-limit risk, splitting strategy, and maintainability. |
| Custom task form workflow | Validate whether Approvals, SharePoint task lists, Power Apps, or Teams patterns are appropriate. |
Inputs needed from the customer
- Nintex workflow exports or batch export ZIPs.
- Workflow owner and business unit for each pilot workflow.
- Known child workflow exports and reusable workflow names.
- Expected run frequency and volume for high-volume workflows.
- Non-production Power Platform environment for import validation.
- Connector and gateway owner contacts for remediation review.
Pilot deliverables
- Portfolio or pilot-workflow assessment report with supported, partial, and unsupported counts.
- Power Automate limit-risk report: estimated emitted actions, nesting, Switch cases, variables, request volume, run duration, and child workflow dependency risks.
- Connector, premium licensing, and gateway readiness summary.
- Dependency graph for parent/child workflows included in the pilot.
- First-pass Power Automate packages where mappings are supportable.
- Remediation backlog for partial and unsupported patterns.
- Pilot validation notes and recommendation for broader migration waves.
Pilot timeline
| Phase | Activity |
|---|---|
| Day 0–2 | Confirm security assumptions, collect workflow exports, choose representative workflow sample. |
| Day 3–5 | Run Flow Migrator assessment, review complexity bands, identify blockers and dependencies. |
| Day 6–10 | Generate first-pass packages for suitable workflows and validate imports in a non-production environment. |
| Day 11–15 | Document remediation patterns, packaging strategy, and migration factory recommendation. |
Success criteriaThe customer should finish the pilot with validated assessment data, import-tested flow packages where supported, a known remediation backlog, a child-workflow dependency strategy, and a defensible plan for migration waves.