CRM migration

Migrate from Click to Nutshell

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

Click logo

Click

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Click and Nutshell.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from ClickDimensions to Nutshell is a structural migration that requires sourcing data from two places: the underlying Microsoft Dynamics 365 CRM (where ClickDimensions actually stores contacts, accounts, and leads) and the ClickDimensions layer itself (which annotates those records with marketing attributes like email engagement, event registrations, web tracking, and survey responses). Nutshell has no native marketing automation objects, so ClickDimensions marketing activity records migrate as Notes or Tasks with structured metadata rather than as native equivalents. We extract via the Dynamics 365 Web API, map ClickDimensions custom field annotations onto standard Nutshell fields, and load through Nutshell's native import tools or API. Workflows, email sequences, event registrations, and web tracking configurations do not migrate; we deliver a written inventory of these for the customer's admin to evaluate for rebuilding in Nutshell's automation tools or a separate marketing platform.

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

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Click objects map to Nutshell

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

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

Click

Contact (from Dynamics 365)

maps to

Nutshell

Contact

1:1
Fully supported

Contacts reside in the underlying Microsoft Dynamics 365 instance, not in ClickDimensions itself. We extract contacts from Dynamics 365 via the Web API using the customer's Dynamics credentials, then load into Nutshell as Contact records. ClickDimensions custom field annotations (email consent flags, engagement scores) migrate as standard Nutshell contact fields or custom fields depending on the field type. The Dynamics contact ID is preserved in a custom field for reconciliation.

Click

Account (from Dynamics 365)

maps to

Nutshell

Account

1:1
Fully supported

Accounts migrate from Dynamics 365 to Nutshell Account. The Dynamics Organization ID and Account ID are preserved in custom fields for reconciliation. Account-to-Contact relationships are resolved during import by matching the Dynamics parentaccountid reference to the newly created Nutshell Account records.

Click

Lead (from Dynamics 365)

maps to

Nutshell

Lead

1:1
Fully supported

Leads from Dynamics 365 migrate to Nutshell Lead. ClickDimensions lead-scoring attributes stored as custom fields on the Dynamics Lead record migrate to Nutshell custom fields on Lead. Lead status from Dynamics maps to Nutshell's Lead status field.

Click

Opportunity (from Dynamics 365)

maps to

Nutshell

Deal

1:1
Fully supported

Dynamics Opportunities map to Nutshell Deals. The Dynamics pipeline and stage names map to Nutshell pipeline and stage names, which we configure before migration. Closed-Won and Closed-Lost reasons migrate as custom fields on Deal if they exist in Dynamics.

Click

Activity (from Dynamics 365)

maps to

Nutshell

Task

1:1
Fully supported

ClickDimensions creates Task and Event records in Dynamics 365 for email engagement, form submissions, and other interactions. These are standard CRM activity objects that migrate cleanly to Nutshell Task. ActivityDateTime preserves the original timestamp for timeline ordering. Activity type (call, email, meeting, task) maps to Nutshell Task category or a custom field.

Click

Note (from Dynamics 365)

maps to

Nutshell

Note

1:1
Fully supported

Notes attached to contacts, accounts, leads, or deals in Dynamics migrate to Nutshell Note records linked to the corresponding Nutshell record. Rich text formatting is preserved. Note attachments migrate as separate file references if the customer can provide the attachment URLs.

Click

Email Send (ClickDimensions)

maps to

Nutshell

Note

1:many
Fully supported

ClickDimensions Email Send records annotate Dynamics contacts with campaign send history. Since Nutshell has no native email send object, we merge send metadata (campaign name, send date, open count, click count, bounce status) into a structured Note on the corresponding Contact. The Note body contains campaign and engagement summary; individual open and click events are not split into separate records.

Click

Event Registration (ClickDimensions)

maps to

Nutshell

Note

1:many
Fully supported

