Migrate from Teleforce CRM to Nutshell

Discovery and extraction feasibility audit

We conduct a discovery session with the customer to audit what Teleforce CRM exports via CSV from the UI (Contacts, Companies, Deals, Pipelines, Activities) and what may require database access. We identify any custom fields in use, confirm the owner roster, and flag the unified inbox data as potentially partial. The discovery output is a written extraction scope that lists exactly what Teleforce can export cleanly, what requires manual steps, and what may not export at all — with a risk rating per data category.

Nutshell account provisioning and schema pre-creation

We provision or validate the customer's Nutshell account and pre-create all custom fields (matching Teleforce's field names and types), pipeline stages (matching Teleforce's board layout and probabilities), and Nutshell Users for any owner email matches confirmed in discovery. Custom field creation happens before any import begins to ensure the CSV mapping has destination fields to write to. We also configure any custom field types required — currency fields, date fields, checkbox fields — to avoid silent type mismatches during load.

CSV extraction and normalization

We guide the customer through Teleforce's CSV export process (Contacts, Companies, Deals, Activities) and receive the exported files. We normalize the CSVs: standardize date formats to YYYY-MM-DD, resolve encoding issues, split multi-value fields (phone numbers with type labels), and validate that exported field headers match the field inventory from discovery. Any discrepancies between the exported headers and the known field inventory are flagged for the customer to reconcile before load.

Owner reconciliation and user provisioning

We extract the distinct owner roster from Teleforce (owner name and email on Contacts, Companies, and Deals) and match against Nutshell User records. Any owner without a matching Nutshell User is flagged in a reconciliation report for the customer to provision before record migration begins. OwnerId references on imported records must point to valid Nutshell Users, so this step gates the record import phase.

Import in dependency order

We run the Nutshell import in record-dependency order: Companies first (since People link to them), then People (Contacts), then Deals (with the Person and Company lookups resolved), then Activities (with Person and Deal references resolved). Each phase emits a row-count reconciliation report — records in, records loaded, records skipped with reason — for the customer to validate before the next phase begins. Custom fields are mapped per-phase once the destination schema is confirmed stable.

Cutover, validation, and automation inventory handoff

We freeze writes in Teleforce during the cutover window, run a final delta migration of any records modified since the initial export, then confirm Nutshell as the system of record. We validate a random sample of records against the Teleforce source and deliver a reconciliation summary. We deliver the automation inventory document (Teleforce workflow and bot flow logic documented for manual rebuild) to the customer's admin. We support a three-day hypercare window for reconciliation issues raised by the team.