Migrate from Teamwork CRM to Nutshell

Discovery and extraction strategy

We audit the Teamwork CRM account across record counts (Companies, Contacts, Leads, Opportunities, Activities), active custom field definitions, pipeline and stage configurations, and owner list. We also confirm the destination Nutshell plan tier and verify custom field capacity. Because Teamwork CRM lacks a bulk API endpoint, we design an extraction strategy combining REST API paginated fetches (with 120 req/min throttling) and list-view CSV exports for objects where column selection is required. We surface the Opportunity-to-Lead schema reduction and the custom field plan limit as migration prerequisites if the destination plan requires verification.

Schema preparation in Nutshell

We configure the Nutshell destination before any data loads. This includes pre-creating all custom fields (matching Teamwork's text, integer, and dropdown types), pre-populating dropdown option values, and setting up Lead status values to match the Teamwork pipeline stages documented in the discovery output. If the customer has multiple pipelines in Teamwork, we create a written pipeline configuration document for Nutshell Settings > Leads > Statuses that the customer configures manually before production migration begins.

Sandbox validation run

We run a representative migration into a Nutshell sandbox or trial environment using a sample of 100-200 records per object type. The customer reconciles field mapping accuracy, custom field values, organization-person relationships, and activity linkage against the Teamwork CRM source. Mapping corrections are documented and applied to the production migration script. This step prevents field mapping corrections from occurring mid-production run, which would require a partial rollback.

Owner and user reconciliation

We extract every distinct Teamwork CRM Owner and map them by email to Nutshell Person records that will serve as user accounts. Any Teamwork Owner without a matching Nutshell user is placed in a reconciliation queue for the customer's admin to provision. Teamwork user records with zero working hours (a known V2 people endpoint issue for legacy profiles) are flagged and surfaced for manual review. Migration cannot proceed past record import until all OwnerId references have a valid target.

Production migration in dependency order

We run production migration in this sequence: Organizations (from Teamwork Companies), Persons (with OrganizationId resolved), Leads (Teamwork Leads and Opportunities converted to Lead records with custom fields for deal data), Activities (calls, meetings, tasks linked to Persons and Leads via owner email resolution). Each phase emits a row-count reconciliation report comparing the count loaded in Nutshell against the count extracted from Teamwork CRM. Discrepancies above the tolerance threshold trigger a re-run of that phase before proceeding.

Cutover, delta sync, and inventory handoff

We freeze writes in Teamwork CRM during the cutover window, run a final delta migration capturing any records modified during the migration, then mark Nutshell as the system of record. We deliver the Pipeline Configuration document (mapping Teamwork pipelines to Nutshell Lead statuses), the Custom Filter inventory (Teamwork saved filters as reference metadata), and the Active Workflow and Automation list (for manual rebuild in Nutshell). We provide a one-week hypercare window for reconciliation issues. Workflows, sequences, and automations are not migrated as code; they require manual rebuild in Nutshell's automation settings or a separate engagement.