How OLE DB, ODBC, and AS400-style queries are handled
Nintex on-premises workflows can use provider-based database actions such as OLE DB, ODBC, and AS400 or IBM i connections. Power Automate does not have a single generic OLE DB or ODBC action that safely replaces every provider, so Flow Migrator treats these as partial integration patterns.
7 min readUpdated May 22, 2026OLE DBODBCAS400
Quick answer
In shortUnderstand why generic provider-based database actions are marked partial and how to choose a replacement target.
Most likely causeProvider-based actions hide the real integration contract inside a connection string, driver, query, stored procedure, or business-system convention. The safest migration output is a reviewable placeholder that preserves the provider, connection reference, query text, and output variables.
What to do nextConfirm the connector family first, then test the target connection before you rely on the exported flow.
Why these actions are partial
Provider-based actions hide the real integration contract inside a connection string, driver, query, stored procedure, or business-system convention. The safest migration output is a reviewable placeholder that preserves the provider, connection reference, query text, and output variables.
This prevents a false supported classification when the actual target might be DB2, Oracle, SQL Server, an API wrapper, or a custom connector.
Common remediation options
- Use a native database connector when the backend is clearly SQL Server, MySQL, Oracle, PostgreSQL, or DB2 and the operation is simple.
- Create a stored procedure, view, or API wrapper when the source query is complex or business-critical.
- Use HTTP/custom connector when the target system already has an API or when direct database access is not desired.
- Move lookup/configuration data into SharePoint, Dataverse, or SQL when the original query was only supporting workflow configuration.
How to scope the review
- Identify the provider and connection constant used by the Nintex action.
- Capture the query, parameters, and output variables.
- Confirm whether the data source is system of record, lookup/configuration data, or transient workflow data.
- Choose the target connector or API pattern before promising an automated conversion.
Complex FRN, AS400, or IBM i queries are often better handled as integration remediation work rather than simple connector replacement.