Enterprise FAQ
Clear answers for Microsoft, partner, and customer architecture reviews.
These answers are designed for enterprise discovery calls where customers need to understand exactly what Flow Migrator can assess, what it can convert, and which patterns still need remediation or design decisions.
Assessment and NAC discovery
| Question | Answer |
|---|---|
| Does Flow Migrator scan the entire NAC tenant? | The standard model is export-based assessment: the customer uploads Nintex workflow exports or batch ZIPs. Live NAC inventory/API discovery can be scoped separately when the customer approves the required NAC API/admin access. |
| How does Flow Migrator authenticate to NAC? | Export-based assessment does not require Flow Migrator to authenticate to NAC. If live tenant discovery is requested, authentication, permissions, and data handling must be scoped with the customer security team. |
| What does the scan capture? | Trigger type, detected source steps, variables, branches, loops, connectors, child workflow references, Power Automate mapping, support status, platform-limit risks, and remediation notes. |
Forms and task forms
| Question | Answer |
|---|---|
| Does Flow Migrator convert Nintex Forms? | Flow Migrator focuses on workflow-to-Power-Automate migration. Forms should be treated as a related workstream. Horton can discuss Form Migrator separately, but workflow and form migration should be scoped independently. |
| Does it convert form-triggered workflows? | Yes, form-triggered workflows can be detected and mapped, but the target trigger depends on the architecture: SharePoint item trigger, manual trigger, parent/child flow, or review placeholder. |
| How are custom task forms handled? | Custom task forms are usually partial. Simple approvals may map to Power Automate Approvals; richer task data capture may need SharePoint task lists, Power Apps, Teams cards, or a custom pattern. |
Power Automate limits
| Question | Answer |
|---|---|
| How does the tool handle the 500-action limit? | Analyze shows detected source steps and estimated emitted Power Automate actions separately. Workflows above the generated-action threshold are flagged as blockers and recommended for splitting/refactoring. |
| How does it handle nesting beyond eight levels? | Flow Migrator reports source nesting depth and flags deep nesting. The generated flow may be flatter than the source, but workflows exceeding limits should be validated or refactored into child flows/stage patterns. |
| What happens to a 600-action workflow? | It is not truncated. It is assessed, flagged, and either generated with warnings where possible or recommended for split/refactor before export. |
Child workflows and reusable workflows
| Question | Answer |
|---|---|
| How are child workflow chains handled? | Start workflow actions are detected as child workflow dependencies. Target workflow names are extracted where available and included in dependency summaries. |
| What if a parent has many child workflows? | The recommended packaging model is parent/child solution packaging or wave-based packaging, with the child exports included in the same migration wave. |
| What if one child workflow is shared by many parents? | The preferred strategy is to convert the shared child once and wire parent flows to that child flow, rather than duplicating logic in every parent. |
Packaging, output, and deployment
| Question | Answer |
|---|---|
| Is the converted output editable? | Yes. Generated output is intended to be standard Power Automate content that customer developers can review and maintain after import. |
| Managed or unmanaged solutions? | Pilot packaging is usually unmanaged for development/test. The customer's ALM standards determine whether production promotion uses managed solutions, unmanaged packages, or wave-based solution packaging. |
| What permissions are needed in Power Platform? | Assessment does not require tenant admin rights. Import/deployment requires environment permissions, connector access, connection reference ownership, SharePoint access, gateway access where needed, and appropriate licensing. |