CRM migration

Migrate from Microsoft Dynamics 365 Sales to Nutshell

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

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Source

Nutshell

Destination

Nutshell logo

Compatibility

78%

7 of 9

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

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Try the reverse

Nutshell
Microsoft Dynamics 365 Sales

Overview

What this migration involves

Moving from Microsoft Dynamics 365 Sales to Nutshell is a structural simplification. Dynamics 365 uses a normalized entity model with separate Account, Contact, Opportunity, Quote, Order, and Invoice objects on the Dataverse Web API; Nutshell collapses most of this into a Company-Person-Deal model where People are embedded in Companies and Deals replace Opportunities. We resolve that entity reframing during scoping, extract via the Dataverse Web API, and load through Nutshell's REST API. We flag territory hierarchies (which have no Nutshell equivalent), commercial document chains (Quotes, Orders, Invoices), and Power Automate workflows as requiring manual rebuild post-migration. The mandatory implementation partner cost that inflates Dynamics 365 for SMB teams is eliminated by switching to Nutshell's self-serve setup, and we migrate the data layer so the admin rebuild is the only remaining work after cutover.

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

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pushing teams away

  • Steep learning curve and complex role hierarchies make user adoption difficult, especially for teams without dedicated IT support
  • Poor implementation partner experiences leave organizations stuck with misconfigured systems and no clear path to remediation
  • Performance degrades noticeably with large datasets and complex customer journeys, particularly in marketing and multi-module environments
  • Integration with non-Microsoft products requires additional configuration or third-party middleware, limiting flexibility
  • Mandatory implementation partner involvement to properly configure the system adds significant upfront cost beyond licensing fees

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 Microsoft Dynamics 365 Sales objects map to Nutshell

Each row shows how a Microsoft Dynamics 365 Sales 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.

Microsoft Dynamics 365 Sales

Account

maps to

Nutshell

Company

1:1
Fully supported

Dynamics Accounts map to Nutshell Companies. The Account Name becomes the Company name, and the primary Address block migrates to the Company address fields. Industry, Annual Revenue, Number of Employees, Website, and any custom fields on Account migrate to corresponding Nutshell Company custom fields. The Account lookup on Dynamics Contact is resolved so that each migrated Person record is nested under the correct Company at migration time.

Microsoft Dynamics 365 Sales

Contact

maps to

Nutshell

Person (within Company)

1:1
Fully supported

Dynamics Contacts map to Nutshell People records embedded within Companies. We resolve the parent Company reference from the Account lookup and nest the Person under the migrated Company at import time. Email, Phone, Title, Department, and Lifecycle Stage fields map to Nutshell Person fields or custom fields. Any Contact ownership in Dynamics maps to the corresponding migrated User in Nutshell.

Microsoft Dynamics 365 Sales

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Dynamics Leads map directly to Nutshell Leads with a 1:1 field mapping. Lead Status, Lead Source, and any scoring fields migrate to Nutshell Lead fields or custom fields. The Lifecycle Stage property from Dynamics (if populated on a Lead) is preserved as a custom text field in Nutshell for audit and segmentation. Dynamics Lead scoring values are flagged as notes for rebuilding in Nutshell's automation layer post-migration.

Microsoft Dynamics 365 Sales

Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

Dynamics Opportunities map to Nutshell Deals. The Opportunity Name becomes the Deal name, Estimated Close Date maps to Nutshell close date, and Amount maps to Deal value. The pipeline stage from Dynamics maps to the Nutshell pipeline stage; we define the stage mapping during scoping so stage names are transliterated rather than copied verbatim. Probability percentage, loss reason, and close date migrate as custom fields in Nutshell since Nutshell Deals do not natively track probability or loss reason as separate fields.

Microsoft Dynamics 365 Sales

Quote, Order, and Invoice

maps to

Nutshell

Deal with Note attachment

lossy
Fully supported

Dynamics Quotes, Orders, and Invoices have no direct Nutshell equivalent. We convert each Quote, Order, and Invoice to a Note attached to the parent Deal and embed the document content as structured text including line items, quantities, unit prices, and totals. The commercial chain relationship (Quote converts to Order, Order invoices out) is preserved as linked Notes rather than separate object records. Customers who need structured quoting after migration should configure Nutshell's built-in quoting feature or evaluate a third-party quoting integration.

