Real-time
Two-way sync
Changes in Elasticsearch or Treasuredata instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Analytics
Elasticsearch to Treasuredata integration — real-time, two-way sync
Keep Elasticsearch and Treasuredata 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 Treasuredata
Give Treasuredata the users, events, and records that live in Elasticsearch in real time, and sync the cohorts and scores Treasuredata computes back into Elasticsearch where your applications read them.
A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Treasuredata is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from Elasticsearch into Treasuredata usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.
Stacksync syncs Indices, Documents, Index mappings, Aliases in Elasticsearch with Master (Parent) Segments, Segments, Journeys, Predictive Segments in Treasuredata in real time and in both directions. Operational rows flow into Treasuredata as they change, so dashboards read current data with no pipeline to maintain, and the segments, cohorts, or scores Treasuredata computes flow back into Elasticsearch, where the applications and services that read from it get them at normal query latency. Field-level mapping, schema and type translation, and conflict resolution are handled for you.
Common use cases
- 01 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
- 02 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
- 03 Sync CRM accounts and contacts into an Elasticsearch index to power internal search across customer records.
- 04 Push product catalog data from an ERP or commerce database into Elasticsearch for storefront search.
Common sync patterns
One version of each user or account
A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.
Filter and grouping dimensions kept fresh
Attributes teams slice by, such as plan, region, or account owner, stay current in Treasuredata because they sync from Elasticsearch as they change, instead of going stale after a one-time import.
Where Treasuredata tracks product events: behavior onto stored records
Signup, usage, and lifecycle events captured in Treasuredata sync into Elasticsearch as rows, so applications and internal tools can read behavioral data next to the records they already keep.
What you can sync between Elasticsearch and Treasuredata
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 | Treasuredata objects | How this pairing syncs | |
|---|---|---|---|
| Aliases Stable read/write names that let a sync cut over between index versions without downtime. | Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. | Aliases is specific to Elasticsearch and Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Data streams Append-only targets for time-series or event data pushed from source systems. | Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. | Data streams is specific to Elasticsearch and Journeys to Treasuredata — each maps to any object or custom field on the other side. | |
| Ingest pipelines Server-side transforms applied to documents as a sync writes them. | Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. | Ingest pipelines is specific to Elasticsearch and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Index templates Reusable settings and mappings applied automatically to new indices a sync creates. | Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. | Index templates is specific to Elasticsearch and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side. | |
| Indices Target containers for synced records; each holds a table-like collection of JSON documents. | Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. | Indices is specific to Elasticsearch and Query Jobs to Treasuredata — each maps to any object or custom field on the other side. | |
| Documents The unit of sync; JSON records created, updated, and deleted by _id. | Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. | Documents is specific to Elasticsearch and Databases to Treasuredata — each maps to any object or custom field on the other side. |
How changes propagate between Elasticsearch and Treasuredata
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.
Elasticsearch Treasuredata Interval-based propagation
DetectionStacksync polls Elasticsearch for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or sequence fields.
DeliveryEach detected change is written to Treasuredata through its API, with automatic retries and rate-limit backoff.
Treasuredata Elasticsearch Interval-based propagation
DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.
DeliveryEach detected change is written to Elasticsearch through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Elasticsearch: No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity.
- Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Elasticsearch ⇄ Treasuredata
Connect Elasticsearch and Treasuredata for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–Treasuredata connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Elasticsearch or Treasuredata 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 Treasuredata record.
Observability
Monitoring
Track your Elasticsearch ⇄ Treasuredata 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 Treasuredata.
How the Elasticsearch and Treasuredata 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
Treasuredata
- Integration surface
- TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
- Authentication
- API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
- Change detection
- Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
- Capabilities
- read · write
- Rate limits
- TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works
How to connect Elasticsearch to Treasuredata — 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 Elasticsearch and Treasuredata with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Elasticsearch
connected
Treasuredata
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Elasticsearch and Treasuredata 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 · Elasticsearch ⇄ TreasuredataCustomers 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.
Elasticsearch TreasuredataCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Elasticsearch and Treasuredata integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Elasticsearch and Treasuredata: authenticate both systems, choose the objects to sync (such as Elasticsearch's Aliases and Data streams), 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 Elasticsearch and Treasuredata connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Elasticsearch–Treasuredata integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Elasticsearch and Treasuredata. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Elasticsearch: Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks. On Treasuredata: Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Treasuredata side: Master (Parent) Segments, Segments, Journeys, Predictive Segments, plus custom fields where Treasuredata exposes them. On the Elasticsearch side: Indices, Documents, Index mappings, Aliases. 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.
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
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 394 integrations available for Elasticsearch and Treasuredata.
Popular · 6 of 394
-
Elasticsearch ⇄ Microsoft Power Bi -
Elasticsearch ⇄ Tableau -
Elasticsearch ⇄ Adobeanalytics -
Elasticsearch ⇄ Pendo -
Treasuredata ⇄ Airtable -
Treasuredata ⇄ MongoDB
No integrations match .
