Data pipeline migration / Fivetran to Ingest
Replace Fivetran with a cutover you can check
Map your connections, confirm source coverage and move scheduled syncs to Ingest. Keep your warehouse and validate each wave before switching.
Scheduled syncs
Ingest is optional. You can keep your existing pipelines.
Know what is worth keeping
Review the source systems and connections your reports depend on. Identify unused sources and the connectors Ingest can cover before planning a cutover.
Migrate in checked waves
Agree source coverage, refresh schedules and reconciliation checks. Our engineers plan a phased cutover so you can compare the data before retiring each connection.
Keep the warehouse you have
Ingest brings scheduled syncs from 30+ tools into your warehouse or ours. Keep your warehouse, and build Rig Map, Migrate and Run on the same data.
Fivetran and Rig, feature by feature
The honest comparison, including the rows Fivetran wins.
| Feature | Fivetran | Rig |
|---|---|---|
| Managed SaaS connectors | 700+ connectors | 300+ connectors, plus open-source dlt for anything missing |
| Database replication | Log-based CDC on enterprise DB connectors | Batch and incremental. Sub-minute CDC is not there yet |
| Schema drift handling | Automatic column and table propagation | Automatic, and Rig Map re-reads the schema so models and metrics follow |
| Your warehouse | Loads into Snowflake, BigQuery, Databricks, Redshift | Same destinations, or Rig hosts the warehouse for you |
| dbt | dbt Core integration, billed per model run | dbt Core included, no per-run billing |
| Transformations | Quickstart data models | Generated dbt models plus virtual data models over the raw tables |
| Sync frequency | 15 min on Standard, 1 min on Enterprise | 15 min standard, configurable per source |
| RBAC | Role-based access to the Fivetran console | Role, schema, column and row-level access to the data itself |
| Audit trail | Sync and connector logs | Every query, by user and by agent, with the SQL attached |
Where we fall short
Four gaps we tell every caller about, so none of them surprises you after the move.
Sub-minute, log-based CDC. If you replicate a high-write production Postgres or MongoDB with a second-level RPO, keep Fivetran on that one connector and run Rig for everything else. Several customers do exactly this.
700+ connectors is more than 300+. The long tail is where Fivetran wins, and if you depend on an obscure source we may need to build it. dlt is open source, so you can build it too, and we will not hold the pipeline hostage.
Fivetran has a decade of SOC 2 audits and a Fortune 500 reference list. We are a younger company. If your procurement team weights vendor age heavily, that is a fair thing to weigh.
No Audience Hub equivalent. Reverse ETL back into Salesforce and HubSpot works, but the campaign-audience tooling around it is thinner.
What you get that Fivetran does not do
Flat pricing
A schema change that triggers a re-sync, a backfill, a chatty API, a table someone accidentally set to full refresh: on MAR pricing each of those is a bill. On Rig the number is the same every month.
Models and context on top of the load
Fivetran lands raw tables and stops. Rig reads the warehouse and builds Rig Map on top: table and column meaning, joins, business terms, certified metrics. Rig Map is what makes the data answerable.
Governed AI access, built in
One MCP endpoint your whole company can point Claude at, with row and column-level permissions, sandboxed SQL and a full audit log. Teams never need their own API keys or warehouse credentials in a config file.
Unlimited seats
Every plan includes unlimited seats, so analysts, ops, finance and the CEO can all ask questions.
We do the migration
Pipelines, models, dashboards, rebuilt by us, running in parallel with Fivetran until you are satisfied. No charge for the build.
Dashboards and automations on top
The things you would otherwise buy a BI seat and a workflow tool for. Included, and generated from the same certified metrics.
Anonymised migrations
Moves we have already run
Named with each customer's approval only; until then, the shape of the work.
Ninety-six connections on the books, fifty-seven actually doing anything. Snowflake ingestion from MongoDB, Postgres, Zendesk and Stripe. We reviewed every connector before quoting, phased the move with parallel runs and schema mapping, and cut the ones nobody had read in a year.
Compute was 80% of total data spend, on top of Fivetran ingestion. Rig replaced the ingestion, auto-migrated the Metabase dashboards, and the query patterns Rig learned fed straight into slot management on the warehouse side.
Common questions
How long does a Fivetran migration take?
A week is typical for a mid-sized stack. We rebuild your connectors, models and dashboards on Rig while Fivetran keeps running, compare the two outputs row by row until they agree, and only then do you switch Fivetran off. Larger estates with database replication and heavy dbt projects run to three or four weeks, phased connector by connector.
Do I have to move all my connectors at once?
No, and most teams shouldn't. The normal pattern is to move the expensive SaaS connectors first, because that is where MAR pricing hurts most, and leave databases on Fivetran until you're comfortable. Running both side by side for a while is normal.
What happens to the data already in my warehouse?
Nothing. It is your warehouse and your data. Rig writes into the same destination, and we match Fivetran's schema and naming so your existing dbt models and dashboards keep resolving. History that Fivetran has already loaded stays exactly where it is.
Can I keep my own Snowflake or BigQuery?
Yes. Rig runs headless on the warehouse you already have, for a flat fee with no compute markup. Or we host the warehouse and bill platform fee plus compute. Both are on the pricing page, and unlimited seats apply either way.
What about my dbt project?
It comes across as-is. Rig runs dbt Core and does not bill per model run, so the transformations line on your Fivetran invoice goes to zero. If your models were built against Fivetran's schema, they keep working, because we match it.
Does Rig do log-based CDC?
Not at sub-minute latency, and we'd rather say so up front. Batch and incremental replication are solid. If you have a high-write production database with a second-level recovery point objective, keep that one connector on Fivetran and move everything else. The savings are in the SaaS connectors anyway.
You don't have a connector I need. Then what?
We build it, usually within the migration window, and it costs you nothing. Rig's ingestion is built on dlt, which is open source, so the connector is a Python module you can read, fork and run yourself if you ever leave.
Is the migration really free?
Yes. Pipelines, models and dashboards rebuilt at no cost, plus a discount on year one once you're live. We do it because a migration we run is a migration that works, and because the fastest way to show the pricing difference is to put both bills next to each other.
How is Rig cheaper if you're also moving the same rows?
Because we don't charge per row. Our cost is compute and storage, which tracks the number of tables and syncs. How often a row changes barely moves it. Under MAR pricing, a backfill or a re-sync raises the bill.
Also comparing
Fivetran pricing, plan names and published rates checked 11 August 2026 against fivetran.com/pricing and Fivetran's own pricing guide. Fivetran changes these; if something here has moved, tell us and we'll fix it. Rig prices are the public tiers, agreed before you start. Customer figures are from migrations we ran, anonymised at the customer's preference.
Talk to Rig
What work do you want to improve?
Tell us where your team spends time, loses money or needs better information.
In a 30-minute call, we’ll discuss the data and systems work that could help.