Migrate from Opal CRM to Nutshell

Opal CRM Lead records map to Nutshell Person (if the contact has a direct relationship with a sales opportunity) or Nutshell Lead (if the contact is still unqualified). We apply a qualification split rule during scoping based on whether the Lead has an associated Quotation, a closed stage, or a assigned Sales Representative beyond the initial capture. Source attribution (form, upload, campaign) migrates as a custom field or tag. All original Lead timestamps are preserved as created_date and last_modified_date in Nutshell.

Opal CRM team members (Sales Rep, Manager, Admin roles) map to Nutshell User accounts. We resolve by email address and preserve the role assignment as a note in the handover documentation so the Nutshell admin can assign equivalent permissions (Admin, Standard) post-migration. Role permissions in Opal CRM are not exported as structured data, so we reconstruct the role matrix from the export file's owner-assignment records.

If Opal CRM captures company data alongside Leads, these map directly to Nutshell Company records. Company name, domain, address, and industry fields migrate 1:1 where present. If Opal CRM stores leads without explicit company records, we create a placeholder Company from the Lead's domain field or leave the Company field blank and document the gap for the customer to complete post-migration.

Opal CRM Tour Plans store itinerary data (dates, locations, assigned rep) and expense line items as a single record or flat export. Nutshell has no native Tour or Visit object, so we decompose each Tour Plan into a dated task sequence: one task per scheduled visit with location, date, and linked Person or Lead; individual expense line items are stored as structured notes on the lead visit task or as a custom Expense Notes field. We flag any expense entries that exceed 500 characters for manual review.

Opal CRM Quotations with line items map to Nutshell Quote records if the destination Nutshell plan includes Quotes, or to Opportunity records with quotation line items stored as structured notes and total value stored as Amount. The Opal CRM approval workflow state (Pending, Approved, Rejected) has no native Nutshell field, so we store it as a custom field quotation_status__c on the Quote or Opportunity. Line item product names, quantities, and unit prices migrate directly.

Opal CRM pipeline stages implied by lead engagement status map to Nutshell stage values or a custom picklist field pipeline_stage__c. We preserve the stage order and probability percentages where available in the export. The customer chooses whether to use Nutshell's default stage set (New, Contacted, Qualified, Proposal, Negotiation, Closed Won, Closed Lost) or to create custom stages during migration setup.

Opal CRM activity logs (calls, emails, meetings) against Leads migrate to Nutshell Activity records with the corresponding type. Call duration and disposition, email subject and body, meeting location and attendees map to Nutshell Activity fields where supported, or to structured notes. Activity timestamps are preserved for timeline ordering. Nutshell's native Activity timeline displays these chronologically against the linked Person or Lead.

Opal CRM custom fields on Leads (and possibly other objects) are identified during discovery and mapped to Nutshell custom fields of matching type. Text fields map to Nutshell text custom fields, date fields to date custom fields, numeric fields to number custom fields. Nutshell requires custom fields to be created before import begins, so we create them during the setup phase using the Nutshell custom fields API. The customer reviews the custom field list and approves any field type decisions before migration.