How SQL Server and MySQL actions are converted
Flow Migrator now recognizes common SQL Server and MySQL row/table patterns and maps them to native Power Automate connector actions where the source action provides enough information to choose a safe target.
Supported database patterns
For SQL Server and MySQL, the strongest mappings are table and row CRUD operations. Recognized patterns can map to get tables, get rows, get row, insert row, update row, and delete row actions.
Stored procedure and raw-query patterns need more review because connector support, parameters, gateway access, and return shapes differ across customer environments.
- Query rows maps to Get rows when table and filter information are clear.
- Get row maps to Get row when a primary key or row identifier can be identified.
- Create, update, and delete map best when target table and row identity are explicit.
- On-premises databases normally require gateway planning and connection validation.
Why some database rows remain partial
Database actions become partial when the source query is too custom, the row identifier is unclear, the table schema is unknown, or the source provider uses OLE DB/ODBC instead of a native connector family.
Partial does not mean the workflow is a poor migration candidate. It means the database step should be validated with the customer database owner before import.
What to validate with the customer
- Confirm the destination database connector and whether it is cloud or on-premises.
- Confirm table names, primary keys, and column mappings.
- Confirm gateway availability, credentials, and driver requirements.
- Test the generated flow in a non-production environment before using it in production.