Migrate from Optimiser CRM to Nutshell

Discovery and field enumeration

We audit the source Optimiser CRM instance for record volumes across Contacts, Companies, Deals, Leads, and Activities. Because Optimiser has no public API, we request access to the CSV export utility and run trial exports to enumerate the full field inventory, including every active custom field. We segment by object type and identify any pipeline stage configurations, owner assignments, and tag sets. The discovery output is a written migration scope document listing record counts, field mappings, and any custom fields that will require Nutshell custom field creation.

Custom field and pipeline schema design in Nutshell

We create the destination schema in Nutshell before any data moves. This includes provisioning custom fields on People, Companies, and Deals to match every enumerated Optimiser custom field. We configure Nutshell Pipelines with stage mappings derived from the source Optimiser pipeline configuration, including probability percentages and stage type assignments. If the target Nutshell plan has field limits, we reconcile the custom field count against the tier cap and flag exclusions for customer approval.

CSV export pagination and data extraction

We run Optimiser's CSV export utility with automated pagination across multiple export batches to capture the complete dataset for each object type. Each export batch is validated for record count completeness and merged into a master dataset before transformation. Duplicates are identified by email (for People) and company name (for Companies) and flagged for customer review. Records with missing required fields are logged separately for remediation or exclusion.

Owner reconciliation and user provisioning

We extract every distinct Optimiser User referenced on Deals and Activities and match by email address against the Nutshell destination's user list. Users without a matching Nutshell account are held in a reconciliation queue for the customer's admin to provision. Owner assignment cannot be resolved without confirmed Nutshell user records, so this step gates the Deals and Activities migration phases.

Production migration in dependency order

We run production migration in record-dependency order: Companies first (to establish the parent record for People), then People (with Company lookups resolved), then Leads (if separate from People), then Deals (with OwnerId and CompanyId resolved), then Activity history (calls, emails, meetings, tasks with parent-record references resolved). Each phase emits a row-count reconciliation report before the next phase begins. Attachments are downloaded from Optimiser and re-uploaded to Nutshell linked to the correct parent record.

Cutover, validation, and automation rebuild handoff

We freeze Optimiser CRM writes during cutover and run a final delta migration to capture any records modified during the migration window. We validate record counts, spot-check sample records against the source, and enable Nutshell as the system of record. We deliver the automation rebuild checklist documenting every Optimiser workflow, assignment rule, and trigger with a recommended Nutshell Workflow equivalent. We support a 72-hour hypercare window for reconciliation issues. Rebuilding Optimiser automations as Nutshell Workflows falls outside standard migration scope and is handled by the customer's admin team.