CRM migration

Migrate from Click to Microsoft Dynamics 365 Sales

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

Click logo

Click

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

80%

8 of 10

objects map 1:1 between Click and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from ClickDimensions to Microsoft Microsoft Dynamics 365 Sales is a two-part extraction: base CRM records (Contacts, Accounts, Leads, Opportunities) live in the underlying Dynamics 365 instance and must be sourced from there, while ClickDimensions-specific marketing activity records (Email Sends, Event Registrations, Web Tracking Events, Survey Responses) require API extraction and field-level mapping to their Dynamics equivalents. ClickDimensions does not store contacts independently — it extends Dynamics CRM — so the first discovery step is always identifying the source Dynamics environment and pulling base CRM records from its API. We preserve the Contact-to-Account lookup relationship, migrate email send history as Campaign Activities or EmailMessages, event registrations as Campaign Responses, web tracking as custom Activity records, and survey responses as Notes or custom fields. Workflows, marketing email templates, and event-based automations do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Microsoft Dynamics 365 Sales or Power Automate.

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

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Click objects map to Microsoft Dynamics 365 Sales

Each row shows how a Click object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Click

Contact

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Contacts are stored in the underlying Microsoft Dynamics 365 CRM instance, not in ClickDimensions itself. We extract Contact records from the source Dynamics environment via the Dataverse API or the ClickDimensions Export tool, then import them into Microsoft Dynamics 365 Sales as Contact records. The Contact's AccountId lookup resolves to the Account record imported in the preceding step. Email address serves as the dedupe key. Any ClickDimensions-specific contact annotations (consent flags, email engagement scores) migrate as custom fields on Contact.

Click

Account

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Accounts are stored in the underlying Dynamics 365 instance and link to Contacts through the Contact's AccountId lookup. We extract Account records first in the migration sequence so that Contact imports can satisfy the required lookup relationship at insert time. Account Name serves as the dedupe key. Industry, AnnualRevenue, NumberOfEmployees, and Website from the source Dynamics environment map directly to the corresponding Account fields.

Click

Lead

maps to

Microsoft Dynamics 365 Sales

Lead

1:1
Fully supported

Leads are standard Dynamics 365 CRM records that can receive ClickDimensions marketing annotations. We extract Leads from the source Dynamics instance along with any ClickDimensions custom field values and lead-scoring attributes that the customer wants preserved. Lead Status from the source maps to the Lead Status picklist values in the destination Microsoft Dynamics 365 Sales org.

Click

Opportunity

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

Opportunities from the source Dynamics 365 instance migrate to Microsoft Dynamics 365 Sales Opportunities with StageName, Amount, CloseDate, and OwnerId resolved. The source Dynamics pipeline stages map to destination Sales Process stage values, which we configure before migration. Closed-Won and Closed-Lost reasons from the source become custom Opportunity fields if they are not already present in the destination schema.

Click

Email Send

maps to

Microsoft Dynamics 365 Sales

Campaign + CampaignActivity or EmailMessage + Task

1:1
Fully supported

ClickDimensions Email Sends track campaign email activity attached to CRM contacts. Send date, campaign name, recipient count, and delivery status migrate to Microsoft Dynamics 365 Sales as Campaign records with CampaignActivity child records, or as EmailMessage records linked to Contact tasks depending on the destination's campaign tracking configuration. Individual email open and click events are aggregated into campaign-level engagement metrics rather than migrated as separate records.

Click

Event Registration

maps to

Microsoft Dynamics 365 Sales

Campaign Response

1:1
Fully supported

Event management entities in ClickDimensions store registrations linked to CRM contacts. Registration status, session choices, and custom registration fields migrate to Microsoft Dynamics 365 Sales Campaign Response records tied to the corresponding Campaign. Session selections map to Campaign Response details or custom fields on the Response. We preserve the Contact-to-Registration relationship through the Campaign Response's CustomerId lookup.

Click

Web Tracking Event

maps to

