CRM migration
Field-level mapping, validation, and rollback between Click and Mailchimp. We move data and schema; workflows are rebuilt natively in Mailchimp.
Click
Source
Mailchimp
Destination
Compatibility
3 of 9
objects map 1:1 between Click and Mailchimp.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from ClickDimensions to Mailchimp is a migration from a marketing automation add-on for Microsoft Dynamics 365 to a standalone email marketing platform. ClickDimensions does not store contacts independently; it extends the Dynamics 365 data model with marketing attributes, custom fields, email send records, event registrations, web tracking events, and survey responses. We extract the underlying CRM records from the connected Dynamics instance alongside the ClickDimensions annotation layer, then map them into Mailchimp's Audience structure with Tags, merge fields, and campaign history. The key migration risk is that ClickDimensions's built-in Export and Import tools are designed for Dynamics-to-Dynamics transfers and do not produce Mailchimp-compatible output—we use the ClickDimensions API and the Dynamics Web API to extract records, then write directly to the Mailchimp API. We do not migrate ClickDimensions Workflows, Event Branding configurations, or Survey logic as functional code; we deliver a written inventory of these for the customer's admin to rebuild in Mailchimp's automation builder.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Click object lands in Mailchimp, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Click
Contact (Dynamics 365)
Mailchimp
Audience Member
1:1Contacts live in the underlying Microsoft Dynamics 365 instance, not in ClickDimensions itself. We extract contacts from the Dynamics Web API using the connected CRM's credentials, then write to Mailchimp as Audience Members via the Mailchimp API. The Dynamics contactid becomes a custom merge field (DynamicsID) for cross-reference. Email address is the Mailchimp dedupe key. First name, last name, phone, and address fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). Consent flags stored in ClickDimensions custom fields migrate to Mailchimp tags and the EmailOptIn merge field.
Click
Account (Dynamics 365)
Mailchimp
Tags and Merge Fields
lossyClickDimensions links marketing activity to Accounts through the contact-to-account relationship in Dynamics. Accounts do not map to a standalone Mailchimp object. Instead, we attach the Account name as a Mailchimp tag (e.g., TAG: EnterpriseAccount) and a custom merge field (ACCOUNTNAME) to each Contact record that has an Account link. This preserves the company association without requiring a separate object in Mailchimp.
Click
Email Sends (ClickDimensions)
Mailchimp
Campaign Archive Records
1:manyClickDimensions tracks email send records attached to CRM contacts with send date, campaign name, and delivery status. We map these to a combination of Mailchimp campaign history entries (for open/click tracking data that Mailchimp can receive) and a custom campaign archive merge field on each contact (e.g., CAMPAIGNS_SENT, LAST_SEND_DATE). Historical engagement metrics from ClickDimensions (opens, clicks, bounces) are written to custom merge fields on the contact record because ClickDimensions send records do not map to live Mailchimp campaign objects.
Click
Event Registrations (ClickDimensions)
Mailchimp
Groups and Tags
lossyClickDimensions Event entities store registration records linked to CRM contacts, with session choices, registration status, and custom registration fields. We map event names to Mailchimp Groups (e.g., Group Category: Events, Group: Q4 Annual Conference) and registration status (Registered, Waitlisted, Cancelled) to Tags. Custom registration field values map to merge fields with names matching the survey question labels. Event date and location are stored as merge fields on the contact record.
Click
Survey Responses (ClickDimensions)
Mailchimp
Merge Fields and Tags
lossyClickDimensions Survey entities capture response records linked to contacts, with question-answer pairs in custom field structures. We map survey names to Tag categories and question-answer pairs to custom merge fields (question label becomes merge field name, answer becomes value). For surveys with multiple response instances per contact, we use Tags to track which surveys each contact completed and the response date as a Tag value. Customers choose between storing responses as merge fields (for single-instance) or Tags (for multi-instance) during scoping.
Click
Web Tracking Events (ClickDimensions)
Mailchimp
Tags
lossyClickDimensions captures web behavioral events tied to known contacts (via email) or anonymous visitors. Known-contact events migrate as Tags on the matching Mailchimp Audience Member (e.g., TAG: Viewed_Pricing_Page_2025-03-15). Anonymous visitor data without a matching email address is not migrated because Mailchimp Audience Members require an email identifier. The customer may choose to suppress anonymous events or to capture them as a separate document for admin reference.
Click
Leads (Dynamics 365)
Mailchimp
Audience Member (unsubscribed or pending)
1:1ClickDimensions annotates Dynamics Leads with marketing attributes. We migrate Leads with email address, name, company, lead score, and any ClickDimensions custom field values. In Mailchimp, Leads without a confirmed double opt-in are imported as Pending members (status: subscribed with Marketing Permission flag) or as unsubscribed if the lead has requested no marketing contact. The customer's consent management preference determines which approach is used during scoping.
Click
Custom Fields (ClickDimensions)
Mailchimp
Merge Fields
1:1ClickDimensions custom fields on contacts (beyond standard CRM fields) map to Mailchimp merge fields. We create merge fields in Mailchimp via the API before contact import, matching the ClickDimensions field label as the merge field name and the field type (text, number, date, dropdown) as the Mailchimp field type. Free Forever plan customers note that their migration scope is limited by the 60-use Custom Field write cap—we track remaining uses during extraction and fall back to manual UI population for overflow records if the plan is not upgraded before migration.
Click
Activities (Dynamics 365)
Mailchimp
Notes (admin reference document)
lossyClickDimensions creates activity records in Dynamics 365 for email engagement, form submissions, and other interactions. These are standard CRM activity objects that do not have a functional equivalent in Mailchimp's Audience model. We export the activity history as a CSV reference file and deliver it to the customer's admin for use in business intelligence or reporting tools outside Mailchimp. Activity history does not appear on individual contact records in Mailchimp.
| Click | Mailchimp | Compatibility | |
|---|---|---|---|
| Contact (Dynamics 365) | Audience Member1:1 | Fully supported | |
| Account (Dynamics 365) | Tags and Merge Fieldslossy | Fully supported | |
| Email Sends (ClickDimensions) | Campaign Archive Records1:many | Fully supported | |
| Event Registrations (ClickDimensions) | Groups and Tagslossy | Fully supported | |
| Survey Responses (ClickDimensions) | Merge Fields and Tagslossy | Fully supported | |
| Web Tracking Events (ClickDimensions) | Tagslossy | Fully supported | |
| Leads (Dynamics 365) | Audience Member (unsubscribed or pending)1:1 | Fully supported | |
| Custom Fields (ClickDimensions) | Merge Fields1:1 | Fully supported | |
| Activities (Dynamics 365) | Notes (admin reference document)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Click gotchas
Custom Field write limit on Free Forever plans
ClickDimensions does not store contacts independently
Export and Import tools move Click records between Dynamics environments
Mailchimp gotchas
Contact count includes unsubscribed and non-subscribed records
Automation workflows cannot be exported
Account suspensions trigger silently during migration
Template HTML is Mailchimp-specific and may not render in other platforms
E-commerce data requires active store connection
Pair-specific challenges
Migration approach
Discovery and Dynamics environment confirmation
We confirm the connected Microsoft Dynamics 365 instance URL, authenticate to the Dynamics Web API, and audit the ClickDimensions entities in scope: contacts, accounts, leads, email sends, event registrations, survey responses, and any custom fields in use. We identify the ClickDimensions plan tier to determine if the 60-use Custom Field write cap applies and advise on upgrade timing. The discovery output is a written scope document listing every object, record count estimate, and a Custom Field usage report from ClickDimensions.
Mailchimp Audience configuration and merge field creation
We create the destination Mailchimp Audience before any data is written, configure the required merge fields (standard FNAME, LNAME, EMAIL, PHONE, ADDRESS plus custom fields mapped from ClickDimensions), and set up Groups and Tags for event registrations, survey responses, and web tracking history. We configure the Audience's GDPR compliance fields and opt-in status defaults. The customer provides Mailchimp API credentials with appropriate permission scope. All merge field creation happens via the Mailchimp Marketing API before contact import begins.
Data extraction from Dynamics 365 and ClickDimensions API
We extract base CRM records (contacts, accounts, leads) from the Dynamics 365 Web API using OAuth 2.0 authentication. We extract ClickDimensions-specific annotation records (email send history, event registrations, survey responses, custom field values) via the ClickDimensions REST API. We resolve the parent contact reference on every annotation record to ensure records can be linked during Mailchimp import. Any Dynamics contacts without a valid email address are flagged for the customer's admin to review before import.
Data transformation and Mailchimp contact import
We transform extracted records into Mailchimp API-compatible payloads. The Dynamics contact becomes a Mailchimp Audience Member with standard merge fields populated. ClickDimensions annotation data (campaign history, event attendance, survey responses) populates custom merge fields and Tags. We use the Mailchimp Marketing API batch endpoint for large imports with exponential backoff on rate limit responses. Each batch emits a success/failure count. Failed records are retried once and then routed to a reconciliation queue for admin resolution.
Reconciliation and consent verification
We run a record-count reconciliation between the source Dynamics CRM contact total and the Mailchimp Audience member total. We spot-check 25-50 records for field-level accuracy (name, email, company tag, event registration tags, survey response merge fields). We verify that consent flags and opt-in status are correctly set on every record per the customer's GDPR and CAN-SPAM requirements. Any records with missing email, duplicate email addresses, or invalid consent status are documented in a reconciliation report for the customer's admin to resolve.
Cutover, final delta migration, and handoff
We freeze new ClickDimensions writes during the cutover window, run a final delta extraction of any records modified since the initial extraction, write the delta to Mailchimp, and mark the migration complete. We deliver the full contact reconciliation report, the event and survey archive CSV, and the ClickDimensions Workflow and Event inventory document for admin rebuild. We support a five-business-day hypercare window for reconciliation issues. We do not rebuild ClickDimensions workflows or survey logic inside the migration scope; that work is handled separately by the customer's admin team.
Platform deep dives
Click
Source
Strengths
Weaknesses
Mailchimp
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Click and Mailchimp.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Click: Inherits Microsoft Dataverse and Power Platform service-protection limits (per-user request quotas published by Microsoft). The vendor does not publish Click-specific limits beyond those..
Data volume sensitivity
Click exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Click to Mailchimp migration scoping. Not seeing yours? Book a call.
Walk through your Click to Mailchimp migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Click
Other ways to arrive at Mailchimp
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.