Delete SQL record(s)

What it does

This action reads from, writes to, or queries a database-style data source. The migration depends on the original provider, table or query shape, credentials, gateway requirements, and how returned values are used later in the workflow.

How Flow Migrator maps it

Flow Migrator maps this to Delete row (V2), sometimes with Get rows + Apply to each using SQL Server. Direct row IDs map to Delete row. Filter-based deletes generate Get rows + Apply to each + Delete row and should be reviewed. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Confirm connection references, gateway setup, server/database names, table names, primary keys, credentials, and returned result shape.
• 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 gateway connectivity, primary key handling, query filters, and returned data shape.