Skip to content
Business productivity ⇄ Accounting and finance

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

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

Connect the financial records in Recurly with the work happening in Microsoft Dynamics 365, so both stay current without exports or copy-paste.

Recurly holds the financial truth: who the customers are, what they were billed, what they paid. Microsoft Dynamics 365 is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Subscriptions, Plans, Invoices, Transactions in Recurly and Quotes, Orders & Invoices, Products, Activities, Custom Tables in Microsoft Dynamics 365 in sync, bi-directionally and in real time. Whatever records Microsoft Dynamics 365 keeps and whatever events it produces, the overlap with Recurly is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

Common use cases

  • 01 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 02 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 03 Two-way sync of accounts and contacts with a Postgres or SQL database so engineers query SQL while sales works in Dynamics.
  • 04 Keep opportunities and orders consistent with the ERP or billing system without manual re-entry.

Common sync patterns

Where Microsoft Dynamics 365 tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Where Microsoft Dynamics 365 handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Recurly next to the customer they are helping, without logging into the finance system.

Where Microsoft Dynamics 365 collects payments or triggers charges: events land in Recurly

Payment and charge activity flows into Recurly as it happens, so the books reflect reality without manual reconciliation.

What you can sync between Microsoft Dynamics 365 and Recurly

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 Recurly objects How this pairing syncs
Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Opportunities is specific to Microsoft Dynamics 365 and Plans to Recurly — each maps to any object or custom field on the other side.
Cases (Incidents) Support records shared with ticketing tools and product databases. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Cases (Incidents) is specific to Microsoft Dynamics 365 and Invoices to Recurly — 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. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Quotes, Orders & Invoices is specific to Microsoft Dynamics 365 and Transactions to Recurly — each maps to any object or custom field on the other side.
Products Catalog records aligned with ERP item masters. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Products is specific to Microsoft Dynamics 365 and Line Items to Recurly — each maps to any object or custom field on the other side.
Activities Emails, calls, and tasks captured for engagement analytics. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Activities is specific to Microsoft Dynamics 365 and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics 365 and Recurly

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.

Microsoft Dynamics 365 Recurly Sub-second propagation

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 Recurly through its API, with automatic retries and rate-limit backoff.

Recurly Microsoft Dynamics 365 Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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

Rate-limit considerations

  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Microsoft Dynamics 365 ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Microsoft Dynamics 365 and Recurly connectors work

Microsoft Dynamics 365

Integration surface
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)
Change detection
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
Capabilities
read · write · CDC · webhooks
Microsoft Dynamics 365 setup guide

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

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

    Choose tables

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

Microsoft Dynamics 365 and Recurly 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
CSA STAR
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 508 integrations available for Microsoft Dynamics 365 and Recurly.

Popular · 7 of 508
All Microsoft Dynamics 365 integrations All Recurly 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