Migrate from Less Annoying CRM to Nutshell

LACRM Contacts map to Nutshell People records. LACRM's standard fields (FirstName, LastName, Email, Phone, Address, Tags) map 1:1 to Nutshell's corresponding Person fields. LACRM's UID primary key must be stored as a string throughout the migration pipeline to avoid precision loss from float rounding in standard data tools. We preserve the LACRM UID in a custom field lacrm_uid__c on the Nutshell Person record for future reference and cross-system reconciliation.

LACRM Companies map to Nutshell Accounts. The Company Name maps to Account Name, and the Company website maps to the Account website field. Account records are created before any Contact import so that the Person-to-Account relationship is satisfied at the moment of Person insert. LACRM's relationship table linking Contacts to Companies is resolved during migration by matching the lacrm_company_id reference to the Nutshell Account record created from the corresponding LACRM Company.

LACRM Pipeline Items map to Nutshell Opportunities. LACRM pipeline stages are free-text and fully customizable per account, which means every LACRM account has a unique set of stage names. We extract the full stage list during scoping, map each to a corresponding Nutshell pipeline stage, and configure Nutshell's pipeline stages in the destination before migration begins. The mapping document is validated with the customer during the scoping call to ensure stage alignment and probability assignment match the original LACRM workflow.

LACRM Notes attached to contacts, companies, or pipeline items migrate with their timestamp, author, and body content preserved. Notes are treated as standalone objects in LACRM and linked by relationship records. We create Nutshell Notes linked to the corresponding Person, Account, or Opportunity using the migrated record's Nutshell ID, which is resolved after the parent record insert completes.

Tasks associated with contacts, companies, or pipeline items migrate including their due date, assignee, completion status, and linked contact reference. Open tasks migrate as open; completed tasks migrate with their completion timestamp. LACRM's task priority (High, Medium, Low) maps to Nutshell's priority field using the corresponding enumerated values. Assignee resolution uses email matching against the Nutshell User table.

Calendar events (meetings, calls) logged against contacts migrate with their timestamp, title, description, and linked contact reference intact. LACRM event types (Meeting, Call) map to Nutshell event types. Attendees from the original LACRM event are mapped to Nutshell Person records that have been created during the migration. We set the ActivityDate on the Nutshell Event to the original LACRM timestamp to preserve timeline ordering.

Files attached to contacts or companies are exported as base64-encoded content from LACRM and re-created in Nutshell as Attachment records linked to the corresponding Person or Account. LACRM's 25GB per-user storage allocation means file size and volume must be audited during scoping. Files exceeding Nutshell's attachment size limits are flagged and resolved before migration.

Tags applied to contacts or companies migrate as-is into Nutshell's Tag system. Multi-select tag fields from LACRM are preserved as comma-separated tag assignments in Nutshell. LACRM's tag vocabulary is retained verbatim so that any filtering or segmentation built on tags in LACRM maps directly to Nutshell's tag-based filtering.

Custom fields exist on Contacts, Companies, and Pipeline Items in LACRM. We audit all custom field names and types (text, date, number, dropdown) during scoping and pre-create the corresponding custom fields in Nutshell before any record import begins. Nutshell's documentation explicitly recommends defining custom fields first and then mapping import files to those fields to prevent cleanup work later. Dropdown fields in LACRM migrate as Nutshell dropdown fields using the same option values; the order of options is preserved as defined in LACRM.

LACRM user accounts, names, email addresses, and permission levels migrate as Nutshell Users. LACRM's role model is simple (Admin vs. Standard User). We map this to Nutshell's user roles, flagging any LACRM Groups that control data visibility as requiring Nutshell Teams configuration post-migration. User provisioning is validated before the migration begins because OwnerId references on Opportunities and Tasks require a resolved User record.