Skip to content
ERP ⇄ Marketing

Dynamics 365 F&O to Iterable integration — real-time, two-way sync

Keep Dynamics 365 F&O and Iterable 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 Dynamics 365 F&O and Iterable

Feed the real customer, order, and revenue records from Dynamics 365 F&O into Iterable so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. Dynamics 365 F&O holds exactly that: Customer Invoices, Vendor Invoices, General Journal Entries, On-hand Inventory that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs Customer Invoices, Vendor Invoices, General Journal Entries, On-hand Inventory in Dynamics 365 F&O with Catalogs, Commerce / Purchases, Export data, Users in Iterable in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Iterable works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Iterable flow back onto the record in Dynamics 365 F&O.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Distribute product and price master data from F&O to downstream channels through a synced database.
  • 02 Sync customers, vendors, and released products into an operational database that internal apps read instead of calling OData directly.
  • 03 Write list subscribe/unsubscribe changes from a CRM back into Iterable Lists so suppression and opt-in state stay current before the next send.
  • 04 Two-way sync User profiles and their custom data fields between Iterable and a Postgres database or CRM so attributes and subscription state stay aligned in both systems.

Common sync patterns

One customer identity across both systems

A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.

Lifecycle triggers from back-office events

A first order, a renewal, or a lapsed account recorded in Dynamics 365 F&O appears in Iterable within seconds, ready to start or stop a lifecycle campaign.

Where Iterable captures new people: signups become customer records

Registrations, form fills, or new subscribers in Iterable create or update the corresponding record in Dynamics 365 F&O, so the back office sees them without anyone re-keying.

What you can sync between Dynamics 365 F&O and Iterable

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.

Dynamics 365 F&O objects Iterable objects How this pairing syncs
General Journal Entries GL postings; read-only extracts for consolidated finance reporting. Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. General Journal Entries is specific to Dynamics 365 F&O and Catalogs to Iterable — each maps to any object or custom field on the other side.
On-hand Inventory Stock positions; read out to storefronts and internal apps for availability. Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. On-hand Inventory is specific to Dynamics 365 F&O and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side.
Customers Customer master records; kept aligned with CRM accounts in two-way 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. Customers is specific to Dynamics 365 F&O and Export data to Iterable — each maps to any object or custom field on the other side.
Vendors Supplier master records; synced with procurement and AP tools. 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. Vendors is specific to Dynamics 365 F&O and Users to Iterable — each maps to any object or custom field on the other side.
Released Products Sellable product master; read out to commerce channels and CRM catalogs. 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}. Released Products is specific to Dynamics 365 F&O and Events to Iterable — each maps to any object or custom field on the other side.
Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. 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. Sales Orders is specific to Dynamics 365 F&O and Campaigns to Iterable — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 F&O and Iterable

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.

Dynamics 365 F&O Iterable Sub-second propagation

DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.

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

Iterable Dynamics 365 F&O 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 Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
  • 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.
What ships with Dynamics 365 F&O ⇄ Iterable

Connect Dynamics 365 F&O and Iterable for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Dynamics 365 F&O or Iterable instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 F&O or Iterable 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 Dynamics 365 F&O or Iterable record.

Observability

Monitoring

Track your Dynamics 365 F&O ⇄ Iterable sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 F&O and Iterable.

How the Dynamics 365 F&O and Iterable connectors work

Dynamics 365 F&O

Integration surface
OData REST endpoint over data entities, plus the Data Management Framework for batch
Authentication
OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
Change detection
Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
Capabilities
read · write · CDC · webhooks
Rate limits
OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
Dynamics 365 F&O setup guide

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.
How it works

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

    Choose tables

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

Dynamics 365 F&O and Iterable 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 374 integrations available for Dynamics 365 F&O and Iterable.

Popular · 7 of 374
All Dynamics 365 F&O integrations All Iterable 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