Skip to content
Database ⇄ ERP

Elasticsearch to SAP integration — real-time, two-way sync

Keep Elasticsearch and SAP 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 Elasticsearch and SAP

Give your engineers SAP's data in Elasticsearch: read it with normal queries, write back through the sync, and skip the ERP API entirely.

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 Sales Orders, Purchase Orders, Outbound Deliveries, Billing Documents from SAP into Elasticsearch and keeps both sides consistent in real time. Whatever SAP is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Elasticsearch sync back into SAP with its validations respected.

Common use cases

  • Sync CRM accounts and contacts into an Elasticsearch index to power internal search across customer records.
  • Push product catalog data from an ERP or commerce database into Elasticsearch for storefront search.
  • Expose sales order and delivery status to customer portals through a synced Postgres database instead of direct SAP access.
  • Publish plant-level inventory to e-commerce and planning systems on change or on schedule.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the SAP interface, limits, and retries.

React to ERP changes

Updates in SAP arrive as row changes in Elasticsearch, so jobs and triggers can respond as the business record changes.

Where SAP is the HR system of record: people data for internal systems

Worker and org records stay current in Elasticsearch for provisioning, access, and reporting systems that read from the database.

What you can sync between Elasticsearch and SAP

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.

Elasticsearch objects SAP objects
Ingest pipelines Server-side transforms applied to documents as a sync writes them. Billing Documents Invoices read for AR status and replicated for revenue reporting.
Index templates Reusable settings and mappings applied automatically to new indices a sync creates. GL Accounts and Journal Entries Financial postings replicated to warehouses for group finance analytics.
Indices Target containers for synced records; each holds a table-like collection of JSON documents. Production Orders Manufacturing orders exchanged with MES and scheduling systems.
Documents The unit of sync; JSON records created, updated, and deleted by _id. Inventory / Stock Plant and storage-location quantities synced to storefronts and planning tools.
Index mappings Field type definitions that determine how synced fields are indexed and queried. Cost Centers Controlling masters read for mapping costs in finance integrations.
Aliases Stable read/write names that let a sync cut over between index versions without downtime. Business Partners The unified customer and supplier master in S/4HANA, the anchor object for CRM and procurement syncs.
What ships with Elasticsearch ⇄ SAP

Connect Elasticsearch and SAP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–SAP connection.

Real-time

Two-way sync

Changes in Elasticsearch or SAP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Elasticsearch or SAP 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 Elasticsearch or SAP record.

Observability

Monitoring

Track your Elasticsearch ⇄ SAP sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Elasticsearch and SAP.

How the Elasticsearch and SAP connectors work

Elasticsearch

Integration surface
REST API (JSON over HTTP)
Authentication
API keys or basic authentication; Elastic Cloud also issues service account tokens
Change detection
Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks
Capabilities
read · write
Rate limits
No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity

SAP

Integration surface
OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
Authentication
OAuth 2.0 or basic auth via communication arrangements on cloud editions; SAP user credentials for RFC on-prem
Change detection
Business events via SAP Event Mesh on S/4HANA; change pointers with IDocs or timestamp polling on ECC
Capabilities
read · write · webhooks
Rate limits
Throttling is configured at the gateway and tenant level rather than as a single published rate limit
How it works

How to connect Elasticsearch to SAP — 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.

  1. 01

    Connect your apps

    Authenticate Elasticsearch and SAP with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Elasticsearch connected
    SAP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Elasticsearch and SAP 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Elasticsearch ⇄ SAP
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Elasticsearch SAP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Elasticsearch and SAP integration FAQ

SECURITY

Security teams love 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 386 integrations available for Elasticsearch and SAP.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.