Use these answers when security, architecture, partner delivery, or Microsoft field teams ask how Flow Migrator handles discovery, Power Automate limits, dependencies, packaging, and deployment.
The standard enterprise model is export-based assessment: the customer provides Nintex workflow exports or batch packages. Live NAC tenant inventory can be scoped separately if the customer approves the required NAC API/admin access and security review.
For export-based assessment, it does not authenticate to NAC. Customers upload exports. If live NAC inventory is requested, authentication, API access, and permissions must be defined as a separate enterprise discovery workstream.
Flow Migrator focuses on workflow migration. Forms and custom task forms are a related workstream. Horton can discuss Form Migrator patterns separately, but workflow conversion and form replacement should be scoped independently.
It detects form/list-start patterns and maps them to the closest target trigger, typically SharePoint item created/modified, manual trigger with inputs, or a parent/child pattern. Form payload behavior must be validated.
Unsupported actions are not silently skipped. They are flagged, documented, and where appropriate represented as reviewable placeholders so the customer and partner can remediate them deliberately.
Analyze includes Power Automate limit-risk scoring for detected source steps, estimated emitted actions, nesting depth, switch cases, variables, expressions, URLs, run duration, request volume, premium/gateway connectors, and child workflow dependencies.
It is flagged as a blocker or high-risk item. The recommended remediation is splitting into child flows, refactoring large sections, or packaging the work as a migration wave rather than a single one-shot import.
Child workflow calls are detected as dependencies. The preferred migration model is to convert shared child workflows once where possible, group parent/child flows in the same wave or solution, and flag missing child workflow exports.
Flow Migrator can generate importable packages and supports an enterprise packaging recommendation. The final ALM model—unmanaged for dev/test, managed for production, one solution per workflow, or wave-based packaging—should be validated with the customer’s Power Platform standards.
Yes. Generated output is standard Power Automate content intended to be reviewed, edited, and maintained by customer developers or partner consultants after import.
Assessment does not require tenant admin rights. Deployment requires appropriate environment access, permission to import/create flows or solutions, connector access, connection references, SharePoint permissions, gateway access for on-premises systems, and the required licenses.
Yes. The analysis flags premium/gateway-sensitive connectors and adds risk notes for connectors such as SQL Server, MySQL, Oracle, HTTP/custom connectors, Dataverse, File System, ODBC/OLE DB, and other enterprise integrations.
