Two-way sync
Changes in Microsoft Dynamics NAV or Reltio instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics NAV and Reltio in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Companies, Customers, Vendors, Items from Microsoft Dynamics NAV into Reltio and keeps both sides consistent in real time. Whatever Microsoft Dynamics NAV 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 Microsoft Dynamics NAV with its validations respected.
Scripts and services read and write the synced tables; Stacksync handles the Microsoft Dynamics NAV interface, limits, and retries.
Updates in Microsoft Dynamics NAV arrive as row changes in Reltio, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in Reltio for provisioning, access, and reporting systems that read from the database.
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.
| Microsoft Dynamics NAV objects | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Purchase Orders is specific to Microsoft Dynamics NAV and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. | |
| G/L Entries Posted ledger entries replicated to warehouses for finance reporting. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | G/L Entries is specific to Microsoft Dynamics NAV and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. | |
| Item Ledger Entries Inventory movement history read for stock and costing analytics. | Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | Item Ledger Entries is specific to Microsoft Dynamics NAV and Entities to Reltio — each maps to any object or custom field on the other side. | |
| Dimensions Analytical codes carried on documents and entries for reporting splits. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Dimensions is specific to Microsoft Dynamics NAV and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Companies Per-company data partitions that scope every sync. | 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. | Companies is specific to Microsoft Dynamics NAV and Crosswalks to Reltio — each maps to any object or custom field on the other side. | |
| Customers Customer cards synced with CRMs so sales sees ERP balances and terms. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | Customers is specific to Microsoft Dynamics NAV and Interactions to Reltio — each maps to any object or custom field on the other side. |
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.
DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.
DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.
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 Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics NAV–Reltio connection.
Changes in Microsoft Dynamics NAV or Reltio instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics NAV or Reltio data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Microsoft Dynamics NAV or Reltio record.
Track your Microsoft Dynamics NAV ⇄ Reltio sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics NAV and Reltio.
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.
Authenticate Microsoft Dynamics NAV and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Microsoft Dynamics NAV and Reltio 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 429 integrations available for Microsoft Dynamics NAV and Reltio.