Migrate from Copper to Nutshell

Copper's People records map to Nutshell Persons with direct field transforms: name fields (first_name, last_name), email addresses, phone numbers, postal addresses, and social URLs. We use the person's email as the dedupe key during import to prevent duplicate creation. Custom fields on People migrate to Nutshell Person custom fields, which we pre-create with matching types (text, number, date, picklist) before any Person records are written. The Copper Person-to-Company linkage maps to Nutshell's Company Person associations, which we write after both objects are in place to satisfy the lookup dependency.

Copper Companies map 1:1 to Nutshell Companies. The company name, domain, industry, phone, address, and annual revenue fields transfer directly. We use the company name as the dedupe key and create Companies before any Person import so that the Person-to-Company relationship is established at insert time rather than patched afterward.

Copper Opportunities map to Nutshell Deals with the deal name, monetary value, expected close date, and pipeline stage transferred. The Copper pipeline stage name maps to the Nutshell Deal status value; we create a Nutshell stage mapping table during schema design so that stage names from Copper appear correctly in Nutshell's deal pipeline view. Loss reason and win reason custom properties from Copper migrate to Nutshell's loss_reason field if configured, or to a custom deal field if the customer's workflow uses a non-standard win-loss taxonomy.

Copper's separate Lead object (distinct from People) requires a scoping decision: whether to import as Nutshell Leads or merge into Nutshell Persons. If the customer's sales process treats Leads as unqualified prospects that do not yet have a Company relationship, we create Nutshell Leads and preserve Copper's lead_status as a custom field. If leads are already associated with Companies and have a sales-qualified status, we merge them into Nutshell Persons and set a lead_source property from Copper's original lead data. The customer makes this decision during scoping, and we document both paths with a sample record count for each approach.

Copper pipelines and their custom stages map to Nutshell Deal statuses. We extract the full stage list from Copper (stage name, stage order, probability percentage, and stage type — open, won, or lost) and create matching statuses in Nutshell before any Deal records are imported. Nutshell's deal statuses are a flat ordered list per pipeline, which maps cleanly from Copper's pipeline stage model with no multi-pipeline complexity at this scale.

Copper Tasks map to Nutshell Tasks with due date, task name, status, priority, and assignee preserved. We resolve Copper owner IDs to Nutshell user emails during owner reconciliation and use the resolved email to set the Nutshell task assignee at import time. Open tasks and completed tasks both migrate; the status field maps directly (Copper open maps to Nutshell pending, Copper completed maps to Nutshell completed).

Copper Projects are a lightweight grouping object with associated tasks. Nutshell does not have a native project object, so we map Projects to a tagged task grouping: the project's tasks migrate as Nutshell Tasks with a tag matching the project name. This preserves the grouping context without forcing a structural fit to a non-existent object. The customer chooses whether to create a Nutshell tag per project name or a custom picklist field on tasks during scoping.

Copper Activities — email logs, call records, meeting records, and notes — map to Nutshell's Activity system with the activity type, date, duration (for calls and meetings), notes content, and related Person or Company preserved. Emails migrate as note-type activities with the email body and timestamp. Call duration and call disposition migrate to custom fields. Meeting details include the attendee list and location. We write activities after Persons and Companies are loaded so that the activity-to-contact relationship is satisfied at insert time. Large activity histories require multiple API passes due to Copper's 180 req/min ceiling.

Copper custom fields on People, Companies, Opportunities, Leads, Projects, and Tasks enumerate from the Custom Field Definitions API. We map each field's type (text, number, date, currency, picklist, checkbox, multi-select) to an equivalent Nutshell custom field type. Nutshell's ceiling is 250 custom fields per object; we flag any customer whose total custom field count approaches this ceiling before migration begins so the customer can decide whether to consolidate or archive retired fields.

Copper's flat tag model on People, Companies, and Opportunities transfers as-is to Nutshell Tags. We map the tag label directly and attach it to the corresponding Nutshell Person, Company, or Deal record. Tags with no corresponding record are held in a reconciliation report for the customer's admin to review.