Migrate from Informatica to QueryFlow

Export the mapping. Drop it in. Done.

By Chris Davidson, founder of yForest · Updated September 26, 2026

The Migrate wizard reads your Informatica mapping export and builds an equivalent QueryFlow pipeline — sources, targets, and field mapping already drawn. You review it, then run it. Enterprise licensing down to $199.99/yr.

No credit card. 14 days. Cancel in one click.

macOS 15+ · Apple Silicon native · 14-day free trial · No credit card

How the Migrate wizard works

Export the mapping for the workflow you want to move — from PowerCenter's Designer (Repository → Export Objects) or from Informatica Cloud's mapping designer. In QueryFlow, open Data Sync and choose Migrate from the source menu. Drop the exported mapping file in. QueryFlow reads the source and target definitions and the port-to-port field mapping, then builds a pipeline that matches — source card, destination card, and the fields already connected.

QueryFlow Data Sync home screen showing the Migrate from another ETL entry point — The Migrate entry point lives in Data Sync, next to New Pipeline.

The review step

Nothing runs automatically. After import, QueryFlow drops you on a review screen: every source port mapped to a destination column, the sync mode it inferred, and any fields it couldn't confidently match — those show up flagged for you to fix by hand in the Bezier field mapper. This is where mismatched types or renamed columns from complex Informatica mappings get caught before a live run.

QueryFlow Bezier field mapping between source and destination columns — Field mapping after import — edit any connection before the first run.

What carries over

Source and target connections, straight port-to-port field mapping, simple renames, and type casts import cleanly. Incremental loads keep their key column. Retries and alerts (email, Slack, or webhook) get set up on the new pipeline using QueryFlow's defaults. Upsert with key fields is supported if the Informatica mapping used a similar update strategy. A dry run is available before you commit to a live schedule.

What does not carry over

Be honest with yourself about these before you migrate: Informatica's Aggregator, Joiner, Lookup, and custom Expression transformations do not import — that logic has to be rebuilt in a Flow Book (SQL + Python) or in your warehouse after load. Mainframe sources and Informatica's broader enterprise connector catalog have no QueryFlow equivalent — QueryFlow's source list is Snowflake, Redshift, Postgres, MySQL, BigQuery, Databricks, Google Sheets, Salesforce, and CSV/TSV. Informatica's metadata catalog, lineage tracking, and governance tooling don't have a QueryFlow counterpart at all.

Sources and destinations QueryFlow supports

Sources: Snowflake, Redshift, Postgres, MySQL, BigQuery, Databricks, Google Sheets, Salesforce, CSV/TSV. Destinations: S3, SFTP, local CSV, email, Salesforce, Snowflake, Redshift, Postgres, MySQL, BigQuery, Databricks. Informatica workflows that move data between systems on this list are good migration candidates. Workflows built around mainframe extracts, complex multi-stage transformations, or Informatica's governance features should stay on Informatica, at least for now.

The cost comparison

Informatica doesn't publish list pricing — it's sold on an enterprise quote that typically lands in the five figures a year once you include connectors, compute, and support. QueryFlow Pipelines is $199.99/year flat, with no quote process and no per-connector add-ons. For the subset of workflows that fit QueryFlow's connector list, migrating them off Informatica removes that quote line entirely.

Migrating off legacy ETL

Frequently asked

What exactly do I export from Informatica?

The mapping XML for the workflow you want to migrate — source and target definitions, port-to-port field mapping, and transformation metadata, exported from PowerCenter or Informatica Cloud's mapping designer.

Will complex Informatica transformations migrate?

Simple ones do — renames, type casts, straight port mappings. Aggregator, Joiner, Lookup, and Expression transformations with custom logic do not import; you rebuild that logic in a Flow Book (SQL + Python) after the basic pipeline is in place.

What does QueryFlow not support that Informatica does?

Informatica's mainframe and legacy enterprise source connectors, its full metadata catalog and lineage tooling, and complex multi-stage transformation pipelines aren't in QueryFlow. QueryFlow covers Snowflake, Redshift, Postgres, MySQL, BigQuery, Databricks, Google Sheets, Salesforce, and CSV/TSV as sources — if your Informatica workflows sit inside that list, migration is straightforward.

How much does Informatica actually cost compared to QueryFlow?

Informatica is sold on an enterprise quote, typically five figures a year once you include connectors and support. QueryFlow Pipelines is $199.99/year flat, no negotiation, no per-connector add-ons.

Do I need to migrate everything at once?

No. Migrate the workflows that fit QueryFlow's connector list first, run them in parallel with Informatica for a cycle to confirm the output matches, then retire the Informatica workflow. Keep anything relying on unsupported connectors or transformations on Informatica.