Migrate from OpenCRM to Nutshell

Scoping and data audit

We audit the OpenCRM tenant for record counts across Contacts, Companies, Deals, Activities, Notes, and custom fields. We confirm the customer's target Nutshell tier and flag whether Enterprise-level API access is required for post-migration workflows. We identify the set of OpenCRM columns to include in the CSV export for each object and document the stage-name set for the Deal pipeline. The scoping output is a written migration scope, a stage-mapping table for customer confirmation, and a custom-field discovery list for Nutshell field creation.

CSV export and data staging

We guide the customer through the OpenCRM UI CSV export process for each object type, selecting all relevant columns including the OpenCRM record ID. We stage the exported CSV files in a secure staging environment, parse and normalise field names, convert date formats to UTC, and deduplicate based on the OpenCRM record ID. Any data quality issues — missing required fields, malformed emails, orphaned records — are flagged in a pre-import audit report for the customer to address or acknowledge before transformation begins.

Nutshell field and pipeline preparation

We create all required Nutshell custom fields (matching the OpenCRM custom field names and types identified during scoping), configure the Deal pipeline with the customer-confirmed stage names, and set up any required Nutshell users to match OpenCRM owners. If the customer is on a non-Enterprise Nutshell tier, we design the migration to use CSV import only, with no API dependency. This step is completed in the customer's live Nutshell environment before any data is loaded.

Companies import with reconciliation

We import OpenCRM Companies into Nutshell as Accounts using the resolved external ID as the matching key. We run a row-count reconciliation and spot-check 20-30 records against the source. Accounts without a valid name or with duplicate entries are flagged for the customer's admin to resolve before the Contact import begins. This phase must complete before Contacts are loaded because Account records are the parent reference for Contact linkage.

Contacts import with parent resolution

We import OpenCRM Contacts into Nutshell as People, resolving each Contact's parent Company to the corresponding Nutshell Account using the OpenCRM Company name or external ID. Contacts without a matching Account are held in a reconciliation queue; the customer confirms whether to create a placeholder Account, merge into an existing Account, or exclude the record. Once the queue is resolved, we commit the Contact import and run a second reconciliation pass to verify the Account-Person linkage.

Deals, activities, and notes import

We import OpenCRM Deals into Nutshell using the stage-mapping table confirmed in step one. Owner assignment resolves by email matching to the Nutshell User table. Activities (calls, meetings, tasks) and Notes are imported after Deals, linked to their parent Account or Person record via the resolved ID. Each phase emits a row-count report; any phase where reconciliation falls below 95 percent is held for review before the next phase begins.

Cutover, validation, and automation inventory handoff

We freeze OpenCRM writes at cutover, run a final delta migration of any records modified during the migration window, then mark Nutshell as the system of record. We deliver a written inventory of OpenCRM workflows, automations, and any active sequences for the customer's admin to rebuild in Nutshell's automation layer. We do not rebuild automations or workflows as part of the standard migration scope. A post-import validation report is delivered covering record counts, linkage verification, and any known gaps in the migration output.