Migrate from Copper to Twenty CRM

Copper People records map to Twenty Persons. Name, email, phone, address, and social links transfer as standard fields. Copper's contact photo URL migrates to Twenty's avatar field if the URL is publicly accessible. Any Person with a status of Lead in Copper gets a custom tag migrated rather than a separate record type, since Twenty Persons serve as both lead and contact records.

Copper Companies map directly to Twenty Companies with domain, annual revenue, employee count, and industry preserved. The Copper People-to-Company linkage migrates as a Person-Company relationship in Twenty. We resolve the Company record before importing related People to satisfy the lookup dependency.

Copper Opportunities map to Twenty Opportunities with name, amount, stage, expected close date, and probability. Pipeline Stage maps to Twenty's pipeline stage. Note: Twenty v2.0 has no automated incremental numbering system for Opportunity IDs, per the Twenty v2.0 changelog discussion on Reddit. We flag this gap during scoping and advise whether to assign sequential IDs before import or accept Twenty's UUID-based identifiers. Closed-Won and Closed-Lost outcomes from Copper migrate as stage values.

Copper's separate Lead object does not have a direct Twenty equivalent. Twenty Persons serve as both leads and contacts. We migrate Copper Leads as Twenty Persons with a custom tag (e.g., source=copper_lead) and preserve the original Lead_Status as a custom field (copper_lead_status__c). The GitHub issue #10422 documents that Twenty's Lead-to-Opportunity conversion is manual rather than built-in, so we advise customers to plan the qualification workflow in Twenty post-migration.

Copper Pipelines (available on Basic and above) map to Twenty Pipelines. Stage names, stage order, and probability percentages transfer. If Copper has multiple pipelines, each maps to a separate Twenty Pipeline. We configure pipeline visibility and stage labels in Twenty before importing Opportunities.

Copper Projects are a lightweight project management object not natively replicated in Twenty's standard workspace. We migrate Projects as Twenty Workspaces and their associated Tasks as Twenty Tasks linked to the workspace. Customers who rely heavily on Copper Projects as a project management layer rather than a CRM feature should plan a parallel migration to a dedicated project tool or document the project-to-task mapping during scoping.

Copper Tasks map to Twenty Tasks with title, due date, assignee (resolved via User email match), status, and related record link preserved. Copper's task priority maps to Twenty's priority field. Tasks with no assignee are migrated with an unassigned flag for the customer to resolve.

Copper Activities (emails, calls, meetings, notes) linked to People, Companies, or Opportunities migrate to Twenty Activity records. Activity type, date, duration, body, and related record link transfer. We resolve the parent Person, Company, or Opportunity ID at migration time to maintain the activity timeline linkage. Note that if activities reference Google Drive-attached files, those attachments must be re-linked after the file migration step.

Copper Custom Fields on People, Companies, Opportunities, Leads, Projects, and Tasks are enumerated via the Copper Custom Field Definitions API before migration. We create equivalent custom fields in Twenty (field type matching where possible: text to text, number to number, date to date, checkbox to boolean). Multi-select fields map to Twenty multi-select picklists. Custom field ordering and section placement in Copper are noted for manual recreation in Twenty's field layout editor.

Copper Tags are flat labels applied to People, Companies, and Opportunities. We migrate all tags as-is and create them in Twenty's tag system. Tags used for segmentation or pipeline classification are noted separately for the customer to assess whether Twenty's pipeline stage or custom field better serves the original use case.

Copper attachments live in Google Drive, not inside Copper's own storage. We extract attachment metadata (filename, URL, associated record) during scoping, then coordinate with the customer to migrate the underlying Google Drive files. Files can be re-uploaded to Twenty directly or re-linked via shared URLs if the customer maintains a Google Drive workspace. Without this step, attachment references in Twenty become broken links.

Copper Owners map to Twenty Users resolved by email address. We extract every distinct Owner referenced on People, Company, Opportunity, Task, and Activity records. Any Copper Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision the account before record import resumes, since OwnerId references are required on most record inserts.