A per-tenant Business Central AL extension that keeps contacts, tags, and campaign engagement in two-way sync with Mailchimp — built, installed, and supported by ECOSIRE on your tenant. One-time license from $249.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A per-tenant Business Central AL extension that keeps contacts, tags, and campaign engagement in two-way sync with Mailchimp — built, installed, and supported by ECOSIRE on your tenant.
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Mailchimp Connector for Dynamics 365 is a build-to-order extension for Microsoft Dynamics 365 Business Central, written in AL and delivered as a per-tenant extension installed directly on your environment. It is not an instant AppSource download — ECOSIRE scopes it to your audiences and field model, builds it, installs it on your sandbox first, then promotes it to production with you.
Bi-directional contact sync between Business Central Contacts and Mailchimp audiences, keyed on email with configurable conflict resolution
Tag sync in both directions, with governance rules so BC categories and Mailchimp tags stay aligned
Map CRM/BC marketing segments to specific Mailchimp audiences via a configuration page (table-extension backed)
Pull open, click, bounce, unsubscribe and per-campaign stats into BC and display them on the Contact card via page extension
Create and schedule Mailchimp campaigns from within Business Central against a chosen audience
Field mapping UI for Mailchimp merge fields ↔ BC contact fields, including custom fields
The connector establishes a two-way sync between Business Central Contacts (and CRM marketing segments) and Mailchimp audiences. New and updated contacts flow to the right Mailchimp audience; subscriber status, tags, and merge fields flow back into Business Central. Engagement data — opens, clicks, bounces, unsubscribes, and per-campaign stats — is pulled into BC and surfaced on the Contact card via page extensions, so your marketers see Mailchimp activity without leaving the ERP.
Under the hood it uses table and page extensions to add mapping and engagement fields, event subscribers on contact insert/modify to queue changes, and a Job Queue entry that calls the Mailchimp Marketing API on a schedule you control. Outbound sync respects your field mapping and dedup rules (email-based matching, audience-to-segment mapping, tag governance) so you don't duplicate subscribers or overwrite curated data. A dedicated permission set scopes who can configure the connector and trigger syncs.
Optional Dataverse / Power Platform alignment is available where your CRM marketing lists live in Dataverse rather than native BC. Because it's your own per-tenant extension, the code, the mappings, and the sync cadence are yours — and ECOSIRE supports them. Pricing is a one-time USD 249 build; installation and the support window are included.
Runs campaigns in Mailchimp but needs the audience to stay current with the D365 CRM contact base — and wants engagement visible to sales without manual CSV exports.
Owns the BC environment and wants a clean per-tenant extension with a scoped permission set and Job Queue, not a fragile manual integration or an opaque third-party app.
Wants to see who opened and clicked recent campaigns directly on the Contact card so follow-up is timed and informed.
Achetez la licence sur ecosire.com et téléchargez le module ZIP Mailchimp Connector for Dynamics 365 depuis le tableau de bord de votre compte.
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez Mailchimp Connector for Dynamics 365 et appuyez sur Installer.
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Two-way contact + tag sync with dedup controls | ||||
| Campaign engagement (opens/clicks/stats) pulled onto the Contact card | ||||
| Installed and supported on your tenant by the builder | ||||
| Tailored to your exact audiences and custom field model | ||||
| You own the source code (per-tenant extension) | ||||
| Fixed, low one-time cost with included install | ||||
| Create and schedule Mailchimp campaigns from inside Business Central | ||||
| Upgrade-safe AL extension (table/page extensions, event subscribers, Job Queue) |
No. This is a build-to-order, per-tenant AL extension. ECOSIRE scopes it to your Mailchimp audiences and Business Central field model, builds it, installs it on your sandbox for validation, then promotes it to production with you. There is no public AppSource listing to download.
Typical lead time is 1–2 weeks from when we receive your Mailchimp API access and a short mapping brief (which audiences map to which segments, which fields, tag rules). Simpler one-audience setups land faster; heavier custom field mapping or Dataverse alignment can extend it. We confirm a firm date after the scoping call.
Sync is keyed on email with pre-sync duplicate detection. You define field-level conflict rules (which side wins per field) and tag governance, so curated Mailchimp data isn't clobbered by BC and vice versa. Only changed records are queued via event subscribers, keeping API usage within Mailchimp rate limits.
The one-time build includes an initial support window for fixes and tuning after go-live. Because the extension is yours per-tenant, ECOSIRE can also provide ongoing support and adapt it as your audiences, fields, or Business Central version change — quoted separately as an optional retainer. You retain the source code either way.
Yes, where your marketing lists live in Dataverse rather than native BC, we can align the connector to read from Dataverse via the BC–Dataverse integration so the same engagement and tag data still surfaces in Business Central. This is part of scoping and may affect lead time.
It is built as a standard AL per-tenant extension using table/page extensions and event subscribers — the supported extensibility model — so it upgrades cleanly with Business Central. If a Microsoft platform change ever affects an API surface, support covers the adjustment within your support window.
A per-tenant Business Central AL extension that keeps contacts, tags, and campaign engagement in two-way sync with Mailchimp — built, installed, and supported by ECOSIRE on your tenant.