Skip to content
Marketing ⇄ CRM

Iterable to Microsoft Dynamics 365 Sales integration — real-time, two-way sync

Keep Iterable and Microsoft Dynamics 365 Sales 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 Iterable and Microsoft Dynamics 365 Sales

Keep the people you sell to and the people you market to in one shared view: Microsoft Dynamics 365 Sales and Iterable sync contacts, accounts, and engagement in real time, in both directions.

Microsoft Dynamics 365 Sales owns the customer relationship and the pipeline; Iterable runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.

Stacksync syncs Orders, Invoices, Activities, Custom Tables in Microsoft Dynamics 365 Sales with Lists, Catalogs, Commerce / Purchases, Export data in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — Microsoft Dynamics 365 Sales can own account and opportunity status while Iterable owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Run a two-way dual-run between Dynamics and another CRM during a migration.
  • 02 Feed BI models with continuously updated CRM data instead of scheduled exports.
  • 03 Push warehouse or CRM audience segments into Iterable as Users via bulkUpdate (up to 1000 per call) and subscribe them to static Lists to drive campaigns.
  • 04 Track product and revenue Events (custom events, trackPurchase, updateCart) into Iterable from an app or database so journeys trigger on live behavior.

Common sync patterns

Where Iterable generates leads: hand-off without re-keying

New leads or responders captured in Iterable flow into Microsoft Dynamics 365 Sales assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.

New and updated people stay in step

When a contact or lead is created or edited in either system, the matching record appears or updates in the other, so campaigns reach real people and reps see who is already being marketed to.

Where Iterable captures engagement: activity lands on the record

Opens, clicks, form fills, event attendance, or ad responses recorded in Iterable post back to the contact or account in Microsoft Dynamics 365 Sales, so reps see interest before they reach out.

What you can sync between Iterable and Microsoft Dynamics 365 Sales

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.

Iterable objects Microsoft Dynamics 365 Sales objects How this pairing syncs
Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Quotes Pricing proposals; often synced with CPQ or ERP pricing data. Export data is specific to Iterable and Quotes to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. Users is specific to Iterable and Orders to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Events Custom and system events tracked via /api/events/track and /api/events/trackBulk (up to 1000 events per call); a single user's event history is read via GET /api/events/{email}. Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Events is specific to Iterable and Invoices to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Campaigns Email, SMS, push, and in-app sends; metadata and metrics read via GET /api/campaigns and /api/campaigns/metrics, created and sent via /api/campaigns/create and /api/campaigns/trigger. Activities Emails, calls, appointments, and tasks; read out for activity analytics. Campaigns is specific to Iterable and Activities to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. Templates is specific to Iterable and Custom Tables to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.
Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. Lists is specific to Iterable and Accounts to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.

How changes propagate between Iterable and Microsoft Dynamics 365 Sales

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.

Iterable Microsoft Dynamics 365 Sales Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryEach detected change is written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.

Microsoft Dynamics 365 Sales Iterable Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
What ships with Iterable ⇄ Microsoft Dynamics 365 Sales

Connect Iterable and Microsoft Dynamics 365 Sales for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Iterable–Microsoft Dynamics 365 Sales connection.

Real-time

Two-way sync

Changes in Iterable or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Iterable or Microsoft Dynamics 365 Sales 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 Iterable or Microsoft Dynamics 365 Sales record.

Observability

Monitoring

Track your Iterable ⇄ Microsoft Dynamics 365 Sales sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Iterable and Microsoft Dynamics 365 Sales.

How the Iterable and Microsoft Dynamics 365 Sales connectors work

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.
How it works

How to connect Iterable to Microsoft Dynamics 365 Sales — 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 Iterable and Microsoft Dynamics 365 Sales 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
    Iterable connected
    Microsoft Dynamics 365 Sales connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Iterable and Microsoft Dynamics 365 Sales 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 · Iterable ⇄ Microsoft Dynamics 365 Sales
    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
    Iterable Microsoft Dynamics 365 Sales
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Iterable and Microsoft Dynamics 365 Sales integration FAQ

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 391 integrations available for Iterable and Microsoft Dynamics 365 Sales.

Popular · 7 of 391
All Iterable integrations All Microsoft Dynamics 365 Sales integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own