Migrate from Access CRM to Nutshell

Discovery and extraction method assessment

We audit the source Access CRM environment across all active objects (Contacts, Companies, Opportunities, Cases, Pipelines, Activities, Attachments), custom fields, and any visible cross-module references to Access Pay & Bill, Access Elite, or Servelec. We also assess the available extraction method — typically admin-level CSV exports or available API endpoints — and document any data-holding patterns unique to the tenant. The discovery output is a written migration scope document including the extraction method, record counts per object, and a preliminary cross-module reference audit.

Cross-module reference audit and resolution

We run a full scan of Access CRM records for foreign-key references to Access Pay & Bill workers, Access Elite client records, and Servelec care episodes. Every reference is classified as either strippable (the reference can be safely removed without business impact) or retainable (the customer needs a human-readable text note preserved). We deliver a cross-module reference register to the customer's admin for sign-off before extraction begins. No records move until this register is approved.

Pipeline stage mapping and Nutshell schema setup

We capture the complete list of Access CRM pipeline stage names and deliver a stage-mapping matrix. The customer's admin reviews and approves the mapping, including which Access CRM stages route to which Nutshell pipeline and which unmapped stages default to an Archive pipeline. We then configure the Nutshell pipeline stages (and multiple Nutshell pipelines if the source has more than one) and create the custom Deal fields for Worst/Likely/Best probability preservation before any data import.

Staging migration and reconciliation

We run a full migration into a Nutshell staging environment (a trial or sandbox account) using production-like data volume. The customer's admin reconciles record counts, spot-checks 20-30 records against the Access CRM source, and reviews the stage mapping and probability custom fields. Any mapping corrections — field name mismatches, incorrect stage routing, duplicate records — are resolved in the staging environment before the production migration begins.

User reconciliation and Nutshell User provisioning

We extract every distinct Access CRM Owner referenced on Contacts, Companies, Opportunities, and Cases and match by email against the destination Nutshell account's User list. Owners without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision. Migration cannot resume past this step because Nutshell requires an Owner assignment on Deal and Case records at import time.

Production migration in dependency order

We run production migration in record-dependency order: Companies first (from Access CRM Companies), then People (from Access CRM Contacts with CompanyId resolved), then Deals (with stage mapping applied and Worst/Likely/Best custom fields populated), then Cases (with cross-module references resolved), then Activities (calls, emails, meetings, notes via batched API inserts), then Attachments (as file references). Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and workflow inventory handoff

We freeze Access CRM writes during cutover, run a final delta migration of records modified during the migration window, then enable Nutshell as the system of record. We deliver the Access CRM workflow inventory document to the customer's admin for rebuild in Nutshell workflows. We support a one-week post-migration window where we resolve any reconciliation issues raised by the team. We do not rebuild Access CRM workflows as Nutshell automations inside the migration scope; that is a separate engagement or an internal admin task.