Migrate from Nimble CRM to Nutshell

Nimble People map to Nutshell Person records. Every Nimble Person field (name, email, phone, address, social profiles) maps to the corresponding Nutshell Person field. The Nimble first_name and last_name split is preserved; unparseable names are stored as full_name in Nutshell. Social URLs (LinkedIn, Twitter, Facebook) stored in Nimble custom fields map to Nutshell Person social_url fields if configured, or are stored as custom text fields if Nutshell's social URL fields are not available in the customer's plan.

Nimble Company records map to Nutshell Organization records. We export Companies from Nimble first and import them as Organizations in Nutshell before any Person import so that the Organization lookup relationship is satisfied at Person import time. The Nimble company name becomes the Nutshell Organization name field. Company domain, industry, size, and address fields map to their Nutshell equivalents. We resolve the Company-to-Organization relationship by exact name match and flag any Nimble Person with no matching Company for manual Organization assignment.

Nimble Deals map to Nutshell Lead records. The deal name becomes the Lead name, deal value maps to the monetary value field, and the Nimble pipeline stage (e.g., Appointment Scheduled, Contract Sent, Closed Won) maps to the Nutshell Lead status field. Deal owner from Nimble maps to the Nutshell assigned_to user by email match. Lost and won reasons from Nimble custom fields are stored as custom text fields in Nutshell Lead for audit purposes.

Nimble custom data fields on People export as CSV columns. We map each to a corresponding Nutshell custom Person field, matching the field type (text, picklist, date, boolean, number). Picklist values in Nimble must be whitelisted in Nutshell before import or the values are rejected. We flag any Nimble field type that Nutshell does not support (e.g., multi-select text) and discuss truncation or transformation options during scoping.

Nimble custom fields on Companies export as CSV columns and map to Nutshell Organization custom fields. Organization custom fields in Nutshell are plan-dependent; Starter plans may have fewer custom field slots. We verify the destination plan's custom field limits during scoping and configure fields via Nutshell's field management UI before import begins.

Nimble Tasks export via CSV with a hard ceiling of 500 records per email-delivered file. Large task histories require multiple CSV export batches that we reassemble, deduplicate, and sort by date before loading into Nutshell. Task subject, due date, completion status, and assignment map to Nutshell Activity fields. We cannot extract Tasks via Nimble's API because the platform lacks Task CRUD endpoints.

Nimble logged calls map to Nutshell Activity records with type = Call. Call duration, disposition, and timestamp migrate as custom fields on the Activity record if Nutshell's plan supports custom activity fields. We link each call Activity to the correct Person or Lead record using the Nutshell API with parent-record resolution.

Nimble Events (meetings, appointments) map to Nutshell Activity records with type = Meeting. Start and end time, location, and attendees migrate from Nimble to Nutshell. We link the meeting Activity to the associated Person, Organization, or Lead record.

Nimble Tags are flat label associations on People and Companies. We export all tags per record and map them to Nutshell Tag records, which are then linked via Nutshell's tag association model. Multi-value tag strings in Nimble are split into individual tag assignments in Nutshell. Tags that do not exist in Nutshell are created during the import phase.

Nimble Segments are saved dynamic filters, not standalone exportable objects. We export the constituent People records that match each segment and create Nutshell List records containing those People. The segment filter criteria are documented as a written artifact so the customer can reproduce the dynamic filter as a Nutshell List if the underlying contact set changes.

Nimble Workflow definitions have no export path via API or CSV. We do not migrate Workflows automatically. During scoping, we conduct a Workflow audit: we document each Nimble Workflow's trigger conditions, action sequences, and Kanban stage assignments and deliver a written playbook mapping each to Nutshell Automation Rules. The customer's admin rebuilds automations in Nutshell post-migration using the playbook.

Nimble Outreach Sequences and email templates have no export mechanism. We document the sequence structure (steps, delays, templates used, recipient criteria) as a written artifact during discovery. The customer rebuilds sequences in Nutshell using its built-in email sequence feature. We do not migrate sequences as live automation.