Migrate from AllClients to Nutshell

Discovery and CSV export extraction

We extract the full AllClients contact export and the separate Notes.csv export. During discovery we validate contact count against the AllClients tier limit (Select: 1,500, Premium: 5,000) to confirm the export captures the complete dataset before cancellation. We inventory all custom field definitions, tag values, group memberships, user accounts, and email templates. We also capture the AllClients Workflow definitions for the template inventory document. The discovery output is a written scope confirming record counts, field mapping, and any data gaps identified during the export.

Notes join and data quality cleaning

We run the Notes.csv join against the main contact export using email as the primary key. We flag contacts where the email changed between exports (orphaned notes), contacts with duplicate emails in the export set (potential note assignment ambiguity), and any notes with empty content. This step produces a cleaned joined dataset and a reconciliation report listing notes that require manual assignment. We do not proceed to Nutshell import schema design until the join is validated and the customer has reviewed the orphaned notes report.

Nutshell account preparation

We create the Nutshell Company records first from the distinct company names in the AllClients contact export. We then create all required custom fields on the Person object to match the discovered AllClients custom field definitions, with type matching (date, number, picklist, text). We configure the migration user's API credentials and validate write permissions for Person, Company, Tag, and custom field objects. If Nutshell's State and Country picklists are enabled, we validate that AllClients address values match the picklist options or route unmapped values to a fallback field.

Owner and user reconciliation

We extract every distinct owner email referenced on AllClients contact records and match against the Nutshell destination account's User table. Owners without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision before migration. Owner assignments on Person records are held until the user mapping is confirmed. Nutshell allows inactive users to own records, so former AllClients users can be provisioned as inactive Nutshell users to preserve historical assignment without granting login access.

Production migration in dependency order

We run production migration in record-dependency order: Companies first (from AllClients company field), then Persons (with CompanyId resolved and owner assigned), then Tags applied to Persons, then Custom Field values on Persons, then Notes appended to Persons from the cleaned Notes.csv join. Email templates are imported into Nutshell's template library. Each phase emits a row-count reconciliation report comparing inserted count to source record count before the next phase begins.

Cutover, validation, and Workflow rebuild handoff

We freeze AllClients writes 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 Workflow template inventory document to the customer's admin with recommended Nutshell Automation Rule equivalents for each migrated workflow. We support a one-week hypercare window where we resolve any data quality issues raised by the customer's team. Workflow rebuild in Nutshell Automation Rules is outside standard migration scope and is handled by the customer's admin or a Nutshell implementation partner.