Migrate from Zendesk Sell to Nutshell

Sell Leads migrate to Nutshell People with a status value set to unqualified or new. The Sell lead_source property maps to a Nutshell custom text field, and any unqualified_reason field maps to a custom picklist on the Person record. Custom Lead fields resolve via the field-key lookup (not numeric ID) and create equivalent Nutshell custom fields on Person before migration begins. The lead-to-contact conversion logic that Sell performs internally does not apply in Nutshell because People serve as both.

Sell Contacts map to Nutshell People with standard fields (name, email, phone, address) preserved directly. Custom Contact fields migrate to Nutshell Person custom fields using the same field-key resolution process. Owner assignment resolves via email match against Nutshell Users during migration. Duplicate detection settings are noted and applied at import time to reduce redundant Person records.

Sell Companies map to Nutshell Organizations. The Company name becomes the Organization name, domain and website fields map directly, and any custom Company fields create equivalent Nutshell Organization custom fields. Organization is created before any Person import so that the Organization lookup on Person is satisfied at insert time.

Sell Deals map to Nutshell Deals with the deal name, amount, expected close date, loss reason, and custom Deal fields preserved. The Sell dealstage property maps to a Nutshell Stage within the configured pipeline. Owner assignment migrates by email match against Nutshell Users. If the Sell Deal has an associated primary Contact, we link it to the Nutshell Person lookup on the Deal record.

Sell Pipelines (custom workflow containers) map to Nutshell Pipeline configurations. If the source account uses a single Sell Pipeline, it maps to the default Nutshell pipeline directly. If multiple Sell Pipelines exist, we consolidate them into Nutshell's single-pipeline model by mapping each Sell Pipeline to an ordered set of Stages, preserving the ordinal position of every Stage. The customer chooses the consolidation strategy during scoping.

Sell Stages (children of Pipelines) map to Nutshell Stages within the target Pipeline. Stage ordinal position and loss/win flags are preserved. Loss reason values from Sell Deals migrate as a custom picklist on the Nutshell Deal record. Stage probability percentages are recorded in a custom field for reference if the customer wants to configure probability-aware forecasting in Nutshell.

Sell Tasks migrate to Nutshell Tasks with due date, assignee (resolved by email match), completion status, and priority preserved. Notes attached to Tasks are handled as child records inserted after the Task itself is created so that the parent reference is satisfied.

Sell Notes attached to Contacts, Deals, Leads, or Companies migrate to Nutshell Notes with their parent reference intact. The Note body (rich text) migrates as-is. Notes serve as the primary conversation-history carrier in Nutshell's activity timeline.

Sell Users (sales reps, admins) export with email, name, and role. We match by email against Nutshell Users. Any Sell User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before the main record migration begins. Role and territory assignments are documented for reconfiguration in Nutshell settings.

Sell Tags applied to Contacts, Deals, and Leads migrate as-is to Nutshell Tags. Tags are preserved for segmentation and filtering. Note that Nutshell's tag-based filtering behaves similarly to Sell's tagging model but the admin should review any tag-dependent reports post-migration.

Sell custom fields on Leads, Contacts, Deals, and Companies require field-key resolution (not numeric ID) during scoping. We create equivalent Nutshell custom fields on the corresponding object before any record migration begins and maintain a field-key-to-Nutshell-field-ID lookup table throughout the project. Custom field types (text, number, date, picklist, checkbox) are type-matched to Nutshell's supported custom field types.