Migrate from noCRM.io to Nutshell

noCRM Leads do not have a direct single-object equivalent in Nutshell. We split each noCRM Lead into a Nutshell Person record (the primary contact) and a Nutshell Company record (the organization). The noCRM Lead title and contact details map to Person fields; company name from noCRM becomes the Company record. A Nutshell Lead is also created to carry the pipeline step history and deal-stage data. The three-record structure is built in dependency order: Company first, Person second (with Company lookup resolved), Lead third (with Person and Company lookups resolved). This order ensures referential integrity during batch import.

noCRM Pipeline Steps define the stages a Lead moves through. We map each Step to a corresponding Deal Stage in Nutshell. For Starter noCRM accounts with a single Pipeline, we configure a single Nutshell Pipeline with matching stage names. For Expert and Dream accounts with multiple Pipelines, we create multiple Nutshell Pipelines (one per noCRM Pipeline) and map Steps within each. Step-transition history is preserved as a custom multi-select field on the Nutshell Deal capturing the stage sequence.

noCRM Pipelines (available on Expert and Dream) map to Nutshell Pipelines. Each Nutshell Pipeline has a default set of Stages; we replace these with the Step names extracted from noCRM during scoping. Starter accounts are limited to one Pipeline and map to a single Nutshell Pipeline. We validate that step count does not exceed Nutshell's practical stage limit of approximately 15 per pipeline.

noCRM Tags are freeform labels on Leads. We preserve all tags as-is and map them to Nutshell Tags on the Lead record. Tags used for lead scoring or segmentation in noCRM are flagged during scoping so the customer can decide whether to recreate them as Nutshell Lead custom fields or retain them as simple labels.

noCRM Lead activity logs capture comments, status changes, step transitions, and manual entries in reverse-chronological order. We export this history as structured Note records linked to the Nutshell Person or Lead. Status-change entries (Won, Lost, Cancelled) are mapped to Nutshell's lead status values. Step-transition entries are preserved as Note content with a timestamp so the history is queryable post-migration.

noCRM's Admin > Sales process > Predefined Fields vary per account. We extract the field definitions (name, type, options) and map them to Nutshell Lead custom fields. Nutshell supports Text, Long Text, Currency, Date, Number, and Dropdown types for Lead fields. Fields that do not map directly (for example, noCRM fields with unsupported types) are documented in the migration inventory with recommended Nutshell equivalents. Field labels are preserved as field names; descriptions migrate as field help text in Nutshell.

noCRM Prospecting Lists group Leads for outbound campaigns. We export list membership and map it to Nutshell Lists (static lists of People or Leads). If the customer uses Nutshell's campaign tracking, we can map list membership to Campaign Members instead. Some destinations treat Prospecting Lists as segmentation data rather than active campaign audiences; we confirm the intended use during scoping and apply the appropriate target object.

Files attached to noCRM Leads are exported as binary blobs alongside the lead record. We preserve the original filename and attach the file to the corresponding Nutshell Person or Lead record. Nutshell's file attachment limit and supported formats apply; we flag any files that exceed size limits before import. PDF and image attachments are fully supported; files requiring special application context (for example, noCRM Quick Scan images) are preserved with a note linking to the original.