Copper to Salesforce migration
We migrate People, Companies, Opportunities, Activities, and Custom Fields from Copper into Salesforce with the Lead-versus-Contact split resolved during scoping, Activity history loaded through the Bulk API, and every Copper tag and custom property mapped to a typed Salesforce field before cutover. We coordinate Google Drive file re-linking separately so that attachment references remain intact after migration.
FlitStack AI migrates lead or contacts, accounts, opportunities, record type + sales process and leads from Copper to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

What moves from Copper to Salesforce?
Moving from Copper to Salesforce is a structural migration that resolves four fundamental schema differences.
Read the full summary
Copper uses People and Companies as primary records with a separate Leads object; Salesforce splits unqualified prospects into Lead and qualified buyers into Contact attached to an Account. We resolve that split during scoping, create matching Account records first so Contact import satisfies the lookup, and preserve the original Copper relationship data throughout. Copper's Activities (emails, calls, meetings) require a type-by-type mapping to Salesforce Task, Event, and EmailMessage. Copper's API rate limit of 180 requests per minute constrains extraction speed, requiring paginated reads and batch scheduling that extend the migration window for large record sets. Custom fields, tags, and pipeline stages migrate fully. We do not migrate Workflows, bulk email sequences, or reports as code; we deliver a written inventory for your admin to rebuild in Salesforce Flow.
People → Lead or Contact (split required)
Copper People records split into Salesforce Lead (for unqualified prospects) or Contact (for qualified contacts with a known company).
How it maps
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.
Companies → Account
Copper Company records map directly to Salesforce Account.
How it maps
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.
Opportunities → Opportunity
Copper Opportunities map to Salesforce Opportunity with the pipeline stage name preserved as StageName.
How it maps
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.
Pipelines → Record Type + Sales Process
Each Copper pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that defines the allowed stage names and probabilities.
How it maps
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.
Leads → Lead
Copper's separate Lead object (distinct from People) maps directly to Salesforce Lead.
How it maps
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.
Tasks → Task
Copper Tasks map to Salesforce Task with Status, Priority, ActivityDate, and Description preserved.
How it maps
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).
- PeopleLead or Contactsplit
- CompaniesAccount1:1
- OpportunitiesOpportunity1:1
- PipelinesRecord Typetransformed
- LeadsLead1:1
- TasksTask1:1
+ 7 more in the mapping below
How Copper and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Copper | Salesforce |
|---|---|---|
| Contact model | Single People object with role-based type | Separate Lead and Contact objects with explicit Convert action |
| Account model | Companies as flat records linked to People | Accounts as parent to Contacts with hierarchical structures |
| Pipeline count | Basic 1, Professional up to 5 pipelines | Unlimited Opportunity record types and sales processes at all paid tiers |
| Custom objects | Not available at any tier | Available from Professional tier without setup fees |
| Workflow automation | Copper Workflows on Professional+ only | Salesforce Flow on all paid tiers; Process Builder on Professional |
| Attachment storage | Files stored in Google Drive, linked to Copper records | Files stored in Salesforce CRM Content or Files object with ContentDocumentLink |
| API rate limit | 180 requests per minute | 100,000 API calls per day on Enterprise; 10,000 on Professional |
What to watch for in a Copper to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
People-to-Lead/Contact split requires a deliberate design decision
Copper's People object covers both qualified contacts and unqualified prospects without a structural distinction.
How we handle it
Salesforce separates these into Lead (unqualified) and Contact attached to Account (qualified). We define the split rule during scoping based on the customer's Copper data — typically using the presence of a Company association and the People type field — then apply it during transformation before any records are written. Skipping this design step results in orphaned Contacts (no AccountId) or Leads that should have been Contacts from day one, both of which require post-migration cleanup and potentially duplicate work.
Copper API rate limit of 180 requests per minute constrains extraction speed
Copper's API enforces 180 requests per minute per User ID.
How we handle it
Large record sets with activity logs, attachment metadata, and custom field definitions can require hundreds of API calls across multiple pages. We implement paginated reads with exponential backoff and estimated extraction time during scoping. For migrations exceeding 50,000 total records, we schedule extraction in off-peak hours to avoid hitting the ceiling during business hours and extend the extraction window to multiple sessions. We warn customers when their dataset size will push extraction beyond a single working day.
Workflows, bulk email, and custom reports do not migrate to Salesforce
Copper Workflows, bulk email sequences, and custom reports are tier-gated features (Professional and Business tiers) that have no direct Salesforce equivalent as configured records.
How we handle it
We do not migrate them as code because the automation models are structurally incompatible. We document every active Copper Workflow, bulk email sequence, and custom report during discovery and deliver a written inventory with a recommended Salesforce Flow or Salesforce Sales Engagement rebuild path. The customer's admin or a Salesforce partner handles the rebuild post-migration.
Attachment files stored in Google Drive must be re-linked in Salesforce
Copper stores files in the user's associated Google Drive, not in Copper's own storage.
How we handle it
Migrations that include file attachment metadata require separate Google Drive file migration: we verify read access for the service account, transfer file ownership to the destination Google account or a shared drive, and re-link file references as Salesforce Files (ContentDocument with ContentDocumentLink) in the destination org. Without this step, all attachment links become broken references and the activity timeline loses its supporting documents.
Data format differences cause silent field rejection without pre-mapping
Copper and Salesforce use different formats for address compounds, phone numbers, currency values, and date timestamps.
How we handle it
We run a data audit during scoping that validates field-level format compatibility and flags records that will fail Salesforce validation rules (required picklist values, conditional required fields, regex patterns on phone or email) before any records are written. Migrations that skip this audit typically see 5-15% record rejection on first load and require a correction pass that adds time and cost.
How the migration runs
Discovery and scoping
We audit the source Copper account across plan tier, People count, Company count, Opportunity volume, activity engagement counts (emails, calls, meetings), pipeline definitions, custom field definitions, active Workflows, bulk email sequences, and tag vocabulary.
What this step covers
We pair this with a Salesforce edition review: Professional ($80/user) covers most Copper migrations; Enterprise ($165/user) is required if the customer needs record-triggered Flow at scale or advanced territory management. The discovery output is a written migration scope with record counts, object list, and a Salesforce edition recommendation.
Schema design and Salesforce sandbox setup
We design the destination schema in Salesforce.
What this step covers
This includes creating custom fields (with types matched to Copper field definitions), Record Types per Copper pipeline, Sales Processes with stage probabilities, Page Layouts per Record Type, and the People-to-Lead/Contact split rule agreed with the customer. We deploy the initial schema into a Salesforce Sandbox (Full Copy or Partial Copy) for validation before production. Custom fields are named with a copper_ prefix (e.g., copper_lead_source__c) to distinguish migrated data from records created post-migration.
Sandbox migration and reconciliation
We run a full migration into the Salesforce Sandbox using a representative data volume.
What this step covers
The customer's RevOps or Salesforce admin reconciles record counts (People in, Leads out, Contacts out, Accounts in, Opportunities in, Activities in), spot-checks 25-50 records against the Copper source, and validates field-level accuracy for at least three core objects. Any mapping corrections, field-type mismatches, or validation rule conflicts are resolved in sandbox before production migration begins.
Owner reconciliation and Google Drive file audit
We extract every distinct Copper owner referenced on People, Company, Opportunity, and Activity records and match by email against the Salesforce destination org's User table.
What this step covers
Owners without a matching User go to a reconciliation queue for the customer's admin to provision. In parallel, we audit all Copper-attached Google Drive files, verify service account read access to the source Drive folders, and prepare the file transfer plan (destination Drive or Salesforce Files) before any CRM records are written to production.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Companies), then Leads and Contacts (with AccountId resolved for Contacts, People-to-Lead/Contact split applied), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Tasks, Events, EmailMessages (via Salesforce Bulk API 2.0 for large activity volumes), Notes, Projects (as Project__c custom object or grouped Tasks), Custom Fields (values mapped), and Tags (as multi-select picklists).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Google Drive files are migrated in parallel and re-linked to Salesforce ContentDocument records after the parent CRM records are in place.
Cutover, validation, and Workflow rebuild handoff
We freeze Copper writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We deliver the Workflow, bulk email sequence, and custom report inventory document to the customer's admin team with a rebuild guide for Salesforce Flow. We support a one-week hypercare window where we resolve reconciliation issues raised by the sales team. We do not rebuild Copper Workflows as Salesforce Flow inside the migration scope; that is a separate engagement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and engagement history depth. Copper's annual billing discount (approximately 26%) is forgone at migration; customers should align the Salesforce contract start date to avoid double-paying during the overlap window. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Copper to Salesforce →Why teams move from Copper to Salesforce
- Teams with growing sales complexity outgrow Copper's feature ceiling. Workflow automation, bulk email, custom reporting, and multi-currency are locked behind Professional ($59/seat/mo) and Business ($99/seat/mo) tiers. As seat counts climb, the effective per-user cost approaches Salesforce Professional ($80/user) without delivering the customization depth, pipeline control, or AppExchange ecosystem that growing sales organizations need once they have more than two or three distinct sales motions.
- Copper has no native custom object capability at any tier. Teams whose data model requires records beyond People, Companies, Opportunities, Leads, Tasks, and Projects (examples: Properties, Subscriptions, Vehicles, Cases) must either use custom fields as a workaround or move to a platform with a proper custom object model. Salesforce supports custom objects from the Professional tier ($80/user) without setup fees, which is a direct cost and capability upgrade for data-model-heavy teams.
- Copper is purpose-built for Google Workspace environments, which becomes a constraint when teams adopt Microsoft 365, Slack-based workflows, or require enterprise integrations (ERP connectors, CPQ, revenue intelligence). Salesforce's AppExchange with over 9,000 listings provides native or certified integrations for NetSuite, SAP, Microsoft 365, Google Workspace, DocuSign, Conga, and MuleSoft, removing the need for Zapier as a middleware for complex automation chains.
- Copper enforces hard contact limits at lower tiers (1,000 on Starter, 2,500 on Basic, 15,000 on Professional) that force an unplanned tier upgrade as the database grows. Salesforce Sales Cloud imposes no contact ceiling; cost scales with seat count rather than database size, which is more predictable for teams actively acquiring and nurturing prospects at scale.
- Activity history retention is a known pain point when teams leave Copper. Reviewers cite difficulty exporting the full engagement timeline (calls, emails, meetings, notes) in a structured format. Salesforce's Bulk API 2.0 supports high-volume activity migration that preserves the timeline as Salesforce-native Task, Event, and EmailMessage records, which is the primary reason teams commission a structured migration rather than a manual CSV export.
Questions, answered
Copper to Salesforce migration questions
How long does a Copper to Salesforce migration take?
Straightforward migrations under 15,000 People records, 3,000 Companies, and 2,000 Opportunities with no custom objects typically complete in four to six weeks. Migrations with large engagement histories (over 300,000 activity records), multiple pipelines, complex Company-to-Account hierarchy construction, or Projects mapped to a custom object move to ten to sixteen weeks because of Bulk API time, schema design scope, and the People-to-Lead/Contact reconciliation work. The Salesforce Sandbox validation step alone typically takes one to two weeks depending on internal review cycles.
Do Copper Workflows, bulk email sequences, and custom reports migrate to Salesforce?
No. Copper Workflows and Salesforce Flow are different automation models, and Copper's bulk email sequences (email series) have no direct Salesforce Sales Cloud equivalent. We do not migrate them as code. We deliver a written inventory of every active Copper Workflow, bulk email sequence, and custom report during discovery with a recommended Salesforce Flow rebuild path or Salesforce Sales Engagement cadence equivalent. The customer's admin or a Salesforce partner handles the rebuild post-migration. Reports similarly do not migrate; we recommend Salesforce Reports and Dashboards as the replacement, with the report mapping documented as a handoff artifact.
What happens to Copper's Google Drive-attached files during migration?
Files attached to Copper records live in the user's Google Drive, not in Copper's storage. We migrate the attachment metadata and coordinate Google Drive file transfer separately from the CRM record migration. We verify service account read access to the source Drive folders, transfer file ownership to a designated destination account or shared drive, and re-link file references as Salesforce Files (ContentDocument with ContentDocumentLink) in the destination org. Without this step, all attachment links become broken references and activity records lose their supporting documents.
Do we lose historical engagement data (calls, emails, meetings)?
No. We migrate the full engagement history through the Salesforce Bulk API 2.0 with parent-record resolution. Emails land as EmailMessage records linked to Tasks; calls land as Task with TaskSubtype=Call and CallDurationInSeconds preserved; meetings land as Event records with attendee resolution to migrated Contacts and Leads; tasks land as Salesforce Task. Activity timeline ordering is preserved by setting ActivityDate to the original Copper timestamp. We use exponential backoff on rate-limit responses to handle Copper's 180 req/min ceiling across large activity batches.
How do we handle the Copper contact limit during scoping?
Copper enforces contact limits at lower tiers (1,000 on Starter, 2,500 on Basic, 15,000 on Professional) that do not apply in Salesforce. We audit the total People count during discovery, compare it against the Copper plan ceiling to determine whether the customer has been approaching the limit, and confirm the Salesforce destination edition (no contact ceiling) resolves the constraint. If the customer is on Copper Starter or Basic with a People count near the limit, the migration to Salesforce is partly motivated by this ceiling and we document it as a business case driver.
Can FlitStack AI also migrate our Copper data to Salesforce Service Cloud if we also handle support?
Yes. If the destination Salesforce org includes Service Cloud, we can migrate Copper Tickets (if applicable) to Salesforce Case and Copper activity history to Case Activities. However, Service Cloud is licensed separately from Sales Cloud and requires a different org configuration. We scope this as a parallel engagement and confirm the Service Cloud license is in place before the Case migration phase begins. We do not rebuild Copper Workflows as Case Auto-Response Rules or Omni-Channel routing configurations inside the standard migration scope.
What happens to our Copper tag taxonomy after migration?
Copper's flat tag labels (applied to People, Companies, and Opportunities) migrate to Salesforce multi-select picklist fields on the respective objects. We audit the full tag vocabulary during discovery, confirm the value count is within Salesforce's picklist limits (500 values per field), create the picklist values in the destination org, and migrate tag assignments during the main record migration. Tags used for content classification rather than CRM segmentation migrate to a custom text field with an agreed naming convention.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → SuperOffice CRM to SalesforceMapping · history · rollbackZendesk Sell to SalesforceMapping · history · rollbackInsightly CRM to SalesforceMapping · history · rollbackConvertkit to SalesforceMapping · history · rollbackDaylite to SalesforceMapping · history · rollbackHousecall Pro to SalesforceMapping · history · rollback Copper to HubSpotMapping · history · rollbackCopper to Zoho CRMMapping · history · rollbackCopper to Dynamics 365Mapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Copper to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote