Migrate from Basic Online CRM to Nutshell

Discovery and export assessment

We audit the Basic Online CRM instance for record counts across Contacts, Companies, Deals, Notes, and custom fields. We confirm the customer's tier (Free, Starter, Professional, or Enterprise) to determine export method: CSV for Free through Professional, and documented API for Enterprise. If record counts exceed 5,000 in any object, we flag the need for multi-file export assembly. We also confirm the number of distinct Basic Online CRM users and ask the customer which Nutshell User should own migrated records.

Dual export and association resolution

We run a dual export of Contacts and Deals simultaneously to ensure the association resolution uses a consistent snapshot. We extract the contact_id column from Deals and cross-reference it against the contact list to resolve each numeric ID to a Person name. Any Deal with an unresolved contact_id is flagged as orphaned and held in a reconciliation queue for the customer to resolve before import. We also extract and normalise all custom field values, noting any date-format inconsistencies for customer review.

Data quality review and field mapping confirmation

We present the customer with a pre-import data quality report covering duplicate Contacts, duplicate Organizations, orphaned Deals, and custom field format inconsistencies. The customer reviews and confirms the field mapping between Basic Online CRM custom fields and Nutshell custom field types before we create the Nutshell schema. This step prevents misformatted values from landing in typed Nutshell fields.

Schema creation and owner assignment

We create the Nutshell custom fields confirmed during mapping, set the bulk owner assignment for migrated records, and configure any pipeline stages that match the source Deal stages. If the customer uses Basic Online CRM's basic pipeline board, we replicate the stage names and order in Nutshell's pipeline configuration. Owner assignment is applied as a bulk setting unless the customer provided a per-record mapping table during scoping.

Staged import in dependency order

We write data into Nutshell in record-dependency order: Organizations first (from Companies), then People (from Contacts) with Organisation links resolved, then Tasks (from Deals) with Person links resolved, then Activities (from Notes). Each phase emits a row-count reconciliation report. If any phase produces orphaned records, import pauses and the customer resolves the flagged records before we resume.

Cutover, validation, and attachment handoff

We freeze writes in Basic Online CRM during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the attachment inventory to the customer for manual re-upload and provide a written summary of any orphaned Deals that require manual reassignment in Nutshell. We do not rebuild Basic Online CRM workflow automation in Nutshell because Basic Online CRM has no workflow engine on Free or Starter tiers, and we do not offer post-migration admin rebuild as standard scope.