Migrate from CRM Service to Nutshell

CRM Service Account records map to Nutshell Company records. The Account Name maps to Company name, Industry maps to Industry, AnnualRevenue maps to a custom number field, and Website maps to Website. Account Site maps to a custom field if the customer uses multi-location data. We use the Account external ID as a reference key and set the dedupe strategy to match on Company name plus domain where available.

CRM Service Contact records map to Nutshell People records. FirstName, LastName, Email, Phone, and Title transfer directly. Contact Department maps to Department if the target Nutshell plan supports custom fields; otherwise it is mapped to a custom People field. The Contact-to-Account lookup resolves to a Company reference in Nutshell at migration time using the matched Account name or external ID. Salesforce Contact external IDs are preserved as a custom People field for relationship reconstruction if the migration requires a second pass.

CRM Service Opportunity records map to Nutshell Deal records. Opportunity fields transfer as follows: Name maps to Deal name, Amount maps to Value, CloseDate maps to Close Date, StageName maps to the Deal stage in the matching pipeline, Probability maps to a custom probability field, and Description maps to Notes. OwnerId resolves to a Nutshell User by email lookup. Salesforce Opportunity external IDs are preserved on the Deal record for reconciliation.

CRM Service Lead records map directly to Nutshell Lead records. Lead Status, Lead Source, Industry, NumberOfEmployees, and AnnualRevenue transfer directly. The Salesforce Lead external ID is preserved on the Nutshell Lead record. If the customer prefers to merge Leads into People records rather than maintaining a separate Lead queue, we apply that rule during the transform phase based on a status threshold agreed during scoping.

CRM Service Campaign records do not have a direct Nutshell equivalent. Campaign membership data (CampaignName, MemberStatus, HasResponded) exports as a tag value set on the associated CRM Service Contact records. We then apply those tag values as Nutshell People tags during import, preserving the campaign association at the individual record level. If the customer requires campaign-level reporting, we recommend recreating campaigns in Nutshell manually after migration.

CRM Service sales processes and Opportunity stage sets map to Nutshell Deal Pipelines. Each CRM Service pipeline becomes a Nutshell pipeline, and each stage within the pipeline becomes a Nutshell stage with the matching name and probability. Stage order and probability percentages transfer as configured in the destination pipeline. We do not import pipeline automation triggers; these are rebuilt in Nutshell's automation rules by the admin post-migration.

CRM Service Task and Event records migrate to Nutshell activity entries linked to the parent People or Deal record. Call disposition and duration transfer to custom activity fields. Email subject and body transfer as activity notes. Meeting start and end time, location, and attendee list transfer to the corresponding Nutshell activity fields. We resolve the CRM Service WhoId (Contact or Lead) to a Nutshell People or Lead record by email match before insert. Completed activities migrate; open activities are excluded by default and flagged for the customer's admin to handle manually.

CRM Service Attachments and ContentDocument files export to a staging location by download URL, then upload to Nutshell as file attachments on the parent record (People, Company, or Deal) via the Nutshell API. The file name and any associated description preserve. We handle this as a post-Contacts and post-Deals phase so that the parent record exists before the file is linked. Salesforce ContentDocumentLink relationships are resolved by matching the LinkedEntityId to the migrated Contact or Account record.

CRM Service User records map to Nutshell User records by email address match. Active CRM Service users provision as active Nutshell Users; inactive users are held in a reconciliation queue for the customer's admin to decide whether to archive or exclude. Salesforce role hierarchy maps to a flat team structure in Nutshell, as Nutshell does not enforce a role hierarchy in the same way.