Migrate from Copper to Salesforce Sales Cloud

Copper People records split into Salesforce Lead (for unqualified prospects) or Contact (for qualified contacts with a known company). We apply the split rule during scoping using Copper's People type and status fields, defaulting unqualified records to Lead and those with a Company association to Contact under an Account. We preserve the original Copper People ID in a custom field copper_people_id__c on both Lead and Contact for traceability.

Copper Company records map directly to Salesforce Account. The Company name becomes Account Name; address fields map to BillingAddress compound fields. The Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time. Multi-location companies in Copper become either a single Account with multiple Addresses or an Account hierarchy (parent Account with child Accounts for each location) depending on the customer's chosen Account model.

Copper Opportunities map to Salesforce Opportunity with the pipeline stage name preserved as StageName. The copper monetary value maps to Amount, and the probability field maps to a custom field probability_pct__c since Salesforce stage probabilities are controlled by the sales process. Closed-won and closed-lost reasons from Copper custom properties migrate to Loss Reason and custom win reason fields.

Each Copper pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that defines the allowed stage names and probabilities. Stage order and probability percentages migrate from Copper to Salesforce StageProbability values. Multiple Copper pipelines map to multiple Record Types so that each business line sees its own stage set.

Copper's separate Lead object (distinct from People) maps directly to Salesforce Lead. Lead status values from Copper become Salesforce Lead Status picklist values. Any lead score or lead source data stored in Copper custom properties migrates to custom fields on Salesforce Lead.

Copper Tasks map to Salesforce Task with Status, Priority, ActivityDate, and Description preserved. Task assignment migrates by resolving Copper's owner reference to the Salesforce User ID via email match. Copper task relationships (linked to People, Companies, or Opportunities) map to Salesforce Task WhatId or WhoId depending on whether the related record is a Contact/Lead (WhoId) or Account/Opportunity (WhatId).

Copper email activities map to Salesforce EmailMessage records (the message content and headers) linked to a Task record (the activity timeline entry). The WhoId on the Task points to the migrated Lead or Contact; the WhatId points to the related Opportunity or Account. Email body content and any attachments migrate as ContentDocumentLink attached to the EmailMessage.

Copper call activities map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and recording URL (if stored in Copper) migrate to custom Task fields. ActivityDate is preserved from the original Copper timestamp to maintain timeline ordering.

Copper meeting activities map to Salesforce Event with StartDateTime, EndDateTime, Subject, Location, and Description preserved. Attendees migrate as EventRelation records linked to the migrated Lead, Contact, or User. Meeting notes migrate as Salesforce Note attached via ContentDocumentLink.

Copper Notes (engagement type NOTE) migrate to Salesforce Note records linked via ContentDocumentLink to the parent People, Company, or Opportunity. Note body migrates as rich text. Any files attached to the Note are migrated as ContentDocument records with a ContentDocumentLink to the Note.

Copper Projects have no direct Salesforce standard object equivalent. We map Projects to a Salesforce custom object (Project__c) with a lookup to Account, and the project's child Tasks migrate as Salesforce Task records linked to the Project__c via WhatId. The customer chooses between the custom object approach and a flat task-grouping approach during scoping.

Copper custom fields on People, Companies, Opportunities, Leads, Tasks, and Projects migrate to Salesforce custom fields of equivalent type. We enumerate all Copper Custom Field Definitions via the API before migration, map field types (text, number, date, picklist, checkbox, currency, phone, URL) to Salesforce field types, pre-create the destination fields in the Salesforce org, and migrate values. Fields that reference other Copper records (lookup relationships) are resolved at migration time to the corresponding Salesforce record ID.

Copper tags (flat labels applied to People, Companies, and Opportunities) migrate to Salesforce multi-select picklist fields on the respective objects. We inspect the full tag vocabulary during scoping, create the picklist values in Salesforce, and migrate tag assignments as semi-colon delimited values in the picklist field. Tags that serve a content classification purpose migrate to a custom text field with a label naming convention agreed during scoping.