Migrate from Snapforce CRM to Nutshell

Snapforce Accounts map directly to Nutshell Accounts. Account Name, Industry, Website, Phone, Address fields carry over as typed fields. We use Account Name as the dedupe key during import to prevent duplicates. Nutshell Accounts do not have a separate parent-account hierarchy by default; if the customer uses parent-account structures in Snapforce, we map those to Nutshell's linked Accounts feature or create a custom field for parent account reference.

Snapforce Contacts map to Nutshell People records. Contact Name, Email, Phone, Title, Address, and custom fields carry over. We preserve the Contact-to-Account linkage by resolving the Nutshell Account by name match during import. If a Snapforce Contact has no associated Account, it imports as a standalone Person. Nutshell People is a unified object holding both leads and contacts; there is no separate Lead module in the standard Nutshell data model.

Snapforce Leads map to Nutshell People with the lead-specific fields (Lead Source, Lead Status, Rating) carried into custom fields on the Person record. We map Lead Status values to Nutshell Person status options or store them in a custom field for visibility. If the customer uses Snapforce's Lead Conversion feature, converted Leads that created Accounts and Contacts have already been split in Snapforce; we map the resulting Account-Contact pair normally.

Snapforce Opportunities map to Nutshell Deals. Deal Name, Amount, Close Date, Stage, Owner, and custom fields carry over. We map Snapforce pipeline stages to Nutshell Deal stages and configure the Nutshell pipeline before migration. If Snapforce Opportunities reference Products via line items, we create Nutshell Products and associate them with the Deal as line items during migration.

Snapforce Tasks map to Nutshell Activities. Task Subject, Due Date, Status, Priority, Assigned To, and Description carry over. We resolve the Assigned To owner by email match against the Nutshell user list. Tasks that are completed in Snapforce are set to Done in Nutshell with the completed date preserved. Note-type tasks from Snapforce migrate as Nutshell Activities with the body preserved.

Snapforce VoIP call logs map to Nutshell Activities as completed tasks with the disposition stored in the description or a custom field. Call duration, timestamp, and direction (inbound/outbound) are preserved as task metadata. Call recordings are extracted as audio file attachments, linked to the Person record in Nutshell by filename convention, and noted as a manual re-association step for the customer's admin if Nutshell supports file attachments on Person records in their plan tier.

Snapforce meeting records (from the calendar integration or manual entry) map to Nutshell Activities. Meeting title, date, time, location, and attendees migrate as Activity records with the attendees listed in the description or a custom field if Nutshell supports attendee tracking at the Activity level.

Snapforce custom fields per module are captured during discovery with label and data type. We recreate them in Nutshell on the corresponding object (Account, Person, Deal, Activity) before data import begins. Custom field IDs from Snapforce are not portable; workflow rules referencing Snapforce custom fields do not migrate and are listed in the configuration inventory for manual rebuild in Nutshell.

Snapforce Users are exported with name, email, and role. We match by email against the Nutshell user list. Any Snapforce User without a matching Nutshell account goes to a reconciliation queue for the admin to provision before record import. Inactive Snapforce users who own records are mapped to the admin user during migration with ownership reassigned post-provisioning.

Snapforce Documents linked to Accounts, Contacts, Opportunities, or Leads are exported with the parent record reference. We download documents to local storage, preserve the parent linkage by filename convention (accountname_contactname_docname), and upload them to the corresponding Nutshell record as file attachments where supported by the plan tier. Documents that reference a Google Drive link in Snapforce are flagged for manual re-link in Nutshell.