Migrate from Concord CRM to Nutshell

Discovery and plan audit

We audit the source Concord CRM instance: record counts for Contacts, Companies, Deals, Products, and Activities; active workflow configurations; custom field inventory with data types; and user list with role assignments. We simultaneously audit the customer's Nutshell account: current plan tier, existing custom field count, and user provisioning status. The discovery output is a written migration scope with record counts, a custom field gap analysis against the Nutshell plan tier, and a workflow inventory document. If the Nutshell plan has insufficient custom field slots, we recommend a plan upgrade before migration begins.

Role and permission setup in Concord

We verify that the API token user in Concord CRM has the export permission enabled at the role level. If the current API token user lacks export permissions, we request that the customer assign the export permission to the user account or create a new admin-level user for migration use. We also extract the complete user list (name, email, role) from Concord for mapping to Nutshell users. Concord users are held in a reconciliation queue until the customer provisions corresponding Nutshell user accounts.

Data extraction with pagination sequencing

We extract data from Concord CRM in dependency order: Companies first, then Contacts, then Deals, Products, and Activities. Each object extraction uses sequential page iteration at 100 records per page, monitoring X-RateLimit-Limit and X-RateLimit-Remaining headers to avoid 429 errors. For each Contact, we capture the company_id foreign key for later lookup resolution against the Nutshell Organization created during the Organization import phase. Custom fields are extracted with their UUID keys and data types for later type mapping to Nutshell's custom field schema.

Nutshell schema pre-creation and custom field mapping

Before any data loads into Nutshell, we pre-create the custom Person, Organization, and Activity fields that correspond to Concord's custom fields. We map Concord field data types (boolean, date, select, text, number) to equivalent Nutshell field types. If the customer's Nutshell plan tier limits the number of custom fields, we consolidate low-value fields and flag the remainder for manual post-migration entry. The Nutshell Organization and Person custom fields are deployed before the first record insert.

Sandbox migration and reconciliation

We run a full migration into a Nutshell test account (or a clean Nutshell account designated for validation) using the extracted Concord data. We reconcile record counts between Concord source and Nutshell destination for each object type. We spot-check 20-30 records per object for field-level accuracy, verifying that custom field values, Organization links on Persons, and Activity timestamps are preserved correctly. Any mapping errors are corrected in the transform logic before the production migration begins.

Production migration and cutover

We run the production migration in dependency order: Organizations first (from Concord Companies), then Persons (from Concord Contacts with Organization lookup resolved), then Products, then Activities (Deals, Calls, Meetings, Tasks with Person and Organization links resolved), and finally custom field data. Each phase emits a reconciliation report showing record count, error count, and skipped records before the next phase begins. We freeze Concord writes during the cutover window and run a final delta extraction of any records modified during migration. Nutshell becomes the system of record after cutover.

Workflow handoff and post-migration support

We deliver the Concord Workflow Inventory document to the customer's admin team within two business days of cutover. The document lists every active Concord workflow with its trigger, conditions, actions, and recommended Nutshell automation equivalent. We support a five-business-day hypercare window where we resolve any data quality issues raised by the team. We do not rebuild Concord workflows as Nutshell automations inside the migration scope; that work is handled by the customer's admin using the workflow inventory as a rebuild guide.