Migrate from Nutshell to Microsoft Dynamics 365 Sales

Discovery and schema baseline

We audit the source Nutshell account across plan tier, People count, Company count, Lead count, Activity volume per object, custom field definitions per object, pipeline definitions (stage names, order, probabilities), active tag taxonomy, and active email sequences. We also document the Nutshell-to-Dynamics 365 edition fit: Sales Professional ($65/user) covers single-pipeline migrations without complex custom objects; Enterprise ($105/user) is needed for multi-pipeline Record Type management, advanced territory forecasting, or integration with Finance or Supply Chain modules. The discovery output is a written migration scope, a data volume estimate, and a Dynamics 365 edition recommendation.

Destination schema design and pre-configuration

We design the Dynamics 365 schema before any data extraction. This includes provisioning custom fields (mapped from Nutshell custom field definitions), creating Option Sets for picklist fields, pre-configuring Account and Contact field-level security, designing the Record Type and Sales Process structure for Opportunity based on the Nutshell pipeline inventory, and creating the Activity timeline configuration. Dynamics 365 schema is deployed to a Sandbox environment first for validation against real Nutshell sample data. Account-Contact relationship rules are established at this stage to prevent orphaned Contact imports.

Paginated extraction from Nutshell JSON-RPC API

We extract Nutshell data using cursor-based pagination with configurable batch sizes. People and their associated Company references are extracted together in a joined pass to build the relationship graph. Leads, Activities, Tags, and custom field data are extracted in parallel passes. We implement retry logic with exponential backoff on rate-limit responses (HTTP 429). Extraction produces a staging dataset organized by object with source IDs preserved for reconciliation. The extraction phase typically runs over one to three days depending on total record volume.

Sandbox migration and reconciliation

We run a full migration into the Dynamics 365 Sandbox environment using production-like data volumes from the Nutshell staging dataset. The customer's RevOps lead reconciles record counts (Accounts in, Contacts in, Leads in, Activities in), spot-checks 20-40 records against the Nutshell source for field accuracy, and validates that the Account-Contact relationship graph resolved correctly with no orphaned Contacts. Any mapping corrections, missing custom fields, or schema gaps are fixed in Sandbox before production migration begins.

Owner reconciliation and User provisioning

We extract every distinct Nutshell User referenced on People, Company, Lead, and Activity records and match by email against the Dynamics 365 destination org's User table. Any Nutshell User without a matching Dynamics 365 User goes to a reconciliation queue. The customer's Dynamics 365 admin provisions missing Users and assigns them the appropriate Security Roles before production migration begins. OwnerId references on Opportunities and Activities require a valid systemuserid, so this step is a hard prerequisite for the production phase.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Nutshell Companies), Contacts (with AccountId resolved from the People-Company relationship graph), Leads, Opportunities (with Record Type, Sales Process, StageName, AccountId, and OwnerId resolved from Nutshell Pipeline data), Activities (Tasks, Events, EmailMessages via Dataverse batch API), and Tags (as multi-select picklist or Topics). Each phase emits a row-count reconciliation report before the next phase begins. The Nutshell source account remains live during migration so that no new records are created during the cutover window.

Cutover, validation, and automation rebuild handoff

We freeze writes to Nutshell during cutover, run a final delta migration of any records modified during the migration window, then switch the system of record to Microsoft Dynamics 365 Sales . We deliver the automation inventory document listing all Nutshell sequences and workflows with trigger conditions and recommended Power Automate or Sales Cadence equivalents. We support a one-week hypercare window for reconciliation issues. We do not rebuild Nutshell sequences or workflows as Power Automate flows inside the migration scope; that is a separate engagement.