Skip to content
Database ⇄ Analytics

MySQL to Treasuredata integration — real-time, two-way sync

Keep MySQL 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 MySQL and Treasuredata

Give Treasuredata the users, events, and records that live in MySQL in real time, and sync the cohorts and scores Treasuredata computes back into MySQL 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 MySQL 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 JSON Columns, Stored Procedures, Triggers, Databases (Schemas) in MySQL with Predictive Segments, Scheduled Queries, Query Jobs, Databases 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 MySQL, 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 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
  • 02 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
  • 03 Replicate ERP master data (customers, items, pricing) into the MySQL databases behind storefronts and portals
  • 04 Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts

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 MySQL 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 MySQL as rows, so applications and internal tools can read behavioral data next to the records they already keep.

What you can sync between MySQL 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.

MySQL objects Treasuredata objects How this pairing syncs
Tables The primary sync target; rows map to records in connected systems. Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. Primary and Unique Keys is specific to MySQL and Master (Parent) Segments to Treasuredata — each maps to any object or custom field on the other side.
JSON Columns Validated semi-structured payloads for nested SaaS data. Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. JSON Columns is specific to MySQL and Segments to Treasuredata — each maps to any object or custom field on the other side.
Stored Procedures Server-side logic that can post-process synced rows. Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. Stored Procedures is specific to MySQL and Journeys to Treasuredata — each maps to any object or custom field on the other side.
Triggers An alternative change-capture mechanism when binlog access is unavailable. Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. Triggers is specific to MySQL and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side.
Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. Databases (Schemas) is specific to MySQL and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side.

How changes propagate between MySQL 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.

MySQL Treasuredata Sub-second propagation

DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.

DeliveryEach detected change is written to Treasuredata through its API, with automatic retries and rate-limit backoff.

Treasuredata MySQL 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 applied to MySQL as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
  • 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 MySQL ⇄ Treasuredata

Connect MySQL and Treasuredata for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in MySQL or Treasuredata instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MySQL 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 MySQL or Treasuredata record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MySQL and Treasuredata.

How the MySQL and Treasuredata connectors work

MySQL

Integration surface
SQL wire protocol (MySQL client/server protocol)
Authentication
Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MySQL setup guide

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 MySQL 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.

  1. 01

    Connect your apps

    Authenticate MySQL 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    MySQL connected
    Treasuredata connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MySQL 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · MySQL ⇄ Treasuredata
    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
    MySQL Treasuredata
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MySQL and Treasuredata integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 420 integrations available for MySQL and Treasuredata.

Popular · 6 of 420
All MySQL integrations All Treasuredata integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own