CRM migration

Migrate from Click to Mailchimp

Field-level mapping, validation, and rollback between Click and Mailchimp. We move data and schema; workflows are rebuilt natively in Mailchimp.

Click logo

Click

Source

Mailchimp

Destination

Mailchimp logo

Compatibility

33%

3 of 9

objects map 1:1 between Click and Mailchimp.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Click logo

Click

What's pushing teams away

  • ClickDimensions is limited to the Microsoft Dynamics 365 ecosystem, making it difficult to switch to non-Microsoft CRMs without losing marketing activity history.
  • The platform's interface and feature set lag behind standalone marketing automation tools, prompting teams to move to HubSpot or Marketo.
  • Support responsiveness and product update cadence have been cited as pain points by mid-market customers.
  • Custom field usage on the free plan is capped at 60 uses, which frustrates teams that need broader automation without upgrading.

Choosing

Mailchimp logo

Mailchimp

What's pulling them in

  • Generous free tier with up to 500 contacts allows small teams to validate email marketing before committing to a paid plan.
  • Intuitive drag-and-drop email builder and 130+ templates let non-technical users produce professional campaigns without HTML or CSS knowledge.
  • 300+ native integrations, especially Canva and Shopify, make it easy to connect existing tools without custom development work.
  • Detailed open-rate, click-through, and campaign analytics give small businesses actionable insights without a dedicated marketing team.
  • One-platform consolidation of email campaigns, automations, landing pages, and ads reduces tool sprawl for lean marketing teams.

Object mapping

How Click objects map to Mailchimp

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)

maps to

Mailchimp

Audience Member

1:1
Fully supported

Contacts 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)

maps to

Mailchimp

Tags and Merge Fields

lossy
Fully supported

ClickDimensions 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)

maps to

Mailchimp

Campaign Archive Records

1:many
Fully supported

ClickDimensions 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)

maps to

Mailchimp

Groups and Tags

lossy
Fully supported

ClickDimensions 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)

maps to

Mailchimp

Merge Fields and Tags

lossy
Fully supported

ClickDimensions 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)

maps to

Mailchimp

Tags

lossy
Fully supported

ClickDimensions 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)

maps to

Mailchimp

Audience Member (unsubscribed or pending)

1:1
Fully supported

ClickDimensions 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)

maps to

Mailchimp

Merge Fields

1:1
Fully supported

ClickDimensions 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)

maps to

Mailchimp

Notes (admin reference document)

lossy
Fully supported

ClickDimensions 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.

Gotchas + challenges

What specifically takes care here

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 logo

Click gotchas

Medium

Custom Field write limit on Free Forever plans

High

ClickDimensions does not store contacts independently

Medium

Export and Import tools move Click records between Dynamics environments

Mailchimp logo

Mailchimp gotchas

High

Contact count includes unsubscribed and non-subscribed records

High

Automation workflows cannot be exported

Medium

Account suspensions trigger silently during migration

Medium

Template HTML is Mailchimp-specific and may not render in other platforms

Medium

E-commerce data requires active store connection

