TL;DR Short answer: Shopify's admin exports orders, products and customers to CSV, but it is manual and gives you current state, not history. For cohort, margin and inventory analysis you need a scheduled Shopify data export into a warehouse. Before choosing a tool, check one thing: by default the Shopify API only returns the last 60 days of orders, so a backfill silently misses older history unless the app has the read_all_orders scope. Ten options:
Airbyte : open-source Shopify source using GraphQL Bulk Operations for large streams, into any of 700+ connectors' destinations.Fivetran : managed Shopify connector with no upkeep, billed on monthly active rows.Estuary Flow : GraphQL-native Shopify capture that handles several stores in one pipeline.Snowflake Openflow : Snowflake's own Shopify connector, for teams whose warehouse is Snowflake.Stitch Data : simple Shopify loading, now consolidating into Qlik Talend Cloud.Hevo Data : no-code Shopify connector, cloud-only and billed on events.Boomi Data Integration : formerly Rivery, with orchestration and reverse ETL back into Shopify.Workato : data pipelines on the GraphQL Admin API inside an automation platform.Matillion : Shopify connector with transformation pushed into your warehouse. Billed in credits.Meltano : open-source and CLI-first, with Shopify extraction defined in code.One Shopify constraint: without the read_all_orders scope, the Admin API returns only orders from the last 60 days, so a first sync looks complete while missing most of your history. Custom apps you build for your own store can include the scope; public apps have to apply to Shopify for it.Why is exporting Shopify data harder than it looks? Shopify's Admin API exposes orders, line items, refunds, transactions, products, variants, inventory, customers, fulfilments and discounts, which is everything an e-commerce analysis needs. Three recent platform changes shape how tools reach it:
GraphQL is now the main API. The REST Admin API has been legacy since October 2024, and new public apps must use GraphQL. Tools that read large stores efficiently use GraphQL Bulk Operations, which run a query asynchronously and return a file, rather than paging through millions of orders.
Custom apps moved to the Dev Dashboard. Since 1 January 2026, merchants can no longer create custom apps in the Shopify admin. Existing ones keep working; new ones are built in Shopify's Dev Dashboard and installed on the store, which changes how you get credentials for tools that do not use OAuth.
Order history is scoped. Apps see the last 60 days of orders unless granted read_all_orders, the most common reason a Shopify warehouse is quietly missing revenue.
How do the Shopify ETL tools compare? Tool Built for Destinations Hosting Pricing basis Airbyte Data teams, many sources Any Cloud or self-hosted Free self-hosted; Cloud volume-based; Pro and Flex capacity-based Fivetran Data teams wanting no upkeep Any Cloud Monthly active rows Estuary Flow Multi-store, low-latency pipelines Warehouses and streams Cloud or private deployment Data volume Snowflake Openflow Snowflake-centred teams Snowflake only Snowflake Snowflake consumption Stitch Data Teams with simple needs Major warehouses Cloud Row volume tiers Hevo Data Teams without engineers Major warehouses Cloud Events Boomi Data Integration ELT plus reverse ETL Major warehouses Cloud Credits Workato Teams already automating in Workato Major warehouses Cloud Quoted subscription Matillion In-warehouse transformation Snowflake, Databricks, Redshift Your cloud account Credits Meltano Engineers who want code Any Singer target Self-hosted Free, open source
Which Shopify ETL tools should you consider? Every option below reads Shopify natively. When you shortlist, ask whether it uses GraphQL Bulk Operations for large stores, whether it can read full order history, and how it authenticates now that custom apps are created in the Dev Dashboard.
1. Airbyte Airbyte is an open-source data integration platform with 700+ connectors and a community of 25,000+ data engineers. Its Shopify source reads orders, line items, refunds, transactions, products, inventory, customers, fulfilments, discounts and metafields, using GraphQL Bulk Operations for the large streams and checkpointing long bulk jobs so a failure resumes rather than restarts. You can tune the date range each bulk job covers, and it syncs incrementally into any Airbyte destination.
What's unique about Airbyte? Shopify rarely feeds a warehouse alone, and Airbyte moves your ad platforms, payments and email data through the same pipeline, so margin and CAC are one join away. Self-hosting keeps customer and order data in your own network. Connectors are open source and editable, and the Connector Development Kit covers anything else. It runs as self-hosted open source, on Airbyte Cloud, or as Enterprise Flex.
2. Fivetran Fivetran is a closed-source, managed ELT service with 700+ connectors, including Shopify. It handles schema changes and Shopify's quarterly API versions for you. It bills on monthly active rows, and order, line item and inventory tables change constantly on a busy store, which counts toward the bill.
Here is a closer look at Airbyte vs Fivetran .
3. Estuary Flow Estuary Flow's Shopify connector is built on the GraphQL Admin API and its bulk queries, and runs several bulk operations in parallel on recent API versions. It can capture multiple Shopify stores in a single pipeline, authenticating each with OAuth, an access token or Dev Dashboard client credentials, which suits brands running regional or wholesale stores side by side. It is streaming-first, with a smaller overall connector catalogue than the established platforms.
4. Snowflake Openflow Connector for Shopify Openflow is Snowflake's own data integration service, and its Shopify connector loads data straight into Snowflake using Shopify's bulk operations. For teams whose analytics already live in Snowflake, it removes a third-party vendor from the pipeline and is paid through Snowflake consumption. It writes only to Snowflake, and like every tool here it needs read_all_orders to backfill orders beyond 60 days.
5. Stitch Data Stitch is a cloud extract-and-load platform with 140+ connectors, including Shopify, originally built on the Singer specification. It has no user-defined transformations and suits straightforward loading. Qlik acquired Talend, and Stitch with it, in 2023, and now publishes a migration path from Stitch to Qlik Talend Cloud, which is worth weighing before committing.
Here is a closer look at Airbyte vs Stitch .
6. Hevo Data Hevo Data is a no-code cloud ELT platform with 150+ connectors, including Shopify, and built-in transformation applied before data reaches the destination. It is cloud-only and billed on events, which suits smaller e-commerce teams without engineering capacity.
7. Boomi Data Integration (formerly Rivery) Boomi acquired Rivery in December 2024 and now sells it as Boomi Data Integration. It has a Shopify connector and bundles transformation, orchestration and reverse ETL, so warehouse-modelled segments or scores can flow back into Shopify. Pricing is in credits that vary by connector, which can make cost hard to model.
8. Workato Workato is an enterprise automation platform whose data pipelines include a Shopify source built on the GraphQL Admin API, extracting orders, products, customers and transactions into a warehouse. It suits organisations already running Shopify workflows in Workato that want analytics loading in the same platform. Pricing is quoted rather than self-serve.
9. Matillion Matillion's cloud platform has a Shopify connector and pushes transformation down into Snowflake, Databricks or Redshift, with dbt support since v1.70. Running in your own cloud account keeps Shopify data in your infrastructure. It bills in credits tied to job runtime and makes most sense when Matillion already runs your warehouse transformations.
Here is a closer look at Airbyte vs Matillion .
10. Meltano Meltano is an open-source, CLI-first platform spun out of GitLab that manages taps and targets as a version-controlled project, with Shopify extractors on Meltano Hub. It suits teams who want pipelines defined in code. Check that the extractor you choose has moved to the GraphQL Admin API and tracks Shopify's quarterly API versions, since connector maintenance falls to the community.
How do you export all Shopify orders? For a one-off, Shopify's admin exports orders to CSV from the Orders page, with one row per line item; larger exports are emailed to you as a file. That suits a quick reconciliation, but it is a snapshot, and doing it repeatedly is error-prone.
For a complete, ongoing export through any tool, three things need to be right:
The read_all_orders scope: without it the API returns only the last 60 days. If you add it to an existing connection, re-run the orders backfill so older history is collected.Bulk operations for the backfill: on a store with years of orders, a tool that pages through the REST or standard GraphQL API will hit rate limits for hours; bulk queries return the result as a file instead.Refunds, edits and cancellations: orders change after they are placed. Sync incrementally on the updated timestamp, not the created date, and model refunds and order edits explicitly, or revenue in the warehouse will drift from Shopify's reports.How do you get Shopify data into BigQuery or Snowflake? For Snowflake, there is now a native option: Snowflake's Openflow Connector for Shopify loads directly into your account. Shopify has no equivalent native route into BigQuery, so BigQuery users need an ETL tool. In both cases, a tool such as Airbyte or Fivetran makes sense when Shopify should share a pipeline with your ad platforms, payments and email data, so that margin, CAC and cohort models draw on one schedule.
Whichever route you take, model the order grain carefully. Orders, line items, refunds and transactions are separate tables, and gross sales, net sales and revenue each come from a different combination of them.
How do you start exporting Shopify data with Airbyte? Step 1: Set up Shopify as a source In Airbyte, open Sources, choose New source and select Shopify, then enter your store name. On Airbyte Cloud, authenticate with OAuth. On Open Source, use an Admin API access token from a custom app with read scopes for the data you need, including read_all_orders: if your store has a custom app created in the Shopify admin before 2026, you can use its token; new custom apps are created in Shopify's Dev Dashboard, so follow Airbyte's Shopify documentation for the current way to generate a token. Set a start date and run the connection test.
Step 2: Set up a destination Choose where the data lands: a cloud warehouse such as BigQuery, Snowflake or Redshift, a database such as Postgres, a data lake or cloud storage.
Step 3: Configure the connection Select the streams you need, use incremental sync with deduplication so edited and refunded orders are updated in place, and set a schedule. For a large store, let the first backfill run outside peak trading hours.
The process is the same in Airbyte Open Source, which you can deploy yourself , and in Airbyte Cloud, which you can try free for 14 days .
Which Shopify ETL tool should you choose? First confirm read_all_orders, whatever you pick. Then choose by warehouse and ownership. Snowflake-centred teams can start with Openflow. For BigQuery or a multi-source stack, Airbyte, self-hosted or in Cloud, brings Shopify in next to your ad, payment and email data, and Fivetran does the same fully managed if the row-based bill works on your order volume. Estuary suits brands running several stores, Hevo, Stitch and Boomi suit simpler no-code needs, and Workato, Matillion and Meltano fit where they already run.
For tools that cover more than Shopify, see our guide to the top data integration tools .
Sync Shopify with Airbyte Move Shopify orders, line items, refunds, products and customers into BigQuery, Snowflake or any Airbyte destination, next to your ad and payment data, self-hosted or in Airbyte Cloud.
Try Airbyte Cloud free for 14 days or talk to our team .
Frequently Asked Questions (FAQs) 1. Why is my Shopify export missing older orders? By default, the Shopify Admin API only returns orders from the last 60 days. The app your tool uses needs the read_all_orders scope to read older history, and after adding it you should re-run the orders backfill.
2. Can you still create a custom app in the Shopify admin? No. Since 1 January 2026, new custom apps are created in Shopify's Dev Dashboard and then installed on the store. Custom apps created in the admin before that date keep working and their access tokens remain valid.
3. Is the Shopify REST API still supported? It still works, but Shopify has treated it as legacy since October 2024, and new public apps must use the GraphQL Admin API. ETL tools are moving to GraphQL and its Bulk Operations, which handle large stores far more efficiently.
4. How do you export Shopify orders to BigQuery? Use an ETL tool with a Shopify source and a BigQuery destination, such as Airbyte, Fivetran or Hevo, with read_all_orders granted for full history. Shopify has no native export into BigQuery.
Suggested reads Stripe ETL Tools
Klaviyo ETL Tools
E-commerce Analytics Tools
Google Ads ETL Tools