Migrate from Simplicity Enterprise CRM to Nutshell

Simplicity Contact records map directly to Nutshell Contact. Standard fields (name, email, phone, address) migrate 1:1. Any Simplicity custom fields on Contact require explicit mapping to Nutshell custom fields or standard fields during the schema discovery phase, which we perform before any export begins. Simplicity contact records that have been merged via the Single Customer View feature preserve a canonical contact ID that we carry forward as a custom field for audit purposes.

Simplicity Company records map to Nutshell Company. Company name, domain, address, and phone fields migrate 1:1. The relationship between Contact and Company in Simplicity maps to the Nutshell linked-company reference on Contact. We create Companies first in the migration sequence so that CompanyId is resolved before Contact import begins, preventing orphaning.

Simplicity Deal records map to Nutshell Deal. Deal name, value, stage, owner, and associated Company or Contact links migrate directly. Stage names require explicit value mapping because Simplicity stage conventions are configurable per client instance and Nutshell uses its own stage set that the customer configures before migration. Closed-won and closed-lost reasons from Simplicity custom fields map to Nutshell custom fields for loss and win analysis.

Simplicity emails stored as Activity records linked to Contact and Company parents map to Nutshell Note records with an activity-style timestamp. We traverse the linked activity table explicitly during export because a naive contact export does not include activity history. Parent-child relationships are resolved at migration time to avoid orphaning emails from their Contact record.

Simplicity call records (Activity with activity type indicating call) map to Nutshell Activity with type set to Call. Call duration, disposition, and outcome stored in Simplicity custom fields migrate to Nutshell custom fields on the Activity record. We preserve the original activity timestamp to maintain the call timeline in Nutshell.

Simplicity meeting records map to Nutshell Activity with type set to Meeting. Location, scheduled time, and attendee list from Simplicity migrate to Nutshell Activity fields. Attendee associations in Simplicity map to Nutshell's linked-contact references on the Activity.

Simplicity notes stored as Activity records with type NOTE map to Nutshell Note records. The note body and creation timestamp migrate directly. We attach notes to their parent Contact or Company record using Nutshell's entity reference system.

Simplicity campaign response tracking stores which contacts responded to which campaign through which channel. Nutshell has no native campaign-response object equivalent. We map campaign responses to tagged activities in Nutshell, using a custom field campaign_name__c and activity_type response to preserve which campaign and channel drove each contact interaction. The customer receives a written campaign-response inventory for evaluation against Nutshell's reporting capabilities.

Simplicity Loyalty module stores reward tiers, point balances, and program membership as distinct relational records linked to Contact. Nutshell has no native loyalty module. We map loyalty data as a JSON archive attached to the Contact record or as structured custom fields on Contact (loyalty_tier__c, points_balance__c, program_name__c) depending on data volume and the customer's reporting needs. This is a data-preservation approach rather than a functional equivalent.

Simplicity integrates social follower data and interaction records linked to Contact. Nutshell does not natively store social media data. We archive social follower counts, account links, and interaction summaries as Note records attached to the Contact or as custom fields on Contact, preserving the data without creating a structural mismatch in the Nutshell CRM.

Simplicity pipeline stages are configurable per client instance. Nutshell uses a pipeline model with configurable stages per deal. We map Simplicity stage order and status logic to Nutshell stages during the schema discovery phase, creating a stage translation matrix that the customer validates before migration. Any Simplicity stage not represented in Nutshell's model is added as a custom stage.

Simplicity's configurable data structure means nearly every object carries client-defined custom fields. We enumerate every active custom field during schema discovery, map each to a corresponding Nutshell custom field or standard field, and flag any Simplicity custom fields that have no Nutshell equivalent. The customer receives a complete field mapping spreadsheet before migration begins.