Two-way sync
Changes in Odoo or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Keep Odoo and SAP Hana in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order) from Odoo into SAP Hana and keeps both sides consistent in real time. Whatever Odoo is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in SAP Hana sync back into Odoo with its validations respected.
Choose exactly which tables and fields may flow from SAP Hana back into Odoo, keeping the ERP authoritative.
Records from Odoo live in SAP Hana as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Odoo interface, limits, and retries.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Odoo objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Inventory Transfers (stock.picking) is specific to Odoo and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Employees (hr.employee) HR records read for directory and provisioning syncs. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Employees (hr.employee) is specific to Odoo and Schemas to SAP Hana — each maps to any object or custom field on the other side. | |
| Projects and Tasks (project.project / project.task) Work items synced with external project tools. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Projects and Tasks (project.project / project.task) is specific to Odoo and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. | Contacts (res.partner) is specific to Odoo and Triggers to SAP Hana — each maps to any object or custom field on the other side. | |
| Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. | System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. | Sales Orders (sale.order) is specific to Odoo and System-versioned temporal tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. | System views (SYS schema) Catalog and monitoring views such as SYS.TABLES and TABLE_COLUMNS; read to discover schema and auto-generate field mappings for new tables. | Invoices (account.move) is specific to Odoo and System views (SYS schema) to SAP Hana — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.
DeliveryEach detected change is written to Odoo through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Odoo–SAP Hana connection.
Changes in Odoo or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Odoo or SAP Hana data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Odoo or SAP Hana record.
Track your Odoo ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Odoo and SAP Hana.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Odoo and SAP Hana with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Odoo and SAP Hana objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Odoo and SAP Hana: authenticate both systems, choose the objects to sync (such as Odoo's Inventory Transfers (stock.picking) and Employees (hr.employee)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Odoo and SAP Hana connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Odoo–SAP Hana integration in-house.
Yes — Stacksync ships production-grade connectors for both Odoo and SAP Hana. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Odoo: Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules. On SAP Hana: Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the SAP Hana side: Triggers, System-versioned temporal tables, System views (SYS schema), Column store tables, plus custom fields where SAP Hana exposes them. On the Odoo side: Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order). Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 554 integrations available for Odoo and SAP Hana.