CRM migration
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
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
8 of 10
objects map 1:1 between Click and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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.
Source platform
Click platform overview
Scorecard, SWOT, gotchas, and pricing for Click.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
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 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
Microsoft Dynamics 365 Sales
Contact
1:1Contacts 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
Microsoft Dynamics 365 Sales
Account
1:1Accounts 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
Microsoft Dynamics 365 Sales
Lead
1:1Leads 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
Microsoft Dynamics 365 Sales
Opportunity
1:1Opportunities 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
Microsoft Dynamics 365 Sales
Campaign + CampaignActivity or EmailMessage + Task
1:1ClickDimensions 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
Microsoft Dynamics 365 Sales
Campaign Response
1:1Event 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
Microsoft Dynamics 365 Sales
Custom Activity or Note
lossyClickDimensions 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
Microsoft Dynamics 365 Sales
Note or Custom Fields on Contact
lossySurvey 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)
Microsoft Dynamics 365 Sales
Custom Fields on CRM Records
1:1ClickDimensions 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)
Microsoft Dynamics 365 Sales
Task, Event, EmailMessage
1:1ClickDimensions 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.
| Click | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Account | Account1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Opportunity1:1 | Fully supported | |
| Email Send | Campaign + CampaignActivity or EmailMessage + Task1:1 | Fully supported | |
| Event Registration | Campaign Response1:1 | Fully supported | |
| Web Tracking Event | Custom Activity or Notelossy | Fully supported | |
| Survey Response | Note or Custom Fields on Contactlossy | Fully supported | |
| ClickDimensions Custom Fields (Tasks) | Custom Fields on CRM Records1:1 | Fully supported | |
| Activity (Email, Call, Meeting, Task) | Task, Event, EmailMessage1:1 | 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
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Click
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
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 Microsoft Dynamics 365 Sales .
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 Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Click
Other ways to arrive at Microsoft Dynamics 365 Sales
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.