Migrate from Lime CRM to Nutshell

Lime CRM Company records (sometimes called Account in some industry variants) map directly to Nutshell Company. The company name, address fields, industry, and website transfer as standard fields. We use company name as the deduplication key during Nutshell import and flag any duplicate matches for the customer's admin to resolve before final insert. Company-to-Contact relationships are preserved by inserting Company records first so that the relationship is satisfied at Contact import time.

Lime CRM Person records (the primary individual record) map to Nutshell Person. Name, email, phone, and custom properties transfer directly. We normalise phone number formats during transformation to prevent leading-zero stripping that commonly occurs during CSV processing. Any Lime CRM Person without a linked company is imported as a standalone Person; the customer's admin assigns the Company relationship in Nutshell post-migration.

Lime CRM Deal records map to Nutshell Deal with deal value, stage, owner, and expected close date preserved. Lime CRM allows custom deal pipelines and stages per industry variant; we map source stages to Nutshell pipeline stages during scoping. The deal owner resolves via email match against Nutshell User records, and any unresolved owner references are held in a reconciliation queue.

Each Lime CRM deal stage becomes a Nutshell pipeline stage. Stage names, probabilities, and ordering transfer as the Nutshell pipeline configuration. We configure the pipeline in Nutshell before Deal import begins so that stage values are whitelisted and accepted during insert rather than rejected as invalid enum values.

Lime CRM Activities (calls, meetings, tasks) attach to a Contact or Deal. We export these as chronological Activity records and reconstruct the parent-child relationship in Nutshell using the original Lime CRM record ID stored as a reference field during import. Activity timestamps preserve for accurate timeline ordering in Nutshell.

Lime CRM does not export email conversations as threaded objects. Each ConversationMessage is a separate file attachment in the export. We detect this at scoping, reassemble threads by conversation ID and timestamp, and inject them into Nutshell as a unified Activity record with the full conversation body so the migration does not arrive as hundreds of disconnected message files. The parent Contact or Deal reference is preserved from the original Lime CRM linking.

Lime CRM Ticket records migrate to Nutshell as either Lead or Case depending on the customer's use case. Tickets that represent pre-sale support inquiries map to Nutshell Lead; Tickets representing post-sale support map to Nutshell Case if Service Cloud is enabled. Ticket status and priority become Lead Status and a custom priority field, or Case Status and Priority respectively. The customer's admin chooses the mapping strategy during scoping.

Lime CRM's configurable Limetypes vary per customer implementation. Each custom Limetype requires field-level analysis because the schema is customer-unique. We treat each Limetype as a separate mapping workstream: we export the live schema definition from the customer's Lime CRM admin during discovery, map each custom property to an equivalent Nutshell custom field on the appropriate standard object (Person, Company, or Deal), and flag any property type that has no direct Nutshell equivalent for the customer's admin to review.

Lime CRM attachments are downloaded individually per record, potentially multiple files per Contact or Deal. We batch downloads and rename files to preserve the parent relationship using a naming convention of ParentObject_ParentID_Filename. Files exceeding 25 MB are flagged before import because Nutshell has file size limits. We validate file integrity against the export manifest to catch any truncated or missing files before the Nutshell import begins.

Lime CRM User records and Deal owners are mapped by email address to Nutshell User records. We validate that destination Nutshell user accounts exist and are active before assigning ownership to avoid orphaned records with null owner fields. Any Lime CRM owner without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes.