Migrate from m-savvy to Nutshell

M-savvy Contact records map directly to Nutshell Person records. The Person's email field serves as the primary dedupe key during import. Standard fields (name, email, phone, address) migrate directly; lifecycle stage properties from m-savvy become custom Person fields or tags in Nutshell. The original m-savvy contact owner is resolved to the corresponding Nutshell Person if the owner is also a CRM user, otherwise the record is assigned to the migrating team member for reassignment post-import.

M-savvy Account records map to Nutshell Company records. The Account-Contact relationship is preserved by linking each Person to its parent Company during import using Company as the parent record inserted before Person. Industry, size, billing address, and website fields migrate directly. Companies with no linked Contacts in m-savvy import as standalone Company records.

M-savvy Deals map to Nutshell Deals with stage, amount, close date, and probability preserved. The m-savvy dealstage property maps to Nutshell's stage field; we flag any custom stage names that differ from Nutshell's default stage values and document the mapping. Each Deal is linked to its parent Company and Person at migration time using resolved IDs. Closed-won and closed-lost reasons migrate as custom fields if present in m-savvy.

M-savvy does not separate Leads from Contacts as distinct objects; leads are Contacts with specific lifecycle-stage property values. We extract all Contacts where the lifecycle stage indicates an unqualified or in-progress prospect status and import them as Nutshell Persons with a custom field ms_original_lifecycle__c preserving the original value. M-savvy's lead source property migrates to a custom Person field or tag.

M-savvy pipeline definitions and custom stage names are read from the m-savvy schema during discovery. We map each m-savvy stage to the closest Nutshell Deal stage value, flagging any stages that cannot map directly to a Nutshell default. If m-savvy has more stages than Nutshell's configured pipeline supports, we consolidate adjacent stages and document the grouping. The customer confirms the stage mapping before production migration begins.

M-savvy Activities (emails, calls, tasks, meetings) linked to Contacts or Deals migrate as People Activities in Nutshell. Each activity is linked to the corresponding Person by resolved ID and carries the original timestamp for timeline ordering. M-savvy's activity type maps to the activity kind in Nutshell (email, call, task, meeting). Activity metadata (duration, disposition, recording URL for calls; location for meetings) migrates to custom activity fields.

M-savvy does not publish a public schema reference for custom objects. During discovery we inspect the live org via API to enumerate each custom object type, its fields, and its relationships to standard objects. Each discovered custom object is then configured in Nutshell as a custom record type linked to Person or Company, and the field-level map is shared with the customer for confirmation before migration. Custom object data migrates after all standard objects to ensure parent-record lookups are satisfied.

Attachment files stored in m-savvy are not embedded in record exports; they require a separate file-export pass using m-savvy's file storage endpoints. We download files to our staging environment, re-upload to Nutshell, and relink each file to its parent Person or Deal record by resolved ID. Files whose parent record failed to migrate are flagged and held in a manual review queue. File metadata (filename, size, upload date) is preserved on the Nutshell file record.