ClickDimensions Event Registrations store attendee records linked to Dynamics contacts. Registration status, session choices, and custom registration fields migrate as a structured Note on the Nutshell Contact. Multiple event registrations for the same contact merge into a single Events Note with all registration records listed.

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • ClickDimensions does not store contacts or accounts

    ClickDimensions is a marketing automation layer, not a CRM. Contacts, accounts, leads, and opportunities must be migrated from the underlying Microsoft Dynamics 365 instance using Dynamics 365 API credentials. Targeting only ClickDimensions exports during scoping will result in empty records at the destination. We confirm the Dynamics environment details during discovery and extract base CRM records from there before handling ClickDimensions marketing annotations.

  • Marketing activity entities have no native Nutshell equivalent

    ClickDimensions Email Sends, Event Registrations, Web Tracking Events, and Survey Responses do not map to native Nutshell objects because Nutshell has no marketing automation data model. We transform these records into Nutshell Notes with structured metadata (campaign name, engagement counts, registration status) on the related Contact. The customer should decide during scoping whether historical marketing activity data is business-critical enough to justify the transformation scope.

  • Dynamics 365 API access required for extraction

    We extract CRM records from Dynamics 365 using the customer's Dynamics API credentials (app registration in Azure AD with appropriate OAuth2 scopes). If the customer does not have direct API access to their Dynamics environment (for example, if Dynamics is managed by a third-party IT provider or a separate business unit), we require the customer's IT team to provision an app registration or provide read-only API export access before migration begins. Without this, we cannot extract base CRM records.

  • ClickDimensions Free Forever Custom Field write limits

    If the customer's ClickDimensions plan is Free Forever, API writes to Set Custom Field Value are capped at 60 uses per workspace. We check the plan tier during scoping and use the API within the limit or fall back to Dynamics-based extraction of custom field values (which does not count against the ClickDimensions limit) for overflow records. Custom field annotations that exceed the limit are flagged for manual verification post-migration.

Migration approach

Six steps for a successful Click to Nutshell data migration

  1. Discovery and Dynamics access confirmation

    We audit the ClickDimensions layer for active entities (email sends, event registrations, web tracking events, survey responses) and the underlying Dynamics 365 instance for CRM record volumes, custom fields, pipelines, and user count. We confirm the customer's ability to provide Dynamics 365 API access (Azure AD app registration with read scope on Contact, Account, Lead, Opportunity, Task, and Note entities). The discovery output is a written migration scope listing record counts per entity, the ClickDimensions entity types in scope, and the Dynamics access method.

  2. Schema design and pipeline configuration

    We design the Nutshell destination schema: custom fields to receive ClickDimensions annotations (campaign name, event registration status, engagement counts), pipeline and stage names mapped from Dynamics Opportunity, and any lead scoring fields to carry over from Dynamics. We configure Nutshell pipelines and stages before any record import so that Deal stage values land in the correct dropdown on insert.

  3. Sandbox migration and reconciliation

    We run a full migration into a Nutshell trial or sandbox environment using a representative data sample (minimum 500 records per object). The customer reviews record counts, spot-checks field mapping accuracy, and verifies that ClickDimensions annotations appear correctly on Contact Notes. Mapping corrections happen in this phase before production migration begins.

  4. Dynamics 365 CRM extraction and contact-account resolution

    We extract contacts, accounts, leads, and deals from Dynamics 365 via the Web API. Accounts are loaded first (since Contact requires an Account reference). Contacts are loaded with the AccountId lookup resolved by matching Dynamics parentaccountid to the Nutshell Account record created in the previous phase. Leads and Deals follow in dependency order.

  5. ClickDimensions annotation layer import

    We extract Email Send records, Event Registration records, and relevant Survey Response records from ClickDimensions via its API. Each record is linked to a Dynamics contact (identified by email address match), which we resolve to the corresponding Nutshell Contact created in the previous phase. Records are transformed into Note format with structured metadata and inserted against the resolved Contact.

  6. Cutover, delta sync, and handoff

    We freeze writes to the source Dynamics and ClickDimensions environment during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of ClickDimensions entities not migrated (event registration sessions, web tracking behavioral data, survey question-answer detail) with recommendations for rebuilding or replacing in Nutshell or a separate marketing platform.

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.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 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 Nutshell.

  • Object compatibility

    B

    2 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 Nutshell 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 Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 15,000 Contacts and 3,000 Deals where direct Dynamics 365 API access is available. Migrations requiring extraction from a managed Dynamics environment (where IT coordination is needed), large ClickDimensions marketing activity histories (over 200,000 email send or event records), or complex multi-annotation custom field structures move to six to ten weeks because of the extraction coordination and ClickDimensions transformation work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Click.
Land in Nutshell, 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