Real-time
Two-way sync
Changes in Kustomer or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Database
Kustomer to SAP Hana integration — real-time, two-way sync
Keep Kustomer 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Kustomer and SAP Hana
Treat Kustomer like part of your database: its records live in SAP Hana as real tables, and writes in either place sync to the other in seconds.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in SAP Hana, where it can be queried and joined like everything else.
Stacksync mirrors Companies, Custom Objects (Klasses), Users, Teams from Kustomer into Calculation views, SQL views, Schemas, Sequences in SAP Hana with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Kustomer with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Common use cases
- 01 Escalate conversation-derived signals into the CRM as tasks or opportunities
- 02 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
- 03 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
- 04 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
Common sync patterns
Trigger workflows from CRM changes
Field and stage updates in Kustomer arrive as row changes in SAP Hana, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Kustomer become tables in SAP Hana you can join with application data directly.
Product events onto CRM records
Signup, usage, or lifecycle changes written to SAP Hana sync onto the matching records in Kustomer, giving go-to-market teams live product context.
What you can sync between Kustomer and SAP Hana
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.
| Kustomer objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Customers is specific to Kustomer and Schemas to SAP Hana — each maps to any object or custom field on the other side. | |
| Conversations Support threads across channels sync outward for analytics and CRM context. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Conversations is specific to Kustomer and Sequences to SAP Hana — each maps to any object or custom field on the other side. | |
| Messages Individual messages within conversations support full-thread replication. | 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. | Messages is specific to Kustomer and Triggers to SAP Hana — each maps to any object or custom field on the other side. | |
| Companies Organization records group customers and map to CRM accounts. | 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. | Companies is specific to Kustomer and System-versioned temporal tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | 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. | Custom Objects (Klasses) is specific to Kustomer and System views (SYS schema) to SAP Hana — each maps to any object or custom field on the other side. | |
| Users Agent records map conversation ownership to people in other systems. | 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. | Users is specific to Kustomer and Column store tables to SAP Hana — each maps to any object or custom field on the other side. |
How changes propagate between Kustomer and SAP Hana
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.
Kustomer SAP Hana Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.
SAP Hana Kustomer Sub-second propagation
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 Kustomer through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Kustomer: Subject to the platform's API rate limits.
- SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Kustomer ⇄ SAP Hana
Connect Kustomer and SAP Hana for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kustomer–SAP Hana connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Kustomer or SAP Hana data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Kustomer or SAP Hana record.
Observability
Monitoring
Track your Kustomer ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Kustomer and SAP Hana.
How the Kustomer and SAP Hana connectors work
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
SAP Hana
- Integration surface
- SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
- Authentication
- Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
- Change detection
- 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.
- Capabilities
- read · write · CDC
- Rate limits
- No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works
How to connect Kustomer to SAP Hana — three steps, no code
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.
- 01
Connect your apps
Authenticate Kustomer 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.
Kustomer
connected
SAP Hana
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Kustomer 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.
objects · Kustomer ⇄ SAP HanaCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Kustomer SAP HanaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Kustomer and SAP Hana integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Kustomer and SAP Hana: authenticate both systems, choose the objects to sync (such as Kustomer's Customers and Conversations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Kustomer side: Companies, Custom Objects (Klasses), Users, Teams, plus custom fields where Kustomer exposes them. On the SAP Hana side: Calculation views, SQL views, Schemas, Sequences. 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.
-
Common patterns for Kustomer and SAP Hana: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in Kustomer arrive as row changes in SAP Hana, ready to drive jobs and notifications.
-
Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. SAP Hana: SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access. Authentication: Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kustomer: Kustomer's data model centers on a customer timeline: conversations, messages, and custom object records all appear chronologically against one customer record rather than as separate tickets. SAP Hana: Connections are governed by workload classes and admission control, so heavy sync concurrency competes with production query load and can be throttled by memory and thread caps. Stacksync's field mapping accounts for these differences between Kustomer and SAP Hana without custom code.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 452 integrations available for Kustomer and SAP Hana.
Popular · 4 of 452
No integrations match .
