Migrate from ASPEC to Nutshell

Scoping and export method confirmation

We run a discovery call with the customer to confirm the ASPEC data export method (UI-based export, direct database access, or a hybrid). We enumerate the objects present in their ASPEC account (Contacts, Companies, Opportunities, Activities), estimate record counts, and begin the mandatory schema discovery step to capture all custom field definitions. We confirm whether the customer has any attachments stored in ASPEC and whether they have database-level access. The output is a written migration scope document with record counts, a custom field inventory, and a confirmed export method.

Schema discovery and Nutshell custom field pre-creation

We analyze the ASPEC custom field schema captured during discovery and map each custom field to a Nutshell custom field of the equivalent type (text, number, date, picklist). We create all custom fields in Nutshell before any record data is written. This includes custom fields on People, Companies, and Deals. If ASPEC has per-user field overrides, we document the mapping logic and either apply a global default or flag the constraint for the customer to resolve in Nutshell after migration.

ASPEC data export and data quality review

We guide the customer through the ASPEC data export from the UI, validating record counts at each step to confirm completeness. We review the exported data for duplicates, missing required fields, and formatting issues (inconsistent date formats, blank email addresses, orphaned owner references). We produce a data quality report with cleaning recommendations and apply standard transformations before writing to Nutshell. Any records with critical issues (no email, no owner, no associated Company) are flagged for the customer's decision before import.

Nutshell pipeline and stage configuration

We configure Nutshell pipelines and stages using the ASPEC pipeline structure captured during schema discovery. This includes stage names, stage order, and probability percentages. We set up the Nutshell pipeline before importing Deals so that stage assignment is valid at the time of import. If ASPEC has multiple pipelines, we create corresponding Nutshell pipelines and map Deals to the appropriate pipeline during the transform step.

Record migration in dependency order

We import data into Nutshell in record-dependency order: Companies first (the anchor object), then People (with Company links resolved at import time), then Deals (with Person and Company links resolved), then Activities (with Person and Company links resolved, timestamps preserved). Owner mapping is validated by email match before each phase. Each phase emits a row-count reconciliation report before the next phase begins. We use Nutshell's REST API for activity import to maintain relationship integrity rather than bulk CSV.

Cutover, validation, and rebuild handoff

We freeze ASPEC writes during the cutover window, run a final delta migration of any records modified during the migration process, then confirm Nutshell as the system of record. We deliver the custom field inventory, data quality findings, pipeline mapping document, and report inventory to the customer's admin team. We support a one-week post-cutover window to resolve reconciliation issues. We do not rebuild ASPEC workflows, automations, or reports inside the migration scope; those are documented for the customer's admin to rebuild in Nutshell as a separate task.