Microsoft Dynamics 365 Sales

Custom Activity or Note

lossy
Fully supported

ClickDimensions captures web behavioral events tied to known contacts (via email) or anonymous visitors. Known-contact events with meaningful behavioral data (page visits, form views, content downloads) migrate as custom Activity records linked to the Contact. Anonymous visitor data without a contact identifier is optionally migrated as a Note on the Account for marketing attribution analysis. The customer chooses the activity type during scoping based on reporting needs.

Click

Survey Response

maps to

Microsoft Dynamics 365 Sales

Note or Custom Fields on Contact

lossy
Fully supported

Survey responses in ClickDimensions are linked to contacts and include answer data in custom field structures. We extract response records and map survey questions to destination custom fields on Contact (for structured responses) or to a Note record (for open-text or multi-question responses). If the survey includes scoring or rating data, we preserve it as a custom numeric field on Contact.

Click

ClickDimensions Custom Fields (Tasks)

maps to

Microsoft Dynamics 365 Sales

Custom Fields on CRM Records

1:1
Fully supported

ClickDimensions supports custom fields on tasks and other entities via its API. We extract custom field values attached to Email Sends, Event Registrations, and Web Tracking records and map them to equivalent custom fields in Microsoft Dynamics 365 Sales . On Free Forever plans, the 60-use Custom Field write limit applies during extraction; we batch writes and fall back to manual field population for overflow records if the limit is reached during migration.

Click

Activity (Email, Call, Meeting, Task)

maps to

Microsoft Dynamics 365 Sales

Task, Event, EmailMessage

1:1
Fully supported

ClickDimensions creates activity records in Dynamics 365 for email engagement, form submissions, and other interactions. These are standard CRM activity objects that migrate cleanly to Microsoft Dynamics 365 Sales using the Dataverse API. Emails map to EmailMessage with linked Task; calls map to Task with TaskSubtype=Call; meetings map to Event with attendee relations; and tasks map to Task with Status, Priority, and ActivityDate preserved.

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

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • ClickDimensions does not store contacts independently

    ClickDimensions is an add-on layer that extends Microsoft Dynamics 365, not a standalone CRM. Contacts, Accounts, Leads, and Opportunities must be migrated from the underlying Dynamics 365 instance, not from ClickDimensions exports alone. We confirm the source Dynamics environment during discovery and pull base CRM records from its Dataverse API or the ClickDimensions export tools that reference the Dynamics schema. Extracting only ClickDimensions records without targeting the source Dynamics instance results in empty or orphaned contact records at the destination.

  • Free Forever plan Custom Field write limit applies during extraction

    ClickDimensions Free Forever plans allow only 60 uses of Custom Field writes per workspace, with each Set Custom Field Value API call counting as one use. During migration extraction, we may exhaust this limit if the source environment has many annotated records. We check the customer's plan tier during scoping and either extract within the limit using batched API calls or fall back to the built-in ClickDimensions Export feature, which does not count against the Custom Field write quota. Migration of custom field values to Microsoft Dynamics 365 Sales has no limit on the destination side.

  • Built-in ClickDimensions export tools are Dynamics-to-Dynamics only

    ClickDimensions provides built-in Export and Import tools within its settings designed specifically for moving Click entities between Dynamics environments. These tools do not support non-Dynamics destinations. For migrations to a new Microsoft Dynamics 365 Sales tenant or org, we use the ClickDimensions API for entity extraction and map the results to the destination's Dataverse schema. The built-in tools serve as a fallback for record count validation rather than as the primary migration path.

  • Dynamics 365 field-level security and validation rules can block import

    Microsoft Dynamics 365 Sales orgs commonly enforce validation rules (required formats, conditional requireds, picklist whitelists) and field-level security that the migration user must explicitly bypass. We coordinate with the customer's Dynamics admin to grant the migration user the necessary Dataverse API permissions and to temporarily adjust validation rules or add a migration-context bypass. Without this coordination, initial import attempts typically show 5-25 percent record rejection, requiring re-run with corrected field values.

  • Campaign and Marketing Activity data maps to non-standard Dynamics objects

    ClickDimensions Email Sends, Event Registrations, and Survey Responses do not map to standard Microsoft Dynamics 365 Sales objects by default. Email sends map to Campaign and CampaignActivity; event registrations map to Campaign Response; survey responses map to Notes or custom fields. We define this mapping during scoping and configure the destination Campaign entity and custom fields before migration begins. Customers expecting marketing activity to appear as standard Opportunity or Contact records should be briefed on the Campaign-based structure during discovery.