Pair-specific challenges

  • ClickDimensions requires access to the underlying Dynamics 365 instance

    ClickDimensions does not store contacts, accounts, or leads independently—it is an extension layer for Microsoft Dynamics 365 CRM. The base CRM records must be extracted from Dynamics, not from ClickDimensions exports alone. During discovery, we confirm the connected Dynamics environment, authenticate to the Dynamics Web API, and extract contacts from there alongside ClickDimensions-specific annotation records. Targeting only ClickDimensions export tools will result in partial or empty records at the destination because the contact name, email, and address fields are not stored in ClickDimensions itself.

  • ClickDimensions Export tools produce Dynamics-compatible output only

    ClickDimensions provides built-in Export and Import features within its settings interface designed for moving Click entities between Dynamics environments. These exports produce file formats and field names that align with the Dynamics CRM schema, not with Mailchimp's API or CSV import format. We do not use the built-in Export tools for this migration. Instead, we call the ClickDimensions REST API and the Dynamics 365 Web API to extract records in a format we can transform and write to the Mailchimp Marketing API directly.

  • Mailchimp imposes a 90-day historical engagement window for campaign data

    Mailchimp's native migration tools and API import contacts, lists, and merge fields without time restriction, but historical open and click engagement data beyond 90 days is not guaranteed to transfer through Mailchimp's standard import process. We capture ClickDimensions campaign engagement history (open dates, click URLs, bounce records) as custom merge fields on the contact record and as a CSV archive so that engagement history is not lost. The 90-day limitation affects live campaign metrics in Mailchimp's reporting dashboard, not the underlying contact data.

  • ClickDimensions workflows and automation logic do not migrate to Mailchimp Customer Journeys

    ClickDimensions workflows are tied to Dynamics CRM triggers and business logic that is specific to the Dynamics environment. Mailchimp's Customer Journeys automation builder operates on a different model—event-triggered, delay-based, and action-oriented within the Mailchimp ecosystem. We do not migrate workflows, event branding configurations, or survey logic as functional code. We deliver a written inventory of every active ClickDimensions workflow and event setup with a recommended Mailchimp Customer Journey equivalent. The customer's admin rebuilds these post-migration.

  • Free Forever plan customers face a 60-use Custom Field write cap during migration

    ClickDimensions Free Forever plans allow only 60 uses of Custom Field write operations across the entire workspace. Each API call to Set Custom Field Value counts as one use. We monitor usage during the extraction phase and either work within the limit for the contact and annotation records that require custom field reads, or advise the customer to upgrade before migration begins. Exceeding the limit blocks new custom field writes until the plan is upgraded. Standard and Professional ClickDimensions plans do not impose this cap.

Migration approach

Six steps for a successful Click to Mailchimp data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Click logo

Click

Source

Strengths

  • Native integration with Microsoft Dynamics 365 CRM with bidirectional data sync.
  • Marketing automation (email, events, web tracking, surveys) in a single add-on layer.
  • Built-in export and import tools for moving Click records between Dynamics environments.
  • Web tracking and survey functionality without requiring a separate marketing platform.

Weaknesses

  • Tied exclusively to the Microsoft Dynamics 365 ecosystem, limiting destination options for migrations.
  • Free plan imposes hard limits on Custom Field usage that affect automation-heavy deployments.
  • Marketing feature set lags behind dedicated marketing automation platforms.
  • Product update cadence and customer support responsiveness trail competitors.
Mailchimp logo

Mailchimp

Destination

Strengths

  • Free plan up to 500 contacts makes it the lowest-friction entry point for new email marketers.
  • Drag-and-drop builder and template library produce polished emails without design or coding skills.
  • Strong deliverability reputation backed by years of email infrastructure expertise.
  • 300+ native integrations cover the most common marketing stack combinations out of the box.
  • Consolidated platform for email, automation, landing pages, and ads reduces the number of tools small teams must manage.

Weaknesses

  • Contact-based pricing model charges for unsubscribed and non-subscribed records, inflating costs relative to competitors.
  • Five-step automation limit on Standard tier forces upgrades for basic customer journeys, a frequently cited frustration.
  • Template HTML is Mailchimp-specific and does not export cleanly for use in other email platforms.
  • Post-Intuit roadmap uncertainty means customers cannot confidently plan long-term platform investments.
  • Account suspension risk without clear pre-warning disrupts campaign scheduling for affected businesses.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Click and Mailchimp.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    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

    A

    Click exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Click to Mailchimp migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Click to Mailchimp data migrations

Answers to the questions buyers ask most during Click to Mailchimp migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Click to Mailchimp migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between two and three weeks for organizations with up to 10,000 contacts and a single Dynamics 365 instance. Migrations with large event registration histories (over 2,000 events), survey response datasets spanning multiple surveys, or complex custom field structures move to four to six weeks because of API extraction time and the reconciliation phase. The primary driver of timeline is the data extraction from Dynamics 365 and ClickDimensions APIs, not the Mailchimp import itself.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Click.
Land in Mailchimp, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day