Migrate from eSalesTrack to Nutshell

eSalesTrack Lead records map directly to Nutshell Lead. Lead source, status, and any custom properties migrate to corresponding Nutshell Lead fields or pre-created custom fields. Owner assignment resolves by email lookup against Nutshell Users. If a HubSpot-equivalent lifecycle model is in use on eSalesTrack, the original stage is preserved in a custom field for reporting continuity.

eSalesTrack Contact maps to Nutshell Person. The email address on Contact becomes the primary key for deduplication during import. Phone, title, address, and custom fields migrate to matching Nutshell Person fields. If eSalesTrack Contacts are associated with Accounts, we resolve the AccountId reference after the Companies phase completes so that the Person-to-Company relationship is established at insert time.

eSalesTrack Account records map to Nutshell Company. Company name becomes the dedupe key; domain or website from eSalesTrack becomes the Company URL in Nutshell. If eSalesTrack uses a parent-child account hierarchy, we preserve the relationship in a custom Company field (parent_company__c) and resolve parent references after the initial Company import completes.

eSalesTrack Opportunity maps to Nutshell Deal. The Opportunity name, amount, close date, stage, and owner migrate to the corresponding Nutshell Deal fields. Stage mapping is configured during scoping: each eSalesTrack stage value is assigned to a matching Nutshell stage within the selected pipeline. Closed-won and closed-lost reasons from eSalesTrack custom fields migrate to Nutshell Deal custom fields for loss analysis.

eSalesTrack pipeline stages map to Nutshell Deal stages within a designated Nutshell pipeline. If the customer uses multiple eSalesTrack pipelines or pipeline configurations, we create a corresponding number of Nutshell pipelines (up to 5 on Nutshell Pro) and assign the appropriate Record Type and pipeline to each Deal during import. Stage probability percentages are set per Nutshell stage configuration.

eSalesTrack owners referenced on Lead, Contact, Account, and Opportunity resolve by email match against Nutshell Users. Any eSalesTrack owner without a matching Nutshell User is flagged in a reconciliation queue for the customer's admin to provision before record import. Owner must be resolved before Deals and Leads are imported because OwnerId is a required reference on both objects.

eSalesTrack call records (if stored as a standalone object or within notes) map to Nutshell Activity with activity type set to call. Call duration, disposition, and date migrate to the corresponding Nutshell Activity fields. The Activity is linked to the parent Person, Company, or Deal record by resolving the original contact or account reference at migration time.

eSalesTrack Notes attached to Leads, Contacts, Accounts, or Opportunities map to Nutshell Activity records of type note. The note body migrates as plain text; any rich formatting is preserved where the target Nutshell Activity field supports it. Activities are linked to the parent record by reference resolution at import time.

eSalesTrack custom properties on Lead, Contact, Account, and Opportunity are created as custom fields in Nutshell before any data is imported. Field types are mapped: text properties become Nutshell text fields, numeric properties become number fields, date properties become date fields, and multi-select or tag properties become Nutshell text fields with comma-separated values or separate custom fields per unique value. The customer's admin confirms field creation and naming in a Nutshell sandbox or trial environment before production import.