Migrate from CASH to Nutshell

Source contact records map directly to Nutshell People objects. Nutshell uses a unified People model for both Contacts and Leads, distinguished by a status field. The source contact's email, name, phone, job title, company association, and address fields transfer to corresponding Nutshell People fields. Records without an email address route to Nutshell Leads by default.

Source Lead records map to Nutshell People with Lead status. The source lead status field (e.g., New, Contacted, Qualified) transfers as a custom field on the Nutshell People record. FlitStack preserves the original lead create date and source attribution so that Nutshell's lead reporting reflects the full lead lifecycle from acquisition onward.

Source Company or Account records map to Nutshell Company objects. Nutshell Company fields include name, website (URL), industry, phone, fax, address components (street, city, state, zip, country), number of employees, and annual revenue. Where the source Company name is blank, FlitStack flags the record before migration so you can supply a default or merge with an existing Company.

Source Deal or Opportunity records map to Nutshell Opportunity objects. Nutshell Opportunity fields include name, value (amount), status (stage), close date, and probability percentage. The source pipeline name and stage name combine to establish the Nutshell pipeline context — the pipeline must exist in Nutshell before migration runs or FlitStack creates it with the source names as a temporary configuration.

Source owner_id or assigned_user fields resolve to Nutshell users by email match. FlitStack queries Nutshell's user list during the pre-migration audit and builds an email-to-user-id lookup table. Records whose owner email has no matching Nutshell user are flagged before migration commits — your admin either invites the user to Nutshell first or reassigns those records to a fallback owner.

Source task records map to Nutshell Task objects. Nutshell Task fields include name (subject), description (body), status (open/completed), due date, assigned user, and related record link (Person or Opportunity). Completed status in the source transfers as a closed Nutshell Task; open tasks transfer as open with original due dates preserved.

Source activity records — calls, emails, and meetings — map to Nutshell Activity objects. Each activity type from the source becomes a separate Activity record in Nutshell. The source activity type (Call, Email, Meeting) is preserved in a custom field on the Nutshell Activity so that filtering by activity type works correctly in Nutshell's Activity feed after migration.

Source note records map to Nutshell Note text. Nutshell stores notes as free-form text attached to People, Companies, or Opportunities. The original note title maps to the Nutshell Note name; the note body maps to the description. Note creation timestamps transfer as custom datetime fields to preserve the original audit trail for compliance and reporting continuity.

Source file attachments associated with People, Companies, or Opportunities transfer to Nutshell's attachment storage. Files are re-uploaded to Nutshell with their original filenames and file types preserved. Nutshell's file size limits apply — files exceeding Nutshell's size threshold are flagged before migration so you can decide whether to split the attachment or store it externally with a link in the Nutshell record.

Source custom objects and custom fields evaluate for Nutshell compatibility during the pre-migration audit. Standard source objects (Contacts, Companies, Deals, Activities) transfer as their Nutshell equivalents with custom fields appended. Non-standard custom objects either map to Nutshell custom fields on existing objects or become Nutshell custom object types if the source schema complexity is manageable — this is determined during the sample migration review.