Migrate from Star CRM to Nutshell

API discovery and scoping call

We perform live API discovery calls against Star CRM to infer the actual field structure across all active record types. We export a sample of 10-20 records per object (Contacts, Companies, Deals, Activities) and document every observed field name, type, and value pattern. During the scoping call, we review the discovered schema with the customer, identify custom fields, pipeline stages, user accounts, and any non-standard record types, and confirm the target Nutshell configuration. This step is required before any mapping work begins because Star CRM provides no public schema reference.

Data quality audit and cleansing

We run a data quality audit against the Star CRM export to identify duplicate records (deduped by email), incomplete records (missing required fields), inconsistent address formats, and stale Deals that should be archived rather than migrated. We present a cleansing report to the customer and perform agreed-upon deduplication and normalization before the migration runs. Pre-migration data cleansing reduces migration time and prevents dirty data from spreading into Nutshell, where it is harder to fix after go-live.

Nutshell custom field and pipeline configuration

We pre-configure Nutshell before any data loads. This includes creating any custom fields discovered in Star CRM (with field types matched to Nutshell's supported types: text, long text, currency, date), configuring deal pipeline stages to match the Star CRM stage names and probabilities, and setting up the Nutshell user accounts that will receive migrated records. Import2 configuration is set up during this phase so that the migration is ready to run once data extraction is complete.

Sample migration and reconciliation

We run a sample migration using a subset of the production data volume (typically 100-500 records per object) into the customer's Nutshell environment to validate the field mappings and reconciliation logic. The customer reviews the sample import in Nutshell, spot-checks 20-30 records against the Star CRM source, and signs off before the full production migration begins. Any mapping corrections happen at this stage. This step prevents field mapping errors from reaching production data.

Production migration in dependency order

We run the full production migration in record-dependency order: Companies first (independent records), then People (with Company lookup resolved), then Deals (with People and Company lookups resolved), then Activities (with post-load re-association to parent People or Deals), then Attachments (with file-to-record re-association via manifest). Each phase emits a row-count reconciliation report. We freeze Star CRM writes during the cutover window and run a final delta migration of any records modified during the migration run.

Validation, cutover handoff, and automation inventory

We validate the production migration by matching record counts, spot-checking 50 random records against Star CRM, and confirming activity linkage in Nutshell. We deliver a written handoff document that includes the full data inventory (records migrated, records skipped with reasons), a list of custom fields created in Nutshell, a written inventory of all Star CRM automations or workflows that require rebuilding in Nutshell, and a recommended Nutshell automation approach for each item. We do not rebuild automations as part of the standard migration scope.