Cross-list lookup

What it does

This action works with SharePoint list items, files, folders, metadata, content approval, or permissions. The key migration inputs are the target site, list or library, field mappings, and any dynamic item identifiers.

How Flow Migrator maps it

Flow Migrator maps this to Mapped SharePoint read, result validation and typed assignment using SharePoint. Supports inline lookups in assignments, conditions and field bindings. Requires an explicit destination list/field, return representation and match policy. Preserves the original comparison operand. Missing values and invalid conversions stop the flow; repeated polling/loop-condition lookups require a separate refresh implementation. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Validate SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path behavior.
• Check converted expressions, branch ordering, loop exit conditions, and state-machine transitions.
• Run a test instance and compare outputs against the original Nintex workflow before production migration.

Validation checklist

1. Open the generated flow and confirm the action card imported correctly.
2. Validate connection references and required settings before running the flow.
3. Test with representative source data from the original workflow.
4. Confirm site/list/library names and complex field mappings in the target tenant.