Migrate from Dynamics 365 Field Service to Nutshell

Direct map. Dynamics Accounts map to Nutshell Companies. Account.Name becomes Company.name. The primary address (address1_line1, city, state, postal code, country) maps to the standard Nutshell Company address fields. Any secondary addresses are recorded as Nutshell Notes tagged with address type (e.g., 'Billing', 'Shipping') for reference. This preserves the full address hierarchy while keeping the Company record clean.

Direct map. Dynamics Contacts become Nutshell People. All standard person fields (name, email, phone, title, address) map directly. The Contact's primary AccountId resolves to a Company lookup in Nutshell — if the Account is not yet migrated, the Contact is held in a staging queue until the Account is confirmed.

Direct map with a value-mapping note. Dynamics Lead.statuscode and statecode map to Nutshell's Lead status pick-list (New, Working, Dead, Won). Dynamics lead-quality scores or grading fields become a custom Number field on Nutshell Leads. Dynamics Lead.industry maps to a custom pick-list if that data is tracked.

Direct map. Dynamics Opportunities map to Nutshell Deals. opportunity.amount becomes deal.value, close date maps to the Deal close date, and OwnerId resolves by email to the Nutshell User. The Dynamics salesstage (statecode/statuscode) maps to Nutshell's pipeline stage pick-list per pipeline.

Direct map. Dynamics Product records (name, productnumber, defaultuomscheduleid, quantitydecimal, standardprice) map to Nutshell Products. Pricing_unit maps to Nutshell's unit field. Bundle and Option products from Dynamics expand into flat product entries in Nutshell — the bundle relationship is preserved in a custom text field on the Nutshell Product.

Work Orders have no direct Nutshell equivalent. We create a Nutshell Deal per Work Order and add custom fields: Work_Order_ID__c (Dynamics ID for traceability), Incident_Type__c, Service_Territory__c, Priority__c, and Actual_Duration__c. The Deal name derives from the Work Order subject or the related Account + incident reference. This preserves Work Order data in a Nutshell-native format without forcing it into a non-contextual Notes field.

Dynamics Resources (technicians, crews, facilities) map to Nutshell People with a custom Resource_Type__c field set to 'Bookable Resource'. Resource traits, skills, and organizational unit are captured as custom multi-select or text fields on the Person record. Resource-specific constraints (like start/end locations) cannot map to Nutshell's simpler schema and are exported as a reference CSV for the customer's FSM tooling decision.

Work Order Incidents (the line-item problems being resolved) map to Notes attached to the corresponding Nutshell Deal. Each incident's description, product, and service task lines are concatenated into a Note with a prefix tag '[Work Order Incident]' so the original data is searchable post-migration.

Direct map across activity types. Dynamics Tasks, Emails, Phone Calls, and Appointments map to Nutshell Activities with original timestamps, owners, and subject lines preserved. The activity's regardingobjectid resolves to the mapped Nutshell record (Company, Person, or Deal). Email body content maps to the Nutshell Activity description field.

Any Dynamics custom attribute on Account, Contact, Lead, Opportunity, or Work Order that has no direct Nutshell equivalent is created as a Nutshell custom field on the target entity. We create the field before the migration run, preserving data type (text, number, date, dropdown). Pick-list values from Dynamics map as options in the Nutshell custom field.

Direct map. Dynamics Competitor entity maps 1:1 to Nutshell Competitors, transferring name, website URL, and description fields. Additional attributes such as primary contact or address stored on the Dynamics record become custom fields on the Nutshell Competitor. When a Dynamics Opportunity references a Competitor, the relationship is recreated as a Competitor association on the corresponding Nutshell Deal, preserving competitive context for the sales pipeline.

Dynamics territory and coverage templates have no Nutshell equivalent, so territory information is saved as tags on the related Account/Company record. Each territory name becomes a Nutshell Tag, and the associated region and priority are stored in a CSV export. The export includes fields such as territory ID, region, service area, and scheduling constraints, giving the customer's FSM rebuild team a reference for configuring territories in their new scheduling system.