Migrate from BSI CRM to Nutshell

Discovery and export coordination

We audit the source BSI CRM environment across all active modules, enumerating Contacts, Companies, Deals, Activities, custom objects, and attachment volumes. Because BSI has no self-service export tool, we submit a data export request through BSI's support channel and query the API during discovery to confirm available endpoints and rate limits for the customer's plan tier. We also capture the pipeline stage matrix, custom field definitions, and any industry-specific configurations in use. The discovery output is a written migration scope with explicit identification of what can and cannot be exported automatically.

Schema design in Nutshell

We design the destination schema in Nutshell before any data moves. This includes creating custom fields on People, Companies, Opportunities, and Leads to accommodate BSI's custom object and field data. We configure Nutshell pipeline stages to match the BSI pipeline stage matrix captured during discovery, create multiple Nutshell pipelines if the BSI configuration uses more than one, and set up any required custom fields for BSI's industry-specific deal properties. Nutshell's plan tier determines the number of custom fields available, so we confirm plan compatibility during this phase.

Data extraction and staging

We extract data from BSI CRM using the supported export method (API or support-coordinated export) and stage it in a normalized format. Attachment files are extracted separately with reference paths back to their parent records. All extraction jobs run outside the customer's peak usage window to avoid infrastructure throttling. We validate record counts against BSI's dashboard totals and flag any discrepancies before proceeding to transformation. Any data quality issues — duplicates, incomplete required fields, inconsistent formats — are documented and escalated to the customer's project lead for resolution before transformation begins.

Data transformation and mapping

We transform the staged data into Nutshell-compatible format. Contact records are mapped to People, Companies to Accounts, Deals to Opportunities with pipeline stage mapping applied, and Activities to their Nutshell equivalents with parent record linkage preserved. Custom field values from BSI are mapped to the corresponding Nutshell custom fields created in the schema design phase. Tags and classification values from BSI are mapped to Nutshell custom fields. All transformations are logged with the original BSI field reference for reconciliation traceability.

Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users (validated from the owner reconciliation queue), Accounts (from BSI Companies), People (with Account reference resolved), Opportunities (with People reference, Owner reference, and pipeline stage resolved), Activities (calls, emails, meetings, tasks with parent record linkage preserved), and Attachments (re-linked to their parent records). Each phase emits a row-count reconciliation report before the next phase begins. Any records that fail validation are held in a retry queue and re-processed after root cause identification.

Cutover, validation, and workflow inventory handoff

We freeze BSI CRM writes during cutover and run a final delta migration of any records modified during the migration window. We deliver a written inventory of every active BSI CRM workflow and automation configuration requiring rebuild in Nutshell, with a recommended Nutshell equivalent for each. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild BSI CRM workflows as Nutshell automations inside the migration scope; that work is documented for the customer's admin to complete as a post-migration task.