Microsoft Dynamics GP and Mailchimp integration

What moves between them

Customer records flow one direction from Dynamics GP into Mailchimp. ml-connector polls GP at a scheduled interval (daily, weekly, or tied to your month-end close), reads the Customers and Receivables Invoices entities where ModifiedDate is recent, and pushes matching customer records into Mailchimp as list members. Completed orders from Receivables Invoices sync as e-commerce orders in Mailchimp's order tracking, tagged with the customer ID so Mailchimp can correlate them for segmentation. Because Mailchimp has no direct financial reporting, only the invoice total and basic metadata (date, number, payment status inferred from GP record status) transfer. New customers and order changes in GP appear in Mailchimp within the polling window.

How ml-connector handles it

ml-connector maintains a Windows domain account credential set for Dynamics GP and an API key for Mailchimp, encrypted and stored per customer. On each poll cycle, it connects to the customer's GP SBA endpoint using Windows Authentication (Kerberos or NTLM), queries Customers with a ModifiedDate filter to find new or changed records, and fetches related Receivables Invoices for those customers. Customer name, billing address, and contact email map to Mailchimp list member fields; invoice number, date, and total map to e-commerce order records with the customer as the buyer. Because Dynamics GP requires the Company name as the actual SQL Server database name (not a human-readable alias) and the SBA endpoint is customer-specific, ml-connector prompts for the exact server URL, tenant name, and company database name during setup. The polling frequency is configurable per customer, and ml-connector tracks which records were last synced to avoid re-sending unchanged data. Retries handle transient network or authentication failures, and a full audit trail logs every customer and order upsert.

A real-world example

A regional office supply distributor runs Microsoft Dynamics GP on-premises for sales, AR, and inventory. They maintain a customer email list in Mailchimp for promotional campaigns but have been uploading customer lists monthly by hand and never had accurate order history in Mailchimp for upsell campaigns. Before the integration, the marketing team worked from stale exports and could not segment buyers by purchase recency or category. With Dynamics GP and Mailchimp connected, each month's polling cycle automatically syncs all customers with email addresses into Mailchimp, and completed orders appear tagged by customer, letting the marketing team build campaigns for repeat buyers and recently inactive accounts. The monthly manual upload process is gone, and Mailchimp now has current order data for smarter audience segmentation.

What you can do

• •Automatically sync new and changed customers from Dynamics GP into Mailchimp audience lists, with email address and billing location.
• •Mirror completed orders from GP Receivables Invoices into Mailchimp's e-commerce order tracker for buyer-based segmentation and remarketing.
• •Authenticate GP using Windows domain credentials (Kerberos or NTLM) and Mailchimp with API key, handling both at encryption and request time.
• •Poll Dynamics GP on a schedule you control (daily, weekly, or custom interval) with ModifiedDate filtering to fetch only changed records.
• •Maintain a full audit trail of every customer and order sync, with error replay and retry logic for transient failures.

Questions

Does Microsoft Dynamics GP expose all customer and order data through its APIs?

Dynamics GP exposes customers, receivables invoices, and other financial records through its REST SBA or SOAP Web Services. However, SBA availability depends on the GP version (GP 2015 and later); older on-premises installs may only have SOAP available. ml-connector works with both, and the customer's IT team can verify which is available in their instance.

What happens if a customer's Dynamics GP server is offline or the Windows domain account password changes?

ml-connector tracks polling failures in its audit log and alerts you on the first failed sync attempt. If the server is offline or credentials are stale, ml-connector backs off and retries at the next scheduled interval; the customer can fix the issue and the next poll picks up where the previous one left off. All synced records are preserved in Mailchimp until explicitly removed.

Can Mailchimp data flow back into Dynamics GP (two-way sync)?

This integration is one-way, from Dynamics GP to Mailchimp. Mailchimp has no GL accounts, invoices, or vendor records, so there is no financial data to write back. If you need to write customer status or subscription changes from Mailchimp back into GP, that would require a separate flow and additional design work.