User Defined Action (UDA)

What it does

This action communicates with people or looks up Microsoft 365 user data. Migration review should focus on recipients, dynamic identities, message content, and connector permissions.

How Flow Migrator maps it

Flow Migrator maps this to Reviewable Scope / separately migrated child flow using Control / Power Automate. The .nwf file identifies the UDA call and input/output field references, but it does not embed the UDA workflow definition. Flow Migrator preserves the call as a reviewable Scope; export the UDA definition separately and replace the Scope with equivalent native actions or a child flow. Flow Migrator can preserve and generate the core mapping, but this action should be reviewed after import.

Common migration issues

• Review the generated action after import because some Nintex behavior does not map one-to-one to Power Automate.
• Validate SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path behavior.
• Run a test instance and compare outputs against the original Nintex workflow before production migration.

Validation checklist

1. Review this item before export or immediately after import.
2. Open the generated flow and confirm the action card imported correctly.
3. Validate connection references and required settings before running the flow.
4. Test with representative source data from the original workflow.