Microsoft Dynamics 365 Sales

Activity (Task, Email, Phone Call, Appointment)

maps to

Nutshell

Note

1:1
Fully supported

Dynamics Tasks, Emails, Phone Calls, and Appointments map to Nutshell Notes. We preserve the activity type as a prefix in the Note subject, the original timestamp, the owner, and the full body content. The rich activity timeline that Dynamics provides per record is flattened into a Note in Nutshell, which is the closest structural equivalent. Call disposition, duration, and recording links are embedded in the Note body. We flag this transformation during scoping so the customer understands that the activity timeline will display differently in Nutshell.

Microsoft Dynamics 365 Sales

Annotation (Note)

maps to

Nutshell

Note

1:1
Fully supported

Dynamics Annotations map directly to Nutshell Notes. The annotation body, created-on timestamp, and modified-on timestamp migrate as-is. Attachments stored as SharePoint document locations or Dataverse blob storage are downloaded and reattached to the corresponding Note in Nutshell. SharePoint file paths are converted to Nutshell note attachments in the migration job.

Microsoft Dynamics 365 Sales

Product and Price List

maps to

Nutshell

Product (reference only)

lossy
Fully supported

Dynamics Products and Price Lists have no native Nutshell equivalent object. We create Nutshell Product records as a reference table with the product name and SKU stored in custom fields, and we attach pricing information from the Price List as a Note on the Product record. Customers who need live pricing integration after migration should configure a product catalog within Nutshell or use a third-party CPQ tool. We deliver a product catalog mapping document at migration close.

Microsoft Dynamics 365 Sales

User and Owner

maps to

Nutshell

User

1:1
Fully supported

Dynamics Users map to Nutshell Users by email match. Active Users in Dynamics migrate as active Nutshell Users; inactive Users are flagged for the customer admin to review and either provision or archive in Nutshell. Dynamics Owner-based record assignments map to Nutshell User assignments on Company, Person, Lead, and Deal records. Role-based security, Business Units, and Teams from Dynamics have no Nutshell equivalent and are not migrated; the customer's admin reviews record ownership after migration and reassigns as needed.

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.

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

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

  • Custom fields must be created in Nutshell UI before migration

    Nutshell does not allow creating custom fields via its REST API alone; fields must first be added through the admin UI and published before API writes can populate values. This mirrors the constraint in Dynamics 365 where custom fields require UI creation before API writes. We coordinate with the customer's Nutshell admin during the pre-migration window to create all required custom fields for Companies, People, Leads, and Deals, matching the source field names and data types from Dynamics. Any custom field that is not pre-created will be skipped during import and flagged in the reconciliation report for addition during the staging window.

  • Activity records become Notes, not native activity records

    Dynamics 365 stores Tasks, Emails, Phone Calls, and Appointments as distinct entity types with rich metadata (call duration, disposition, attendee lists, email headers). Nutshell does not have native activity objects of equivalent depth. We migrate activity history as Nutshell Notes with the original timestamp and type encoded in the Note subject, preserving the content and owner but not the timeline structure. Call dispositions, email subjects, and meeting attendee lists are embedded in the Note body. The customer should understand before migration that the activity timeline will display differently in Nutshell.

  • Quotes, Orders, and Invoices have no Nutshell equivalent

    Dynamics 365 maintains a commercial document chain where Quotes convert to Orders and Orders invoice out, each as a related object with line items, product references, and pricing. Nutshell has no native Quote, Order, or Invoice object. We convert each commercial document to a structured Note attached to the parent Deal, preserving line items and totals as text. The sequential conversion relationship is lost. Customers who rely on structured quoting or order management should configure Nutshell's quoting feature or select a third-party CPQ integration after migration.

  • Territory data has no native Nutshell destination

    Territory management is available on Microsoft Dynamics 365 Sales Enterprise tier only, with hierarchical territory structures and assignment rules tied to Accounts and Opportunities. Nutshell has no territory object. We extract territory names from Dynamics Account or Opportunity records and map them to a custom text field on the Nutshell Company or Deal record. Territory-to-rep assignment rules must be rebuilt manually in Nutshell's settings post-migration.

  • Inactive owner records require pre-migration audit

    Dynamics activity records and CRM entities are assigned to Owner IDs that may reference users who are inactive or unlicensed. Nutshell requires a valid active User to own records. We audit all Owner IDs referenced in the source data before migration and map inactive owners to a designated migration admin placeholder in Nutshell. The original owner name is preserved in a custom field on the record for reference and post-migration reassignment. This prevents orphaned records that would otherwise fail Nutshell's validation on insert.

