Two-way sync
Changes in Hibob or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Keep Hibob 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.
Hibob is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. SAP Hana is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Salaries, Time off, Lifecycle, Documents in Hibob need to exist as queryable Schemas, Sequences, Triggers, System-versioned temporal tables in SAP Hana before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Schemas, Sequences, Triggers, System-versioned temporal tables in SAP Hana with Salaries, Time off, Lifecycle, Documents in Hibob field by field, in real time. You decide which system owns which fields — Hibob typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Groups, departments, managers, and reporting lines from Hibob stay consistent in SAP Hana, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in SAP Hana write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.
Records maintained in Hibob land as queryable Schemas, Sequences, Triggers, System-versioned temporal tables in SAP Hana, so internal apps and dashboards read live data instead of a periodic export.
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.
| Hibob objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. | Documents is specific to Hibob and Column store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. | Named lists is specific to Hibob and Row store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | People (Employees) is specific to Hibob and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Employment is specific to Hibob and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Work is specific to Hibob and Schemas to SAP Hana — each maps to any object or custom field on the other side. | |
| Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Salaries is specific to Hibob and Sequences 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.
DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.
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 Hibob through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–SAP Hana connection.
Changes in Hibob or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Hibob 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 Hibob or SAP Hana record.
Track your Hibob ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Hibob 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 Hibob 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 Hibob 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 Hibob and SAP Hana: authenticate both systems, choose the objects to sync (such as Hibob's Documents and Named lists), map fields visually, and changes propagate both ways in milliseconds — no code required.
SAP Hana: Polling change detection requires a last-modified timestamp column; without one, triggers or system-versioned temporal tables are needed to catch updates and deletes. Hibob: Service User permissions are granular and per-category (People, Payroll, Documents); a request fails unless that category is explicitly granted in Bob admin. Stacksync's field mapping accounts for these differences between Hibob and SAP Hana without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Hibob and SAP Hana records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Hibob and SAP Hana connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Hibob–SAP Hana integration in-house.
Yes — Stacksync ships production-grade connectors for both Hibob and SAP Hana. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Hibob: Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event). 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.
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 540 integrations available for Hibob and SAP Hana.