Migration approach

Six steps for a successful Click to Microsoft Dynamics 365 Sales data migration

  1. Discovery and source Dynamics environment identification

    We identify the underlying Microsoft Dynamics 365 instance that ClickDimensions extends and audit its schema (Contacts, Accounts, Leads, Opportunities), ClickDimensions-specific entities (Email Sends, Event Registrations, Web Tracking Events, Survey Responses), custom fields, and plan tier. We confirm whether the destination is the same Dynamics 365 tenant (different org) or a different tenant entirely, which determines whether ClickDimensions export tools or the Dataverse API is the primary extraction path. The discovery output is a written migration scope and object inventory.

  2. Source plan check and extraction method selection

    We check the ClickDimensions plan tier. For Free Forever plans, we plan extraction around the 60-use Custom Field write limit, either using batched API calls or the built-in Export feature. For paid plans with full API access, we use the Dataverse API directly with pagination and rate-limit handling. We extract base CRM records (Contacts, Accounts, Leads, Opportunities) from the source Dynamics environment and ClickDimensions entities in parallel streams, maintaining a record-level cross-reference file for relationship resolution.

  3. Destination schema preparation

    We design the destination Microsoft Dynamics 365 Sales schema in a Sandbox environment. This includes provisioning custom fields on Contact, Account, Lead, and Opportunity to receive ClickDimensions annotations (email engagement scores, consent flags, survey responses). We configure the Campaign entity to receive Email Send and Event Registration data, create the required Campaign Response structure, and define custom Activity types or Note records for Web Tracking Events. Validation rules are reviewed and adjusted to allow migration-workspace data without errors.

  4. Sandbox migration and reconciliation

    We run a full migration into a Microsoft Dynamics 365 Sales Sandbox using production-like data volumes. The customer's Dynamics admin reconciles record counts (Contacts in, Accounts in, Leads in, Opportunities in, Campaign records in), spot-checks 20-40 random records against the source environment, and validates the Contact-to-Account lookup chain. Any mapping corrections and schema adjustments happen in Sandbox before production migration begins.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (first, as the root of the hierarchy), Contacts (with AccountId resolved), Leads, Opportunities (with AccountId and OwnerId resolved), Campaigns and Campaign Activities (Email Sends), Campaign Responses (Event Registrations), Web Tracking Activity records, Survey Response data (Notes or custom fields), and Activities (Tasks, Events, EmailMessages via Dataverse API). Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and automation rebuild handoff

    We freeze source writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver a written inventory of every ClickDimensions marketing automation (email sequences, event-based workflows, survey triggers) with recommended Microsoft Dynamics 365 Sales or Power Automate equivalents. We do not rebuild ClickDimensions automations as Power Automate flows inside the migration scope; that is a separate engagement or an internal admin task.

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.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

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 Microsoft Dynamics 365 Sales .

  • 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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during Click to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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

Book a free 30 minute consultation

Straightforward migrations under 10,000 CRM records with no marketing activity history land between three and five weeks. Migrations that include email send history, event registrations, web tracking data, or survey responses (over 50,000 marketing activity records) extend to six to nine weeks because of Dataverse API pagination, field-level transform work, and campaign-response relationship resolution. The timeline also depends on the availability of the source Dynamics environment for extraction and the speed of Sandbox validation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Click.
Land in Microsoft Dynamics 365 Sales , 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