Fivetran copies data from hundreds of sources into a warehouse through managed connectors, and dbt transforms it there with SQL; the two companies became one on June 1, 2026 [1]. Lima Backbone reads SAP and Oracle through their released interfaces, transforms the data on its own engine, loads it into planning applications and lakehouses, and writes results back into the ERP. The differences that matter are how you pay, how SAP is read, whether the ERP receives results, and whether planning applications are targets.
Each row states what each product does in plain words. Where a fact depends on a vendor document, the document is numbered and linked beneath the table.
| Item | Fivetran + dbt Labs | Lima Backbone |
|---|---|---|
| What it is | Managed connectors (Fivetran) that copy source data into a warehouse or lake, and a transformation framework (dbt) that runs SQL inside the warehouse [1][2]. | Lima Backbone: the data-movement part of the Lima platform. Pipelines, orchestration, change capture and write-back, from a nightly copy into a data lake to a full ERP-to-planning integration with results returned to the ERP. |
| Where it runs | Fivetran SaaS; a Hybrid Deployment where the data plane runs in your environment; HVR 6 as a self-hosted product. dbt Cloud SaaS or dbt Core [7][9]. | Lima's cloud, your private cloud, or on your own machines; the same software in each (product). |
| How you pay | Fivetran: monthly active rows (MAR), priced per connection on a tiered curve; plans Free, Standard, Enterprise and Business Critical; a $5 minimum per standard connection and deleted rows counted since January 1, 2026; Activations billed in MAR [2][3][4]. dbt Cloud: Developer free, Starter $100 per user per month, Enterprise on request [9]. | A subscription sized by the tier your estate needs (32C to 128C); the whole platform is included; the price does not change with rows moved, connections, jobs or questions asked. Fixed-price entry offers (product; see the pricing page). |
| SAP extraction | SAP ERP on HANA: in NetWeaver mode the Fivetran NetWeaver API is installed in the SAP system; alternatively direct HANA JDBC with trigger-based change capture. SAP ECC on Oracle or SQL Server through HVA log-based capture. SAP OData with ODP delta tracking. SAP connectors require the Enterprise or Business Critical plan [5][6]. No product statement on SAP Note 3255746 was found in the documentation. | Table reads through a named released function module, BAPIs, released CDS views, change pointers and extractor delta queues. No ODP RFC (SAP Note 3255746), no RFC_READ_TABLE in production (Note 382318), no HANA log reading (Note 2971304). Nothing installed in SAP (product; compliance statement pending sign-off). |
| Oracle extraction | Oracle Database connector with log-based change capture; Oracle applications are read at the database level [5]. | Partitioned JDBC reads within a cap agreed with the DBA; changed rows by last-update columns; LogMiner where the DBA allows; Oracle Fusion Cloud through BICC extracts and REST (product). |
| Change capture | Log-based for databases (HVR lineage); API-based for SaaS sources; sync frequency set per connection [2][5]. | Application-layer change capture for SAP; database-log capture for PostgreSQL, MySQL, SQL Server and Oracle; streams in micro-batches (product). |
| Transformation | dbt: SQL models run inside the warehouse; Fivetran quickstart models for common sources [9]. | 150+ visual operators and Python on a parallel engine; ETL, ELT or a mix (product). |
| Orchestration and deadlines | Sync schedules per connection; dbt Cloud job schedules and triggers [2][9]. | Runs on Apache Airflow with five trigger modes. A run window with a business deadline; a failed check pauses the run and its clock; resume from checkpoint; ordered replay (product). |
| A bad record | Connector-level sync status and alerts; schema changes propagated automatically [2]. | Incoming = valid + exception records. A failed row is kept, routed to the buyer, planner or steward who owns it with a deadline, and replayed once fixed (product). |
| Write-back | Activations (reverse ETL, launched February 1, 2026) write to SaaS destinations such as NetSuite; no SAP or Oracle ERP destination found [3][8]. | To SAP through BAPIs and IDocs, to Oracle through open interface tables and public APIs; each write carries a key and counts as done only when the ERP confirms it; a ledger records every write (product). |
| Planning applications as targets | Destinations are warehouses and lakes; planning applications are not listed as destinations [2]. | Kinaxis Maestro, o9, Blue Yonder, SAP IBP, OMP and Anaplan are packaged targets with their data models described (product). |
| Reconciliation | Sync logs and row counts per connector [2]. | A report after every run: rows in, rows out, control totals and variance per table; exceptions and their owners; deadline met or missed (product). |
| Standards | dbt Core open source (v2.0 with the Fusion engine); data lake destinations in Iceberg and Delta formats [1][2]. | Airflow-native; OpenLineage, Open Data Contract Standard, MCP server, Iceberg and Delta output on a dated schedule (see the standards page). |
Adding a connection costs nothing on Lima. A Lima subscription is sized by the tier; the twentieth source on the same tier costs the same as the first. On Fivetran each standard connection carries its own MAR curve and, since January 1, 2026, a $5 monthly minimum [3][4]. Test it: price your estate's connection count both ways.
A comparison is only useful if it says when the other product fits. These are the situations in which each one does.
Many estates run both. Fivetran copies the long tail of SaaS sources into the warehouse; Lima Backbone reads the ERPs, delivers the planning datasets and returns the plans. dbt models can run after a Lima load lands in the warehouse, triggered from the same Airflow DAG.
Lima routes its own long tail of small SaaS sources to a partner connector service, so a request for a connector Lima does not package is met without a second contract.
Lima transforms data on its own engine before the load, or lands raw data and lets dbt transform it in the warehouse. Teams that work in dbt keep dbt; Lima adds the ERP extraction, the checks, the planning targets and the return path.
No. Lima packages 60 connectors for the ERPs, planning applications, warehouses, databases, files, streams and applications that carry enterprise volume, and routes the long tail of small SaaS sources to a partner connector.
Yes in two ways: Lima installs nothing in SAP and does not use the ODP RFC interface. Fivetran's SAP ERP on HANA connector in NetWeaver mode installs the Fivetran NetWeaver API in the SAP system [6]; its OData connector uses ODP over OData, which SAP permits.
A two-week bake-off on your estate measures rows per minute, hours to a first load, reconciliation variance, run-window adherence and exceptions routed, plus one confirmed write-back.