Real-time
Two-way sync
Changes in Intercom or Microsoft Dynamics GP instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ ERP
Intercom to Microsoft Dynamics GP integration — real-time, two-way sync
Keep Intercom and Microsoft Dynamics GP 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 Intercom and Microsoft Dynamics GP
Close the gap between front office and back office: Intercom and Microsoft Dynamics GP share customers and status in real time, in both directions.
Intercom holds the customer relationship; Microsoft Dynamics GP runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Conversations, Tickets, Data Events, Custom Data Attributes in Intercom with Sales Documents (SOP), Purchase Orders (POP), Inventory Items (IV), GL Accounts & Journal Entries in Microsoft Dynamics GP field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- 02 Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
- 03 Replicate GP company databases into a warehouse for financial and operational reporting.
- 04 Sync customers and invoices between GP and a CRM so sales sees balances and billing history.
Common sync patterns
Where Microsoft Dynamics GP is the finance system of record: money status on the account
Invoice and payment state from Microsoft Dynamics GP shows on the account in Intercom, so reps see balances before promising the next order.
One customer master
Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
Where Microsoft Dynamics GP manages people and org data: keep Intercom aligned
Owners, territories, and org structure informed by Microsoft Dynamics GP stay current in Intercom.
What you can sync between Intercom and Microsoft Dynamics GP
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.
| Intercom objects | Microsoft Dynamics GP objects | How this pairing syncs | |
|---|---|---|---|
| Conversations Support and sales threads sync outward for analytics and CRM context. | Inventory Items (IV) Item master and quantity data mirrored to ecommerce and planning systems. | Conversations is specific to Intercom and Inventory Items (IV) to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Tickets Structured ticket records track issues alongside conversational threads. | GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. | Tickets is specific to Intercom and GL Accounts & Journal Entries to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | Data Events is specific to Intercom and Receivables & Payables Transactions to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Company Databases Per-company SQL databases that define the scope of any sync. | Custom Data Attributes is specific to Intercom and Company Databases to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Customers Receivables master records (RM tables) synced with CRMs and billing tools. | Tags is specific to Intercom and Customers to Microsoft Dynamics GP — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Vendors Payables master records aligned with procurement and AP automation. | Segments is specific to Intercom and Vendors to Microsoft Dynamics GP — each maps to any object or custom field on the other side. |
How changes propagate between Intercom and Microsoft Dynamics GP
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.
Intercom Microsoft Dynamics GP Sub-second propagation
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.
Microsoft Dynamics GP Intercom 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 Intercom through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Intercom ⇄ Microsoft Dynamics GP
Connect Intercom and Microsoft Dynamics GP for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Microsoft Dynamics GP connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Intercom or Microsoft Dynamics GP 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 Intercom or Microsoft Dynamics GP record.
Observability
Monitoring
Track your Intercom ⇄ Microsoft Dynamics GP sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Intercom and Microsoft Dynamics GP.
How the Intercom and Microsoft Dynamics GP connectors work
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
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
How it works
How to connect Intercom to Microsoft Dynamics GP — 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 Intercom and Microsoft Dynamics GP with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Intercom
connected
Microsoft Dynamics GP
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Intercom and Microsoft Dynamics GP 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 · Intercom ⇄ Microsoft Dynamics GPCustomers 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.
Intercom Microsoft Dynamics GPCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Intercom and Microsoft Dynamics GP integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Microsoft Dynamics GP: authenticate both systems, choose the objects to sync (such as Intercom's Conversations and Tickets), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Intercom side: Conversations, Tickets, Data Events, Custom Data Attributes, plus custom fields where Intercom exposes them. On the Microsoft Dynamics GP side: Sales Documents (SOP), Purchase Orders (POP), Inventory Items (IV), GL Accounts & Journal Entries. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Intercom and Microsoft Dynamics GP: Where Microsoft Dynamics GP is the finance system of record: money status on the account; One customer master; Where Microsoft Dynamics GP manages people and org data: keep Intercom aligned. Invoice and payment state from Microsoft Dynamics GP shows on the account in Intercom, so reps see balances before promising the next order.
-
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Intercom: Conversations are composed of nested conversation parts (messages, notes, assignments), which matters when replicating full thread history. 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 Intercom and Microsoft Dynamics GP without custom code.
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
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 512 integrations available for Intercom and Microsoft Dynamics GP.
Popular · 7 of 512
- Intercom ⇄ Microsoft Dynamics NAV
-
Intercom ⇄ Plex ERP -
Intercom ⇄ QAD ERP -
Intercom ⇄ Rootstock ERP -
Microsoft Dynamics GP ⇄ DealCloud -
Microsoft Dynamics GP ⇄ Chorusai -
Microsoft Dynamics GP ⇄ Clari
No integrations match .
