Skip to content
Database ⇄ ERP

Citus to Rootstock ERP integration — real-time, two-way sync

Keep Citus and Rootstock ERP 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 Citus and Rootstock ERP

Give your engineers Rootstock ERP's data in Citus: 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 Purchase Orders, Items / Products, Bills of Material, Inventory Balances from Rootstock ERP into Citus and keeps both sides consistent in real time. Whatever Rootstock ERP is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Citus sync back into Rootstock ERP with its validations respected.

Common use cases

  • Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
  • Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
  • Replicate work order and inventory data to a Postgres database or warehouse for shop-floor and planning analytics.
  • Sync inventory availability by site to e-commerce storefronts so promised dates reflect real stock.

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

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

Controlled write-back

Choose exactly which tables and fields may flow from Citus back into Rootstock ERP, keeping the ERP authoritative.

Read ERP records with a query

Records from Rootstock ERP live in Citus as ordinary tables or collections, joinable with the rest of your data.

What you can sync between Citus and Rootstock ERP

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.

Citus objects Rootstock ERP objects
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Inventory Balances On-hand quantities by site and location, synced to storefronts and WMS.
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Receipts and Shipments Inbound and outbound transactions synced to logistics and 3PL systems.
Views Curated projections over distributed data, often used as read-only sync sources. Salesforce Accounts and Contacts Shared CRM masters in the same org, so customer data needs no separate ERP sync.
Sequences Key generators that matter when external writes must not collide with application inserts. Sales Orders Order headers and lines synced to fulfillment, invoicing, and reporting systems.
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Work Orders Manufacturing execution records synced to MES, scheduling, and analytics tools.
Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Purchase Orders Procurement documents synced with supplier portals and AP systems.
What ships with Citus ⇄ Rootstock ERP

Connect Citus and Rootstock ERP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Rootstock ERP connection.

Real-time

Two-way sync

Changes in Citus or Rootstock ERP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or Rootstock ERP 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 Citus or Rootstock ERP record.

Observability

Monitoring

Track your Citus ⇄ Rootstock ERP sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Citus and Rootstock ERP.

How the Citus and Rootstock ERP connectors work

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC

Rootstock ERP

Integration surface
Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
Authentication
OAuth 2.0 (standard Salesforce connected app flows)
Change detection
Salesforce Change Data Capture on Rootstock custom objects where enabled (entity selection limits apply); SOQL polling on SystemModstamp as fallback
Capabilities
read · write · CDC
Rate limits
Consumes the Salesforce org's daily API request allocation, shared with other integrations
How it works

How to connect Citus to Rootstock ERP — 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 Citus and Rootstock ERP 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
    Citus connected
    Rootstock ERP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and Rootstock ERP 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 · Citus ⇄ Rootstock ERP
    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
    Citus Rootstock ERP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Citus and Rootstock ERP 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 Citus and Rootstock ERP.

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.