Migrate from FIVE CRM to Nutshell

FIVE CRM Contacts map 1:1 to Nutshell People. Standard fields — first name, last name, email, phone, address — transfer directly. Owner assignment (FIVE CRM hubspot_owner_id equivalent) maps to Nutshell's assigned_to user by email match. We flag any FIVE CRM Contacts that reference a non-existent Company as orphaned and hold them in a reconciliation queue for the customer to resolve before final import.

FIVE CRM separates Leads from Contacts in its data model. Nutshell does not have a separate Lead object; all records are People with optional type categorization. We migrate FIVE CRM Leads to Nutshell People and set the lead_source field to 'FIVE CRM - Imported Lead' to preserve the origin. Any FIVE CRM lead_score value transfers as a custom field on the Nutshell Person record. If the customer wants to distinguish imported leads from imported contacts at a glance, we create a custom Person field (e.g., original_record_type__c) during migration scoping.

FIVE CRM Companies map to Nutshell Organizations. The Organization record is created before any Person import so that the Person-Organization lookup relationship is satisfied at insert time. Company name becomes Organization name; domain or website maps to the website field. We run a dedupe check against existing Nutshell Organizations during migration to prevent duplicate company records if the customer has been using Nutshell as a secondary CRM alongside FIVE CRM.

FIVE CRM Pipelines with their custom stage names vary by tenant configuration. We map pipeline stages during scoping and create Nutshell Deals with the corresponding stage values. Each FIVE CRM pipeline becomes a separate Nutshell Deal. We confirm the Nutshell plan tier during scoping because the number of allowed custom pipelines is tier-gated (Growth allows 3, Pro allows 5, Business and above allow unlimited pipelines). Stage probabilities migrate from FIVE CRM to Nutshell Deal stage weights.

FIVE CRM's Campaigns object tracks email marketing sequences and campaign membership. Nutshell does not have a native Campaign object; marketing sequences are handled via the Nutshell Engagement suite. We migrate campaign membership as tag values on the associated Person records. Campaign name becomes the tag name prefixed with 'Campaign:' (e.g., 'Campaign: Q1 Outreach'). Individual email engagement events (opens, clicks) do not transfer because Nutshell Engagement stores this data natively and FIVE CRM does not expose a bulk export endpoint for granular engagement history.

FIVE CRM Tasks with due dates, assignees, completion status, and type flags map to Nutshell Activities. We preserve the original due date, completion status, and assignment by email-matching to the Nutshell user. FIVE CRM task type distinctions (call, email, meeting, follow-up) map to Nutshell Activity type where available, or transfer as a custom activity_type field. We flag any FIVE CRM task with an attachment over 10MB for separate file handling due to Nutshell API size limits.

FIVE CRM relies heavily on custom fields for telemarketing-specific data capture. We enumerate every custom field during scoping, confirm its data type against FIVE CRM's export schema, and map it to a Nutshell custom field of the equivalent type. Nutshell custom-field limits are plan-gated (Foundation 5, Growth 15, Pro 30, Business 60, Enterprise unlimited), so we confirm the destination plan before designing the field map. Any FIVE CRM custom field exceeding the destination plan's limit is flagged for the customer to choose: upgrade the Nutshell plan or consolidate fields pre-migration.

FIVE CRM Tags label records for segmentation and campaign targeting. Tags migrate to Nutshell Tags on the corresponding Person or Organization record. Multi-select tag fields in FIVE CRM may generate multiple rows per Person during import; we handle this with a tag-normalization step that splits multi-select values into individual Nutshell tag entries. The customer chooses whether to prefix tags with their origin (e.g., 'fivecrm_tagname') during scoping.

FIVE CRM User records (names, emails, roles, assignment permissions) map to Nutshell Users by email match. We extract every distinct owner referenced on Contact, Company, Lead, Pipeline, Campaign, and Task records and resolve against Nutshell's User table. Any FIVE CRM owner without a matching Nutshell User goes to a reconciliation queue; the customer's admin provisions missing Users before record import resumes. Role discrepancies are flagged as post-migration manual reassignment items.

File attachments associated with FIVE CRM Contacts, Companies, or Deals migrate as files attached to the corresponding Nutshell Person, Organization, or Deal record. Attachments over 10MB are flagged for separate handling due to Nutshell API size constraints. We re-upload from the source file store rather than attempting a binary transfer through the import API. PDF and image attachment types migrate cleanly; we flag any attachment in a non-standard format for manual verification post-migration.