Boomi is an integration platform for applications and APIs, with a data-integration product (change capture, ELT and reverse ETL) from its acquisition of Rivery in December 2024 and an SAP change-capture capability generally available since October 8, 2025 that runs through the Boomi for SAP add-on installed in the SAP system [1][2][3]. Lima Backbone reads SAP with nothing installed in it, moves data at analytical volume to planning applications and lakehouses, and returns results to the ERP. The differences that matter are the SAP path, the volume the engine is built for, planning targets and how you pay.
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 | Boomi | Lima Backbone |
|---|---|---|
| What it is | An integration platform (application integration, API management, Data Hub for master data) and Boomi Data Integration for change capture, ELT and reverse ETL [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 | Boomi-hosted cloud, a private runtime cloud, on-premises, hybrid and containerised runtimes [5]. | Lima's cloud, your private cloud, or on your own machines; the same software in each (product). |
| How you pay | Pay-As-You-Go at $99 per month plus usage; Integration, API Management, Data Hub and Data Integration editions quoted on request [4]. | 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 change data capture for tables, CDS views and extractors, described as SAP-certified, application-layer and without ABAP coding; it requires the Boomi for SAP add-on installed in the SAP system [2][3]. | 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 | Connectors for Oracle E-Business Suite and Oracle Fusion applications (vendor connector catalog). | 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 | Boomi Data Integration for databases and SAP (through the add-on) [2]. | Application-layer change capture for SAP; database-log capture for PostgreSQL, MySQL, SQL Server and Oracle; streams in micro-batches (product). |
| Transformation | Mapping and process shapes in the integration designer; ELT pushdown in Boomi Data Integration [1]. | 150+ visual operators and Python on a parallel engine; ETL, ELT or a mix (product). |
| Orchestration and deadlines | Process schedules and event-driven processes (vendor docs). | 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 | Process-level error handling and retry; document tracking (vendor docs). | 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 | Application integration writes to SAP and other applications; reverse ETL from warehouses to applications [1][2]. | 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 | General connectors; confirm planning-application coverage in the connector catalog. | Kinaxis Maestro, o9, Blue Yonder, SAP IBP, OMP and Anaplan are packaged targets with their data models described (product). |
| Reconciliation | Document tracking and process reporting (vendor docs). | 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 | Agentstudio for building and governing agents, generally available since May 2025 [6]. | Airflow-native; OpenLineage, Open Data Contract Standard, MCP server, Iceberg and Delta output on a dated schedule (see the standards page). |
Nothing installed in SAP. Boomi's SAP change capture runs through the Boomi for SAP add-on installed in the SAP system [3]. Lima's SAP path installs nothing: a communication user, released interfaces, a session cap agreed with Basis. Test it: ask both vendors for the transport list.
A comparison is only useful if it says when the other product fits. These are the situations in which each one does.
The two are often complementary: Boomi carries the application-to-application flows and APIs; Lima Backbone carries the bulk and planning data. A Boomi process can call a Lima pipeline, and a Lima exception can open a ticket through Boomi's connectors.
Lima reads and writes applications through their APIs where a data flow needs it, and exceptions can open tickets in ServiceNow or similar. For event-driven application-to-application flows an integration platform is the usual tool, and the two run side by side.
No. Boomi's release describes change capture without ABAP coding, and its documentation describes an add-on installed in SAP [2][3]. Lima installs nothing in SAP.
Ask both for a measured run on your tables. Lima publishes its benchmark method and labels its figures: 220M rows in about 30 minutes on 64 vCPU is an estimate until the public run replaces it.
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.
