Real-time
Two-way sync
Changes in Reltio or Sage 100 instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
Reltio to Sage 100 integration — real-time, two-way sync
Keep Reltio and Sage 100 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 Reltio and Sage 100
Give your engineers Sage 100's data in Reltio: 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, AR Invoices, Purchase Orders, GL Accounts from Sage 100 into Reltio and keeps both sides consistent in real time. Whatever Sage 100 is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Reltio sync back into Sage 100 with its validations respected.
Common use cases
- 01 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
- 02 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
- 03 Replicate GL and sales history to a warehouse or Postgres database for reporting off the on-premise system.
- 04 Sync customers, invoices, and payment status into a CRM so sales sees AR standing without opening the ERP.
Common sync patterns
Internal tools and automations without API code
Scripts and services read and write the synced tables; Stacksync handles the Sage 100 interface, limits, and retries.
React to ERP changes
Updates in Sage 100 arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.
Where Sage 100 is the HR system of record: people data for internal systems
Worker and org records stay current in Reltio for provisioning, access, and reporting systems that read from the database.
What you can sync between Reltio and Sage 100
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.
| Reltio objects | Sage 100 objects | How this pairing syncs | |
|---|---|---|---|
| Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Purchase Orders Procurement documents read for spend and receiving workflows. | Crosswalks is specific to Reltio and Purchase Orders to Sage 100 — each maps to any object or custom field on the other side. | |
| Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | GL Accounts Chart of accounts read for mapping transactions in finance integrations. | Interactions is specific to Reltio and GL Accounts to Sage 100 — each maps to any object or custom field on the other side. | |
| Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | Journal Entries Posted GL activity replicated to warehouses for FP&A. | Matches (Potential Matches) is specific to Reltio and Journal Entries to Sage 100 — each maps to any object or custom field on the other side. | |
| Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Customers AR customer master records synced to CRMs for account and credit visibility. | Activity Log is specific to Reltio and Customers to Sage 100 — each maps to any object or custom field on the other side. | |
| Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Vendors AP vendor master records synced with procurement and payment tools. | Data Change Requests (DCR) is specific to Reltio and Vendors to Sage 100 — each maps to any object or custom field on the other side. | |
| Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Inventory Items Item master with pricing and quantities, synced to e-commerce catalogs. | Reference Data (RDM) is specific to Reltio and Inventory Items to Sage 100 — each maps to any object or custom field on the other side. |
How changes propagate between Reltio and Sage 100
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.
Reltio Sage 100 Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is applied to Sage 100 as a row-level write, with types converted between the two schemas.
Sage 100 Reltio Interval-based propagation
DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Reltio ⇄ Sage 100
Connect Reltio and Sage 100 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Sage 100 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Reltio or Sage 100 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 Reltio or Sage 100 record.
Observability
Monitoring
Track your Reltio ⇄ Sage 100 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Reltio and Sage 100.
How the Reltio and Sage 100 connectors work
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
Sage 100
- Integration surface
- ODBC (ProvideX driver) for reads; Business Object Interface (BOI) or Sage-provided web services for writes
- Authentication
- Sage 100 company and user credentials; ODBC DSN credentials for direct reads
- Change detection
- Scheduled polling; no webhooks or change log on the integration surface
- Capabilities
- read · write
How it works
How to connect Reltio to Sage 100 — 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 Reltio and Sage 100 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Reltio
connected
Sage 100
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Reltio and Sage 100 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 · Reltio ⇄ Sage 100Customers 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.
Reltio Sage 100Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Reltio and Sage 100 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Reltio and Sage 100: authenticate both systems, choose the objects to sync (such as Reltio's Crosswalks and Interactions), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Reltio and Sage 100. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. On Sage 100: Scheduled polling; no webhooks or change log on the integration surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Reltio side: Reference Data (RDM), Entities, Relations, Crosswalks, plus custom fields where Reltio exposes them. On the Sage 100 side: Sales Orders, AR Invoices, Purchase Orders, GL Accounts. 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.
-
Common patterns for Reltio and Sage 100: Internal tools and automations without API code; React to ERP changes; Where Sage 100 is the HR system of record: people data for internal systems. Scripts and services read and write the synced tables; Stacksync handles the Sage 100 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
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 432 integrations available for Reltio and Sage 100.
Popular · 5 of 432
-
Reltio ⇄ Epicor ERP -
Sage 100 ⇄ Google Cloud Spanner - Sage 100 ⇄ Google Cloud SQL
-
Sage 100 ⇄ IBM AS/400 -
Sage 100 ⇄ IBM Informix
No integrations match .
