Migrate from OplaCRM to Nutshell

OplaCRM Accounts map to Nutshell Companies by display name and external_id where present. Address data (street, city, state, country, postal code) maps directly to Nutshell's standard address compound fields. Any locked flag on the Account replicates as a custom property Opla_Locked for admin review since Nutshell has no native record-level locking mechanism.

OplaCRM Contacts map to Nutshell People by email as the primary deduplication key. Name, email, phone, and role fields migrate directly. The contact-to-account link resolves via Account external_id matching against Nutshell Companies at migration time, ensuring the People record attaches to the correct Company owner.

OplaCRM Opportunities map to Nutshell Deals by external_id with stage, close date, close reason, and win or loss status preserved. Stage names migrate by display label rather than internal enum, which prevents a stage labeled CLOSE_WON in OplaCRM from landing in the wrong terminal bucket in Nutshell's pipeline configuration.

OplaCRM Products map to Nutshell Products by name. Pricing may require review if OplaCRM stores list price differently from Nutshell's price book model, and we flag any discrepancy in the pre-flight reconciliation report. Quantity and unit price migrate as line-item fields attached to the related Deal.

OplaCRM Invoices created via CreateOpportunityInvoiceDto map to Nutshell Invoice records where the target account supports it. Invoice amount, date, and payment status migrate directly. Nutshell's invoice numbering scheme may differ from OplaCRM's, and we surface the numbering mapping in the pre-flight review so the customer can decide on a convention before final cutover.

OplaCRM Custom Field values stored as CustomFieldValueDto key-value pairs per record migrate as Nutshell custom fields on the corresponding object. Naming collisions with existing Nutshell properties are prefixed with opla_ and surfaced in the mapping table for the customer to rename or merge before production import.

OplaCRM's composite healthscore per Account has no native Nutshell equivalent because the underlying algorithm is opaque and undocumented. We preserve the numeric value as a custom numeric field on the Nutshell Company record (for example, Opla_Healthscore__c) and flag it in the post-migration handoff so the team can decide whether to use it for prioritization or treat it as a reference value.

OplaCRM stage names stored as plain string enums in the sale_process_stage field map to Nutshell pipeline stages by display label. We configure the Nutshell pipeline with matching stage names and display order before migration begins so that stage values land in the correct bucket. Terminal stages (won and lost) are mapped explicitly to prevent ordering issues.

OplaCRM's opportunities_joint_id field links joint or co-selling opportunities via UUID. Nutshell has no native linked-opportunities concept, so we resolve each UUID into a custom property on the Deal (for example, Opla_Joint_Opportunity_ID__c) and write a matching note so the team can manually reconnect the relationship after cutover if needed.

OplaCRM's locked boolean prevents edits on any record type. We replicate this as a custom boolean property Opla_Locked__c in Nutshell and flag it in the handoff for the customer's admin to handle via permission sets or field-level visibility rules since Nutshell does not support record-level locking natively.

OplaCRM tag arrays on records map to Nutshell tags on the equivalent object. Comma-delimited tag strings are split into individual tag entries. Any tags that do not already exist in Nutshell are created at migration time so that tag-based filtering works immediately after cutover.

OplaCRM Users map to Nutshell Users by email address. Owner assignments on Accounts, Contacts, and Deals resolve by matching the OplaCRM user email against the Nutshell User table. Any OplaCRM owner without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes.