Real-time
Two-way sync
Changes in Microsoft Dynamics 365 Sales or Recurly instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Microsoft Dynamics 365 Sales to Recurly integration — real-time, two-way sync
Keep Microsoft Dynamics 365 Sales 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 Sales and Recurly
Sync customers, invoices, and payment status between Recurly and Microsoft Dynamics 365 Sales in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Microsoft Dynamics 365 Sales knows the relationship: who the contacts are and what is in motion with the account. Recurly knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Transactions, Line Items, Coupons and Redemptions, Billing Info in Recurly to Custom Tables, Accounts, Contacts, Leads in Microsoft Dynamics 365 Sales with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
Common use cases
- 01 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.
- 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 03 Bi-directional sync of accounts, contacts, and opportunities with a SQL database so teams query CRM data without OData or FetchXML.
- 04 Write product usage and warehouse-computed scores onto Dataverse tables so sellers see them in the model-driven app.
Common sync patterns
Where Microsoft Dynamics 365 Sales tracks deals: closed-won creates the finance record
A won opportunity creates or updates the customer in Recurly with the right billing details, so invoicing starts without re-keying.
Payment status on the account
Invoice and payment status from Recurly appears on the account in Microsoft Dynamics 365 Sales, so reps see overdue balances before they promise the next order.
Billing detail changes flow back
When a contact or address is corrected in Microsoft Dynamics 365 Sales, Recurly gets the update before the next invoice goes out.
What you can sync between Microsoft Dynamics 365 Sales 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 Sales objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. | 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. | |
| Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Custom Tables is specific to Microsoft Dynamics 365 Sales and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Contacts Person records linked to accounts; synced with marketing and support systems. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Contacts is specific to Microsoft Dynamics 365 Sales and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. | |
| Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). | Leads is specific to Microsoft Dynamics 365 Sales and Billing Info to Recurly — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Opportunities is specific to Microsoft Dynamics 365 Sales and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics 365 Sales 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 Sales Recurly 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 Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Microsoft Dynamics 365 Sales 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 Sales through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
- 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 Sales ⇄ Recurly
Connect Microsoft Dynamics 365 Sales and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365 Sales–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics 365 Sales 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 Sales or Recurly record.
Observability
Monitoring
Track your Microsoft Dynamics 365 Sales ⇄ 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 Sales and Recurly.
How the Microsoft Dynamics 365 Sales and Recurly connectors work
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.
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 Sales 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.
- 01
Connect your apps
Authenticate Microsoft Dynamics 365 Sales 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.
Microsoft Dynamics 365 Sales
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics 365 Sales 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.
objects · Microsoft Dynamics 365 Sales ⇄ RecurlyCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Microsoft Dynamics 365 Sales RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics 365 Sales and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics 365 Sales and Recurly: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365 Sales's Accounts and Invoices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Sales and Recurly 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 Sales and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft Dynamics 365 Sales–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Microsoft Dynamics 365 Sales and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Microsoft Dynamics 365 Sales: Dataverse change tracking with delta tokens, plus registered webhooks on table events. On Recurly: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Transactions, Line Items, Coupons and Redemptions, Billing Info, plus custom fields where Recurly exposes them. On the Microsoft Dynamics 365 Sales side: Custom Tables, Accounts, Contacts, Leads. Stacksync auto-detects both schemas and converts types between the two systems.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 426 integrations available for Microsoft Dynamics 365 Sales and Recurly.
Popular · 6 of 426
-
Microsoft Dynamics 365 Sales ⇄ Chargebee -
Microsoft Dynamics 365 Sales ⇄ QuickBooks -
Recurly ⇄ Freshsales -
Recurly ⇄ Freshworks CRM -
Recurly ⇄ Gladly -
Recurly ⇄ Gorgias
No integrations match .
