Real-time
Real-time sync
Changes in SuiteAnalytics or TiDB instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
SuiteAnalytics to TiDB integration — real-time data sync
Keep SuiteAnalytics and TiDB 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 SuiteAnalytics and TiDB
Give your engineers SuiteAnalytics's data in TiDB: read it with normal queries, write back through the sync, and skip the ERP API entirely.
SuiteAnalytics is a read-only source: Stacksync reads its data in real time and delivers it into TiDB, so TiDB always reflects the current state of SuiteAnalytics — without exports, scripts, or schedulers.
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 Accounting Period, Bin Transfer, Currency Rate, Price Level from SuiteAnalytics into TiDB and keeps both sides consistent in real time. Whatever SuiteAnalytics is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in TiDB sync back into SuiteAnalytics with its validations respected.
Common use cases
- 01 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
- 02 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
- 03 Give internal tools a read replica of item and inventory data without hitting SuiteScript governance limits
- 04 Join ERP data with CRM data in Postgres for quote-to-cash and revenue visibility
Common sync patterns
Internal tools and automations without API code
Scripts and services read and write the synced tables; Stacksync handles the SuiteAnalytics interface, limits, and retries.
React to ERP changes
Updates in SuiteAnalytics arrive as row changes in TiDB, so jobs and triggers can respond as the business record changes.
Where SuiteAnalytics is the HR system of record: people data for internal systems
Worker and org records stay current in TiDB for provisioning, access, and reporting systems that read from the database.
What you can sync between SuiteAnalytics and TiDB
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.
| SuiteAnalytics objects | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| Nexus Synced with incremental and full sync per the Stacksync docs. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Nexus is specific to SuiteAnalytics and Databases to TiDB — each maps to any object or custom field on the other side. | |
| Tax Type Synced with incremental and full sync per the Stacksync docs. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Tax Type is specific to SuiteAnalytics and Tables to TiDB — each maps to any object or custom field on the other side. | |
| Sales Tax Item Synced with incremental and full sync per the Stacksync docs. | Views Logical views for shaping reads before syncing outward. | Sales Tax Item is specific to SuiteAnalytics and Views to TiDB — each maps to any object or custom field on the other side. | |
| Billing Schedule Customer Subsidiary Relationship Synced with incremental and full sync per the Stacksync docs. | Columns MySQL-compatible types mapped to fields in the paired system. | Billing Schedule Customer Subsidiary Relationship is specific to SuiteAnalytics and Columns to TiDB — each maps to any object or custom field on the other side. | |
| Account Synced with incremental and full sync per the Stacksync docs. | Indexes Secondary indexes that keep incremental sync queries efficient. | Account is specific to SuiteAnalytics and Indexes to TiDB — each maps to any object or custom field on the other side. | |
| Accounting Period Synced with incremental and full sync per the Stacksync docs. | Sequences Server-side ID generation relevant when external systems write rows. | Accounting Period is specific to SuiteAnalytics and Sequences to TiDB — each maps to any object or custom field on the other side. |
How changes propagate between SuiteAnalytics and TiDB
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.
SuiteAnalytics TiDB Interval-based propagation
DetectionStacksync polls SuiteAnalytics for changes on an incremental schedule, reading only records changed since the previous pass.
DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.
TiDB SuiteAnalytics Sub-second propagation
DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.
DeliverySuiteAnalytics does not accept inbound record writes, so this direction carries requests rather than records: SuiteAnalytics's output flows back as field updates on the originating TiDB records.
Rate-limit considerations
- SuiteAnalytics: Concurrency and query load are governed by the NetSuite account's Connect service allowances rather than per-request rate limits.
- TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with SuiteAnalytics ⇄ TiDB
Connect SuiteAnalytics and TiDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every SuiteAnalytics–TiDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever SuiteAnalytics or TiDB 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 SuiteAnalytics or TiDB record.
Observability
Monitoring
Track your SuiteAnalytics ⇄ TiDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between SuiteAnalytics and TiDB.
How the SuiteAnalytics and TiDB connectors work
SuiteAnalytics
- Integration surface
- SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)
- Authentication
- NetSuite Token-Based Authentication: create an integration record (Consumer ID + Consumer Secret), an access token (Token ID + Token Secret), a role with SuiteAnalytics Connect and SuiteAnalytics Connect - Read All
- Change detection
- Not stated in the docs
- Capabilities
- read
- Rate limits
- Concurrency and query load are governed by the NetSuite account's Connect service allowances rather than per-request rate limits
TiDB
- Integration surface
- MySQL wire protocol (SQL)
- Authentication
- Database credentials (MySQL-compatible username/password)
- Change detection
- Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
- Capabilities
- read · write · CDC
- Rate limits
- Throughput scales with cluster size rather than fixed API quotas
How it works
How to connect SuiteAnalytics to TiDB — 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 SuiteAnalytics and TiDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
SuiteAnalytics
connected
TiDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the SuiteAnalytics and TiDB 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 · SuiteAnalytics ⇄ TiDBCustomers 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.
SuiteAnalytics TiDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
SuiteAnalytics and TiDB integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between SuiteAnalytics and TiDB — SuiteAnalytics is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both SuiteAnalytics and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on SuiteAnalytics: Not stated in the docs. On TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the TiDB side: Indexes, Sequences, Databases, Tables, plus custom fields where TiDB exposes them. On the SuiteAnalytics side: Accounting Period, Bin Transfer, Currency Rate, Price Level. Stacksync auto-detects both schemas and converts types between the two systems.
-
SuiteAnalytics is a read-only source, so this integration runs one-way: Stacksync reads from SuiteAnalytics in real time and delivers into TiDB. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for SuiteAnalytics and TiDB: Internal tools and automations without API code; React to ERP changes; Where SuiteAnalytics is the HR system of record: people data for internal systems. Scripts and services read and write the synced tables; Stacksync handles the SuiteAnalytics interface, limits, and retries.
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:
