Real-time
Two-way sync
Changes in Microsoft Dynamics GP or Recurly instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Microsoft Dynamics GP to Recurly integration — real-time, two-way sync
Keep Microsoft Dynamics GP 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 GP and Recurly
Keep Recurly and Microsoft Dynamics GP agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.
A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.
Stacksync syncs Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts in Recurly with Sales Documents (SOP), Purchase Orders (POP), Inventory Items (IV), GL Accounts & Journal Entries in Microsoft Dynamics GP in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
- 03 Push web or CRM orders into Sales Order Processing through eConnect instead of manual entry.
- 04 Keep item and inventory data aligned with an ecommerce storefront.
Common sync patterns
Where Recurly handles billing: invoices land in Microsoft Dynamics GP
Invoices and payment activity from the billing side post through to the enterprise system automatically.
Migration without a hard cutover
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
One customer and vendor master
Where both systems keep records of the same organizations, corrections made in either propagate to the other.
What you can sync between Microsoft Dynamics GP 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 GP objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. | Receivables & Payables Transactions is specific to Microsoft Dynamics GP and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Company Databases Per-company SQL databases that define the scope of any sync. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Company Databases is specific to Microsoft Dynamics GP and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Customers Receivables master records (RM tables) synced with CRMs and billing tools. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Customers is specific to Microsoft Dynamics GP and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Vendors Payables master records aligned with procurement and AP automation. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Vendors is specific to Microsoft Dynamics GP and Transactions to Recurly — each maps to any object or custom field on the other side. | |
| Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. | Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Sales Documents (SOP) is specific to Microsoft Dynamics GP and Line Items to Recurly — each maps to any object or custom field on the other side. | |
| Purchase Orders (POP) Procurement documents reconciled with receiving and vendor systems. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Purchase Orders (POP) is specific to Microsoft Dynamics GP and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics GP 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 GP Recurly Sub-second propagation
DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Microsoft Dynamics GP 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 applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.
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 GP ⇄ Recurly
Connect Microsoft Dynamics GP and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics GP–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics GP 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 GP or Recurly record.
Observability
Monitoring
Track your Microsoft Dynamics GP ⇄ 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 GP and Recurly.
How the Microsoft Dynamics GP and Recurly connectors work
Microsoft Dynamics GP
- Integration surface
- SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
- Authentication
- SQL Server credentials or Windows authentication
- Change detection
- SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
- Capabilities
- read · write · CDC
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 GP 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 GP 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 GP
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics GP 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 GP ⇄ 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 GP RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics GP and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics GP and Recurly: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics GP's Receivables & Payables Transactions and Company Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Microsoft Dynamics GP: SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments. Authentication: SQL Server credentials or Windows authentication. Recurly: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Recurly: List endpoints support incremental pulls via sort=updated_at (or created_at) with begin_time/end_time filters, so polling fetches only records changed since the last run. Microsoft Dynamics GP: Microsoft has announced the end of the Dynamics GP product lifecycle, which makes sync-out and migration integrations a common requirement. Stacksync's field mapping accounts for these differences between Microsoft Dynamics GP and Recurly 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 GP 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 GP and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft Dynamics GP–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Microsoft Dynamics GP and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 500 integrations available for Microsoft Dynamics GP and Recurly.
Popular · 6 of 500
-
Microsoft Dynamics GP ⇄ Stripe -
Microsoft Dynamics GP ⇄ Coupa -
Microsoft Dynamics GP ⇄ Zuora -
Microsoft Dynamics GP ⇄ Adyen -
Recurly ⇄ Epicor ERP -
Recurly ⇄ Extensiv (3PL Central)
No integrations match .
