Two-way sync
Changes in Microsoft Dynamics 365 or Reltio instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics 365 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.
Engineers integrate with tools like Microsoft Dynamics 365 through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Reltio.
Stacksync mirrors Custom Tables, Accounts, Contacts, Leads from Microsoft Dynamics 365 into Entities, Relations, Crosswalks, Interactions in Reltio and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Microsoft Dynamics 365, so the tool and the database never disagree.
Records from Microsoft Dynamics 365 are ordinary rows in Reltio; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in Reltio and Stacksync propagates the change into Microsoft Dynamics 365, replacing custom integration code.
Updates in Microsoft Dynamics 365 arrive as row changes in Reltio, so triggers, jobs, and services can respond in near real time.
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 365 objects | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Leads Inbound records enriched and routed from external sources into sales queues. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Leads is specific to Microsoft Dynamics 365 and Activity Log to Reltio — each maps to any object or custom field on the other side. | |
| Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | Opportunities is specific to Microsoft Dynamics 365 and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side. | |
| Cases (Incidents) Support records shared with ticketing tools and product databases. | Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | Cases (Incidents) is specific to Microsoft Dynamics 365 and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side. | |
| Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | 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. | Quotes, Orders & Invoices is specific to Microsoft Dynamics 365 and Entities to Reltio — each maps to any object or custom field on the other side. | |
| Products Catalog records aligned with ERP item masters. | 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. | Products is specific to Microsoft Dynamics 365 and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Activities Emails, calls, and tasks captured for engagement analytics. | 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. | Activities is specific to Microsoft Dynamics 365 and Crosswalks 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.
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
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 written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365–Reltio connection.
Changes in Microsoft Dynamics 365 or Reltio instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics 365 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 365 or Reltio record.
Track your Microsoft Dynamics 365 ⇄ Reltio sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 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 365 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 365 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.
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics 365 and Reltio: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365's Leads and Opportunities), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Microsoft Dynamics 365 and Reltio: Read Microsoft Dynamics 365 with a query; Automate Microsoft Dynamics 365 from your codebase; React to changes as they happen. Records from Microsoft Dynamics 365 are ordinary rows in Reltio; join them, index them, and use them in application logic without touching the vendor API.
Microsoft Dynamics 365: REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface. Authentication: Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities). Reltio: 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). Stacksync manages authentication, retries, and rate limits on both sides.
Microsoft Dynamics 365: Customer engagement apps store data in Dataverse, which exposes a uniform OData v4 Web API across standard and custom tables. Reltio: Reltio tenants are environment- and region-specific: the REST base URL is https://{environment}.reltio.com/reltio/api/{tenantId}, so the host and tenant ID must match where the tenant is provisioned. Stacksync's field mapping accounts for these differences between Microsoft Dynamics 365 and Reltio without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Microsoft Dynamics 365 and Reltio records are not retained after a sync operation.
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 438 integrations available for Microsoft Dynamics 365 and Reltio.