Migration approach

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

  1. Discovery and source audit

    We extract the full Dynamics 365 entity inventory via the Dataverse Web API, pulling Accounts, Contacts, Leads, Opportunities, Activities, Annotations, Products, and any custom tables. We count record volumes per entity, audit the custom field list against the Professional tier's 15-table ceiling if applicable, flag inactive owner IDs, and identify territory data in Account or Opportunity records. The discovery output is a written scoping document with entity counts, custom field inventory, and a flag for any schema simplification required before migration.

  2. Field mapping design and Nutshell custom field creation

    We design the field-level mapping between each Dynamics entity and its Nutshell equivalent. We identify fields that have no Nutshell equivalent (probability, loss reason, territories, commercial document chain) and document the custom field or Note-based replacement strategy for each. We then coordinate with the customer Nutshell admin to create all required custom fields in the Nutshell UI before the migration job runs. Any field that cannot be created in time is flagged and deferred to the post-migration staging window.

  3. Owner and user reconciliation

    We extract all distinct Owner IDs referenced on Accounts, Contacts, Leads, Opportunities, Activities, and Annotations and match them by email against the Nutshell destination account's user list. Any Owner without a matching Nutshell User is held in a reconciliation queue. The customer provisions missing Nutshell Users for active Dynamics users and flags inactive Dynamics users for archive or placeholder assignment in Nutshell. Migration cannot proceed past this step because Nutshell requires a valid owner reference on record insert.

  4. Staged data extraction from Dynamics

    We extract Dynamics data in dependency order using the Dataverse Web API with batched requests and configurable concurrency limits to stay within Power Platform request allocations. For large migrations, we run extraction in off-peak hours and use Dataverse bulk export where available. The extraction produces staged JSON or CSV files per entity, each tagged with the source record ID, created-on and modified-on timestamps, and owner email for reconciliation at the destination.

  5. Migration load into Nutshell

    We load data into Nutshell in record-dependency order: Companies first (as the parent for People), then People nested under Companies, then Leads, Deals with stage mapping applied, Products as reference records, and Notes converted from Dynamics Activities and Annotations. We load through Nutshell's REST API with retry logic and batch chunking. Each phase emits a row-count reconciliation report comparing source record count to destination record count before the next phase begins.

  6. Validation, cutover, and automation inventory delivery

    We validate final record counts in Nutshell, spot-check 30-50 records per entity against the Dynamics source for field-level accuracy, and check for duplicate companies or people created during import. We deliver the full automation inventory document listing every Power Automate flow, business rule, and Dynamics-specific workflow requiring rebuild in Nutshell, with a recommended Nutshell automation approach for each. We do not rebuild Dynamics workflows as Nutshell automations within the migration scope. We support a one-week hypercare window for reconciliation issues raised during the first week of Nutshell production use.

Platform deep dives

Context on both ends of the pair

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Source

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

  • 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

    Microsoft Dynamics 365 Sales : Per-user and per-environment request limits enforced across Power Platform; exact limits vary by license tier and environment capacity.

  • Data volume sensitivity

    A

    Microsoft Dynamics 365 Sales exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales to Nutshell data migrations

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

Can't find your answer?

Walk through your Microsoft Dynamics 365 Sales 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 two and four weeks for environments under 10,000 records with a single pipeline and no custom objects above the 15-table Professional tier ceiling. Environments with multiple pipelines, complex custom field schemas, large activity histories exceeding 100,000 records, or territory hierarchies that require field-based remapping move to six to ten weeks. Discovery and schema design add one to two weeks at the front end regardless of record volume.

Adjacent paths

Related migrations to explore

Ready when you are

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