Migrate from Dynamics 365 Marketing to Nutshell

Dynamics 365 Marketing Contact records map to Nutshell People. Where the source Contact has a related Lead, we evaluate the Lead's lifecycle stage and merge into a single People record in Nutshell with a custom field retaining the original lifecycle stage value from Dataverse. The primary email address becomes the dedupe key during import. The Contact-to-Account lookup resolves to the Account mapping described below before the People import begins.

Dynamics Lead records that have not been qualified into Contacts merge into Nutshell People. We preserve the leadscore, lead status, and source attribution fields as custom fields on the People record. Active Leads and Contacts are processed together in a single pass using the lifecycle stage evaluation logic to avoid creating duplicate People records for the same individual.

Dynamics 365 Marketing Accounts map to Nutshell Companies. The primary address, industry, website, and any custom account fields migrate as Company fields. The Account is created before any People import so that the Account-to-People relationship is satisfied at the moment of People insert.

Dynamics Opportunities map to Nutshell Deals. Pipeline stage maps from the Dynamics stage name to the Nutshell pipeline stage. Estimated close date, deal amount, probability, and owner assignment migrate directly. The opportunity-to-People and opportunity-to-Company lookups resolve via the People and Company import passes completed earlier.

Dynamics Task records (ActivityPointer with Task type) map to Nutshell Activity entries on the relevant People or Deal timeline. Subject, description, due date, priority, and owner assignment transfer. The regarding object lookup (WhoId, WhatId) resolves to the migrated People or Deal record using the ID mapping table built during the People and Deal passes.

Dynamics PhoneCall records (ActivityPointer with PhoneCall type) map to Nutshell Activity entries with the call disposition and duration preserved in custom fields. The Activity timestamp preserves the original Dynamics call date and time. Resolved WhoId and WhatId references connect the activity to the migrated People or Deal record.

Dynamics Appointment records map to Nutshell Activity entries with start time, end time, and location preserved. Attendee information migrates as custom fields on the Activity record because Nutshell does not have a separate EventRelation equivalent. The original Dynamics timestamp is retained as the Activity date.

Dynamics Annotations with file attachments export as individual records. We map each Annotation to a Nutshell Attachment linked to the parent People or Deal record via the objectid and objecttypecode from Dataverse. The attachment content and the note body migrate as separate entries: note body as Activity content and the file as a linked Attachment.

Dynamics Users referenced as record owners are mapped to Nutshell Users by email match. We extract the complete owner list from Dataverse during discovery and the customer's Nutshell admin provisions the corresponding users before production migration begins. Owner resolution is a prerequisite for the Deal and Activity passes because OwnerId is a required reference on those object types.

Custom fields defined in the Dataverse solution schema migrate to Nutshell custom fields on the corresponding People, Company, or Deal object. The customer must confirm which custom fields are available on their Nutshell plan (Enterprise tier required for custom fields on some objects). We require the managed solution ZIP or Configuration Migration Tool schema export to capture field type, required status, and picklist values before creating the Nutshell field definitions.