Two-way sync
Changes in Microsoft Dynamics 365 or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics 365 and Newrelic in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Microsoft Dynamics 365 is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Newrelic is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.
Stacksync syncs Quotes, Orders & Invoices, Products, Activities, Custom Tables in Microsoft Dynamics 365 with NRQL Query Results, Entities, Workloads, Synthetics Monitors in Newrelic field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.
Records created or changed in Microsoft Dynamics 365 publish to the queue or topic in Newrelic as they happen, so downstream services react to real events rather than polling for them.
People and accounts in Microsoft Dynamics 365 stay matched to the users in Newrelic, so access, provisioning, and org changes propagate instead of being keyed in twice.
Open items, throughput, and error counts from Microsoft Dynamics 365 replicate into Newrelic, so the operational view reflects what is actually happening in the business.
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 | Newrelic objects | How this pairing syncs | |
|---|---|---|---|
| Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Workloads Workload groupings of related entities via NerdGraph workloadCreate/workloadUpdate/workloadDelete with full CRUD; read for status rollups or provisioned from a service catalog to keep team-level views current. | Opportunities is specific to Microsoft Dynamics 365 and Workloads to Newrelic — each maps to any object or custom field on the other side. | |
| Cases (Incidents) Support records shared with ticketing tools and product databases. | Synthetics Monitors Synthetic uptime and scripted browser checks managed through NerdGraph synthetics mutations (create, update, delete); monitor results are read via NRQL for availability and latency reporting. | Cases (Incidents) is specific to Microsoft Dynamics 365 and Synthetics Monitors to Newrelic — 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. | Custom Events Custom events posted write-only to the Event API on insights-collector with a License/Ingest key; business or pipeline events pushed into New Relic to enrich dashboards, then queried back out with NRQL. | Quotes, Orders & Invoices is specific to Microsoft Dynamics 365 and Custom Events to Newrelic — each maps to any object or custom field on the other side. | |
| Products Catalog records aligned with ERP item masters. | Change Tracking (Deployments) Deployment and change markers recorded through NerdGraph changeTrackingCreateDeployment; written from CI/CD to annotate charts, and read back via NRQL on the Deployment event for release correlation. | Products is specific to Microsoft Dynamics 365 and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side. | |
| Activities Emails, calls, and tasks captured for engagement analytics. | Dashboards Dashboard definitions and widgets via NerdGraph dashboardCreate/dashboardUpdate/dashboardDelete mutations and entity queries, with full CRUD; exported for backup and audit or provisioned and updated programmatically from a source of truth. | Activities is specific to Microsoft Dynamics 365 and Dashboards to Newrelic — each maps to any object or custom field on the other side. | |
| Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Alert Policies & Conditions Alert policies and NRQL alert conditions managed through NerdGraph alertsPolicy and alertsNrqlCondition mutations with full create, update, and delete; read out for audit or provisioned from a config source so alerting stays consistent across accounts. | Custom Tables is specific to Microsoft Dynamics 365 and Alert Policies & Conditions to Newrelic — 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 Newrelic through its API, with automatic retries and rate-limit backoff.
DetectionNewrelic notifies Stacksync of record changes through webhook events. NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans).
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–Newrelic connection.
Changes in Microsoft Dynamics 365 or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics 365 or Newrelic 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 Newrelic record.
Track your Microsoft Dynamics 365 ⇄ Newrelic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 and Newrelic.
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 Newrelic 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 Newrelic 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 Newrelic: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365's Opportunities and Cases (Incidents)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Microsoft Dynamics 365: Customer engagement apps store data in Dataverse, which exposes a uniform OData v4 Web API across standard and custom tables. Newrelic: NRQL queries run via the API are limited to 3,000 per account per minute with a 5-second default timeout and about 5,000 data points per response; the historical data export path can return far more. Stacksync's field mapping accounts for these differences between Microsoft Dynamics 365 and Newrelic 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 Newrelic records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Microsoft Dynamics 365 and Newrelic connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft Dynamics 365–Newrelic integration in-house.
Yes — Stacksync ships production-grade connectors for both Microsoft Dynamics 365 and Newrelic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Microsoft Dynamics 365: Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties. On Newrelic: NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans); config objects such as dashboards, alert policies, and workloads carry no modified-date and are diffed on each run. Alert workflows can push outbound webhook notifications for near-real-time alerting. No CDC feed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 392 integrations available for Microsoft Dynamics 365 and Newrelic.