Snowflake ETL tools compared: the best Snowflake data integration software and connectors
Eleven ways to get data into Snowflake and keep it current, lined up by how each one runs, what it connects to, how it bills and who it is wrong for. Snowflake shipped its own ingestion service, Openflow, in November 2025, which changes the shortlist and makes most published comparisons of this category out of date. Below: the four native loading paths with the numbers from Snowflake's own documentation, then the tools that wrap them.
Field mapping auto-plugged · tap a port to rewire
Plug a source port into
Transform on this cable
JSON in
JSON out
5 sample records ready
Snowflake documentation read 13 August 2026 · Last updated August 2026
Which Snowflake ETL tool should you use?
Pick by which problem you actually have. If you want the widest managed connector catalog and no pipeline maintenance, Fivetran is the default and you accept a metered bill. If you want catalog breadth with control over where it runs, Airbyte is open source and self-hostable. If you want transformation in a visual canvas pushed down into Snowflake compute, Matillion was built for exactly that. If you want ingestion governed and billed inside your Snowflake contract, Snowflake Openflow is now first-party and generally available. And if the requirement is a handful of dependable scheduled syncs with field mapping an analyst can edit and a bill that does not move, Adapters is flat at $49 to $399 a month.
One correction worth making early, because it appears in most articles ranking for this term: Snowflake does now have its own ETL tooling. Openflow, built on Apache NiFi, went generally available for Snowflake Deployments on 4 November 2025, and its Oracle connector followed on 27 February 2026. Any comparison that opens with "Snowflake has no native ingestion tool" was written before that and should be read with the date in mind. For the broader category outside Snowflake specifically, start with best data integration tools.
Snowflake ETL tools compared
Billing units rather than price tags, because almost everything in this category is volume-metered and quote-driven. The one flat published figure below is ours. Verify current numbers with each vendor before you sign anything.
| Tool | Where it runs | Approach | Connects to | Pricing model | Best for |
|---|---|---|---|---|---|
| Snowflake Openflow | Inside Snowflake on SPCS, or BYOC in your own cloud | Managed ingestion, batch and streaming, CDC on databases | Dozens of prebuilt connectors: Postgres, MySQL, SQL Server, Oracle, MongoDB, Salesforce, Kafka, Shopify and more | Snowflake compute and storage consumption, on your existing contract | Teams that want ingestion billed and governed inside Snowflake itself |
| Fivetran | Managed cloud | Automated ELT with schema drift handling | The largest managed connector catalog, plus database CDC | Monthly active rows for connections, model runs for transformations | Teams that want zero pipeline maintenance and will pay a metered bill for it |
| Airbyte | Open source self-hosted, or Airbyte Cloud | ELT, with a connector development kit for anything missing | Very large catalog, community and certified connectors | Free self-hosted, or Cloud billed by credits tied to rows and volume | Engineering teams that want catalog breadth and control over where it runs |
| Matillion | Managed cloud, transformations pushed down into Snowflake | Visual ELT built specifically for cloud warehouses | Connectors plus a strong graphical transformation layer | Credit-based consumption | Teams that want transformation logic in a visual canvas rather than in SQL files |
| Estuary | Managed cloud or private deployment | Streaming CDC with real-time and batch destinations | Databases and SaaS, streaming-first | Usage based, by connector and data volume | Sub-minute freshness requirements into Snowflake |
| Hevo Data | Managed cloud | No-code ELT with in-flight transformations | SaaS applications and databases | Tiered by events loaded per month | Marketing and analytics teams without a data engineer on staff |
| Stitch | Managed cloud, part of Talend and now Qlik | Simple ELT built on the Singer standard | A steady mid-sized catalog | Tiered by rows replicated per month | Straightforward replication where simplicity beats features |
| Informatica | Managed cloud, enterprise deployment options | Full ETL and ELT with governance, quality and lineage | Very broad, including mainframe and legacy systems | Consumption units across the platform | Regulated enterprises that are buying governance as much as movement |
| AWS Glue | Serverless inside AWS | Spark-based ETL, code-first with a visual option | AWS services and JDBC sources, Snowflake as a target | Per data processing unit hour | Shops already standardized on AWS tooling and Spark skills |
| dbt | Open source Core, or dbt Cloud | Transformation only. It does not move data | None. It models what is already in Snowflake | Free Core, or seat-based Cloud | The T in ELT, paired with any of the loaders above |
| Adapters | Managed cloud, scheduled sync | Visual field mapping and no-code transforms, both directions | Postgres, MySQL, SQL Server, Redshift, BigQuery, Salesforce, HubSpot, NetSuite, Stripe, Shopify, QuickBooks, Xero and more | Flat monthly price: $49, $149, $399, or Enterprise | Ops and finance teams that want a predictable bill and mappings an analyst can edit |
The column the table cannot show you is connector depth. Two vendors will both list Salesforce and only one will replicate the custom object with the formula field you actually report on. During the trial, sync the exact tables you need and read what landed, rather than trusting the logo on the connector page. Salesforce is the source this bites hardest on, and the vendors that handle it well are lined up on Salesforce integration tools.
The four native ways to load data into Snowflake
Every tool in the comparison above is ultimately driving one of these four paths. Knowing which one your vendor uses tells you more about latency and cost than any feature list. Details below were read from Snowflake's own documentation on 13 August 2026.
| Method | Shape | Latency | Compute | Use it for | The catch |
|---|---|---|---|---|---|
| COPY INTO | Bulk load from a stage | Whenever you schedule it | Your own virtual warehouse | Nightly batch loads, historical backfills, one-off migrations | A single COPY job loading millions of files can hit the 24 hour default job timeout, so split very large jobs |
| Snowpipe | Continuous micro-batch from files | Typically within a minute of the file notification | Serverless, per-second billing | Files landing in S3, GCS or Azure throughout the day | Better than COPY for highly concurrent loads into the same table, because it manages table metadata for parallel operations |
| Snowpipe Streaming | Rows written directly, no staged files | Lowest of the file-free options | Serverless | Event streams and application writes that should not be batched into files first | You give up the file-level replay story that staged loading gives you |
| Openflow and third-party connectors | Configured source, managed pipeline | Scheduled or CDC, depending on the connector | Snowflake compute for Openflow, vendor infrastructure for the rest | Replicating a production database or a SaaS application without writing load code | You inherit the connector vendor schema decisions, so check how it names and types columns before you build on it |
File sizing is the lever most teams never touch and it is worth more than a tool change. Snowflake recommends producing data files roughly 100 to 250 MB compressed, because load parallelism is bounded by how many files you give it, and it explicitly advises against loading files of 100 GB or larger. If your loads are slow and your warehouse is already large, count the files before you resize the warehouse. The step-by-step version of all of this is in our guide to how to load data into Snowflake.
What changed in the Snowflake ingestion category
Six dated facts, each read from a primary source on 13 August 2026. If a comparison you are reading still describes Snowflake as having no first-party ingestion product, check when it was written.
Nov 2025
Snowflake Openflow reached general availability
Openflow Snowflake Deployments, running on Snowpark Container Services, went GA on 4 November 2025. Snowflake now ships first-party ingestion. Source: Snowflake release notes.
Apache NiFi
What Openflow is built on
Openflow is built on Apache NiFi, so the processor model and extensibility are open source lineage rather than a closed engine. Source: Snowflake Openflow documentation.
Feb 2026
Openflow Connector for Oracle went GA
Announced 27 February 2026, replicating Oracle tables into Snowflake in near real time using change data capture. The database connector set is filling in fast.
100 to 250 MB
Snowflake recommended file size, compressed
The single most common cause of slow loads is thousands of tiny files. Snowflake also states that loading very large files, 100 GB or larger, is not recommended. Source: Snowflake data loading docs.
128 MB
Maximum size of a VARIANT, VARCHAR or ARRAY value
BINARY caps at 64 MB, and VARCHAR defaults to 16 MB unless you declare it larger. Worth knowing before you load wide JSON documents. Source: Snowflake documentation.
$49/mo
Adapters entry price, flat
No monthly active rows, no credits, no per-connector charge. The bill is the same whether the sync moves 400 rows or 400,000.
How a Snowflake pipeline should be built, step by step
Five decisions that decide whether the pipeline is boring or a recurring incident. The tool you pick affects how much of this it does for you, but none of them do all five.
Step 01 / Land
Get the raw data into Snowflake first
Resist transforming on the way in. Land source data as close to raw as you can, in its own schema, and let Snowflake compute do the reshaping afterwards. Raw landing zones are what make a pipeline replayable: when a transformation turns out to be wrong, you fix the model and rerun it instead of re-extracting six months of history from a source API that no longer has it.
Step 02 / Type
Decide the column types before the first load, not after
Snowflake NUMBER defaults to (38,0), which silently truncates decimals if the source column had scale. VARCHAR defaults to 16 MB. Unquoted identifiers fold to uppercase, so a source column named createdAt becomes CREATEDAT unless you quote it. Every one of those is cheap to set correctly on day one and expensive to change once dashboards depend on the column.
Step 03 / Key
Pick the key that makes reloads idempotent
A load you cannot safely run twice is a load you will be afraid to rerun at 2am. Choose the primary key or business key that identifies a record in the source, and make the pipeline merge on it rather than append. This is the difference between a failed run being a non-event and a failed run creating duplicate revenue in a report.
Step 04 / Increment
Move only what changed after the first backfill
The initial historical load is a one-time cost. After that you want either a reliable updated-at watermark or change data capture reading the database log. Watermarks are simpler but miss hard deletes and any row updated by a process that does not touch the timestamp. CDC catches both, at the cost of database configuration.
Step 05 / Watch
Alert on the sync that did not run
The failure that hurts is not the loud one. It is the pipeline that stopped three weeks ago while a dashboard kept rendering the last numbers it saw. Freshness monitoring, row count checks against the source, and an alert routed to a human who is actually on duty matter more than any feature on a comparison table.
Step two is where most of the silent damage happens, and the data mapping best practices guide covers the type and naming decisions in detail. If you have not settled the incremental strategy in step four, change data capture tools compares log-based options against watermark polling, and ETL versus ELT explains why landing raw and transforming in Snowflake became the default order.
What teams load into Snowflake
Production database into the warehouse
Replicating Postgres, MySQL or SQL Server into Snowflake so analysts can query without touching the transactional database. This is the most common Snowflake pipeline of all, and the one where change data capture earns its configuration cost.
CRM data for revenue reporting
Pulling Salesforce or HubSpot objects into Snowflake so pipeline, conversion and attribution can be modeled against product and billing data instead of inside a CRM report builder.
Payments and billing into finance models
Loading Stripe, PayPal or Square into Snowflake to reconcile against the accounting system. Amounts arrive as integers in the smallest currency unit from Stripe, so $42.50 lands as 4250 and needs a cast on the way in.
Ecommerce orders and inventory
Shopify order, customer and inventory data into Snowflake for cohort analysis and margin reporting. Rate limits make the first full backfill slow, so plan the historical load separately from the incremental schedule.
Warehouse to warehouse migration
Moving from Redshift or BigQuery onto Snowflake, or running both during a transition. Type mapping and identifier case are where these projects actually break, not the transfer itself.
Snowflake back out to the applications
Once the modeled result exists, someone wants it in the CRM. That is the reverse direction, and it has its own tooling category with its own failure modes around API rate limits and upsert matching.
That last one, pushing modeled results from Snowflake back into Salesforce, HubSpot or NetSuite, is a separate purchase with separate failure modes. It is covered on reverse ETL tools. For the HubSpot leg specifically, the native sync runs from Snowflake into HubSpot rather than the other way, and its record and column ceilings are tabled on HubSpot integration tools.
When another Snowflake ETL tool is the right answer
We would rather you buy the correct thing than churn in month three. Five situations where Adapters is not what you want.
You need hundreds of connectors
If the requirement list runs to forty SaaS sources including several obscure ones, buy catalog breadth. Fivetran and Airbyte have spent years on that surface area and we have not.
Everything must stay in your Snowflake account
If security says no processing outside Snowflake, Openflow on Snowpark Container Services or a Snowflake Native App answers that architecturally. A managed cloud service, ours included, does not.
You want a visual transformation canvas
We do field-level mapping and no-code transforms, not a graphical job designer with joins, aggregates and branching. That is Matillion's territory, or dbt if you would rather write SQL.
You need sub-minute streaming freshness
We run on a schedule you choose. If rows have to land seconds after the event, look at Snowpipe Streaming directly or a streaming CDC vendor such as Estuary.
Your volume genuinely is enormous
Flat pricing is a bet that most teams move a predictable amount of data. If you are loading billions of rows a month, negotiate a volume contract with a metered vendor and you will likely beat our list price. Our advantage is the middle, where a metered bill is unpredictable and a hand-built loader is a permanent staffing cost nobody put on the budget.
Four questions to ask on every Snowflake ETL demo
Question 01
What does a full historical resync cost?
On a monthly-active-rows meter, one accidental resync of a large table can cost more than the rest of the year. Get the answer in writing before you sign.
Question 02
How does it handle a schema change?
A new column upstream should not break the load. Ask whether it adds the column, ignores it, or fails the run, and whether anyone gets told either way.
Question 03
What types does it choose in Snowflake?
Ask to see the CREATE TABLE it generates. Decimals landing in NUMBER(38,0) and timestamps losing their zone are discovered months later, in a finance report.
Question 04
What happens when 40 rows fail?
You want the per-record error log with the source values attached, the retry behavior, and the alert path. Partial failure is the normal case, not the edge case.
Snowflake connectors, source by source
Each page below covers one lane into or out of Snowflake: the field mappings, the type conversions that bite, the incremental strategy and the questions people ask about that specific pair.
Questions buyers ask about Snowflake ETL tools
- What are Snowflake ETL tools?
- Snowflake ETL tools are the platforms that move data from your source systems into Snowflake tables and keep them current. In practice most of them run ELT rather than ETL: they land raw data in Snowflake first, then transform it with SQL inside the warehouse, because Snowflake compute is cheaper and faster at that work than an external transformation engine.
- Does Snowflake have its own ETL tool?
- Yes, as of late 2025. Snowflake Openflow is its first-party ingestion service, built on Apache NiFi, with dozens of prebuilt connectors for databases and SaaS sources. Openflow Snowflake Deployments running on Snowpark Container Services reached general availability on 4 November 2025. A lot of published comparisons still say Snowflake has no native ETL tool, and that is now out of date.
- What is the best ETL tool for Snowflake?
- There is no single best one, only a best fit. Fivetran wins on managed connector breadth with no maintenance. Airbyte wins on catalog size and open source control. Matillion wins on visual pushdown transformation inside Snowflake. Openflow wins when you want it inside your Snowflake contract. Adapters wins when you need a handful of dependable syncs on a flat monthly bill instead of a row meter.
- Is Snowflake ETL or ELT?
- Snowflake is the destination, not the pipeline, so it is neither by itself. The pattern nearly everyone runs on it is ELT: extract from the source, load raw into Snowflake, then transform with SQL or dbt using Snowflake compute. Classic ETL, transforming in a separate engine before the load, still exists where compliance requires masking data before it lands.
- How do I load data into Snowflake?
- There are four native paths. COPY INTO handles scheduled bulk loads from a stage. Snowpipe loads files continuously and typically lands them within a minute of the file notification. Snowpipe Streaming writes rows directly with no staged files at all. Openflow and third-party connectors wrap all of that so you configure a source instead of writing load code.
- What is a Snowflake connector?
- The term covers two different things, which is why search results for it are confusing. A Snowflake driver or client library, such as the Python connector, lets your own code talk to Snowflake. A Snowflake data connector, such as the Openflow Connector for PostgreSQL or a Fivetran connector, is a managed pipeline that replicates a source system into Snowflake tables on a schedule.
- What are the best ETL tools for Snowflake for small teams?
- Small teams should optimize for predictable cost and low maintenance, not connector count. A metered platform can be excellent value at low volume and then spike when someone triggers a full historical resync. Look for flat pricing, a visual field mapping step so an analyst can change a mapping without a deploy, and per-record error logs you can actually read.
- How much do Snowflake ETL tools cost?
- Almost every vendor in this category bills by volume rather than by seat. Fivetran meters monthly active rows, Airbyte meters credits tied to rows or gigabytes, and most enterprise platforms quote consumption units. That makes the bill hard to forecast before you run it. Flat per-month pricing, which is what Adapters uses at $49 to $399, trades ceiling for predictability.
- Are there open source Snowflake ETL tools?
- Yes. Airbyte is the largest open source option and can be self-hosted with a Snowflake destination. dbt Core is open source for the transformation half, though it does not move data. Apache NiFi is open source, and Snowflake Openflow is built on it, so the open source lineage now runs through Snowflake first-party tooling too.
For the categories around this one, see BigQuery ETL tools if you are choosing between the two warehouses or run both, best data integration tools for the general market, iPaaS platforms when the job is keeping business applications in agreement rather than filling a warehouse, and ETL software for how our own pipeline works end to end. Where the source is a database rather than a SaaS application, Postgres ETL tools covers the native replication paths that often make a vendor unnecessary in the first place, and Redshift ETL tools does the same for teams weighing Snowflake against staying on AWS. Ecommerce sources deserve their own warning: the first full Shopify backfill is throttled by calculated query cost rather than row count, which is covered in Shopify API rate limits. Payments data has its own route into Snowflake, either through Stripe's own managed share or through a pipeline you control, and both are compared on Stripe integration tools.
Load your sources into Snowflake on a flat monthly price
Map the columns once, pick a schedule, and let it run with retries, alerts and per-record logs. From $49 a month, with no row meter and no credits to forecast.
No credit card required.