Migrate your Copper data
Google Workspace-native CRM built around Gmail and Google Drive, targeting small-to-mid teams that want relationship tracking without leaving the tools they already use.
In its favor
Why people choose Copper
The signal that keeps Copper on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Google Workspace tight integration lets teams stay inside Gmail and Google Drive without switching context, reducing adoption friction for small sales teams already committed to Google's ecosystem.
Contact and pipeline visibility in a clean, uncluttered interface that new users can navigate without formal training or extensive onboarding documentation.
Automatic activity capture from email threads means Copper builds an engagement history without requiring salespeople to manually log every touchpoint.
Per-seat pricing is straightforward and predictable, with annual billing cutting cost by ~26% compared to monthly payments across all four tiers.
Zapier integration extends Copper beyond Google's own toolset, allowing teams to connect to other apps without custom API development.
Workflow automation, bulk email, and advanced reporting are gated behind Professional and Business tiers, pushing growing teams toward unexpected cost increases as their seat count and feature needs both climb.
Teams report the platform feels underpowered for complex sales motions, with limited customisation compared to Salesforce or HubSpot once use cases move beyond simple pipeline tracking.
Some users report that the interface is intuitive for basic tasks but becomes less intuitive when navigating advanced configuration, custom fields, or pipeline customisation.
The AI-assisted features such as email rewriting are only available on higher tiers and reviewers note they feel underdeveloped compared to AI capabilities offered by competitors.
Reasons to switch
Why people leave Copper
The recurring reasons buyers give for replacing Copper. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Copper fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Copper pricing overview
Copper uses per-seat, per-month pricing across four tiers. Annual billing provides approximately 26% savings versus monthly. The main cost driver is seat count and tier; the Starter cap of 1,000 contacts can force a tier upgrade as a team's database grows, which also unlocks previously unavailable features like workflows and bulk email.
Starter
Tier 1 of 4
$9/seat/month (annual) or $12/seat/month (monthly)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Copper's schedule — see our quote-based pricing →
What gets migrated
Copper object support
Object-by-object support for Copper migrations. Per-pair details surface during scoping.
People
Fully supportedPeople is Copper's primary contact object, storing name, email, phone, address, and related company. We migrate People records 1:1 with standard field mapping; no custom mapping required for the core schema.
Companies
Fully supportedCompanies represent business accounts and are related to People records. We preserve the People-to-Company linkage during migration, maintaining referential integrity across both objects.
Opportunities
Fully supportedOpportunities drive Copper's pipeline tracking with customizable stages and monetary values. We migrate open Opportunities fully and map their Pipeline Stage to the destination's equivalent stage concept.
Leads
Mapping requiredLeads is a separate object from People in Copper. We handle the distinction by mapping Lead records into the destination's lead or contact object and preserving Lead_Status as a custom property where the target supports it.
Pipelines
Mapping requiredPipelines define the stages Opportunities flow through. Copper allows multiple pipelines on higher tiers. We preserve stage names, order, and stage-specific probability data, though destination CRMs may require manual stage recreation if the pipeline structure differs significantly.
Tasks
Fully supportedTasks are Copper's basic action items with due dates, assignees, and related records. We migrate Tasks including their status, due date, and association to People, Companies, or Opportunities.
Projects
Mapping requiredProjects are a lightweight project-management object in Copper. We migrate Projects with their associated Tasks, though destination CRMs without a native project object may require mapping to a Tasks-based structure.
Activities
Mapping requiredActivities log emails, calls, meetings, and notes linked to People, Companies, or Opportunities. We preserve activity type, date, and notes; the destination's activity model may require mapping to a different engagement or interaction object.
Custom Fields
Mapping requiredCustom fields are available on People, Companies, Opportunities, Leads, Projects, and Tasks. We inspect the Custom Field Definitions API to enumerate all custom fields, then map values to equivalent destination fields or create new ones at import time.
Tags
Mapping requiredTags in Copper are flat labels applied to People, Companies, and Opportunities. We migrate tags as-is and map them to the destination's tagging or label mechanism.
Attachments
Mapping requiredFile attachments are stored in Google Drive when linked to Copper records. We migrate attachment metadata and re-link files to the destination CRM, noting that the actual file ownership and permissions in Google Drive may need manual verification post-migration.
| Object | Support | Notes |
|---|---|---|
| People | Fully supported | People is Copper's primary contact object, storing name, email, phone, address, and related company. We migrate People records 1:1 with standard field mapping; no custom mapping required for the core schema. |
| Companies | Fully supported | Companies represent business accounts and are related to People records. We preserve the People-to-Company linkage during migration, maintaining referential integrity across both objects. |
| Opportunities | Fully supported | Opportunities drive Copper's pipeline tracking with customizable stages and monetary values. We migrate open Opportunities fully and map their Pipeline Stage to the destination's equivalent stage concept. |
| Leads | Mapping required | Leads is a separate object from People in Copper. We handle the distinction by mapping Lead records into the destination's lead or contact object and preserving Lead_Status as a custom property where the target supports it. |
| Pipelines | Mapping required | Pipelines define the stages Opportunities flow through. Copper allows multiple pipelines on higher tiers. We preserve stage names, order, and stage-specific probability data, though destination CRMs may require manual stage recreation if the pipeline structure differs significantly. |
| Tasks | Fully supported | Tasks are Copper's basic action items with due dates, assignees, and related records. We migrate Tasks including their status, due date, and association to People, Companies, or Opportunities. |
| Projects | Mapping required | Projects are a lightweight project-management object in Copper. We migrate Projects with their associated Tasks, though destination CRMs without a native project object may require mapping to a Tasks-based structure. |
| Activities | Mapping required | Activities log emails, calls, meetings, and notes linked to People, Companies, or Opportunities. We preserve activity type, date, and notes; the destination's activity model may require mapping to a different engagement or interaction object. |
| Custom Fields | Mapping required | Custom fields are available on People, Companies, Opportunities, Leads, Projects, and Tasks. We inspect the Custom Field Definitions API to enumerate all custom fields, then map values to equivalent destination fields or create new ones at import time. |
| Tags | Mapping required | Tags in Copper are flat labels applied to People, Companies, and Opportunities. We migrate tags as-is and map them to the destination's tagging or label mechanism. |
| Attachments | Mapping required | File attachments are stored in Google Drive when linked to Copper records. We migrate attachment metadata and re-link files to the destination CRM, noting that the actual file ownership and permissions in Google Drive may need manual verification post-migration. |
Gotchas
What to watch for in Copper migrations
Issues we've hit on past Copper migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Contact limit enforcement varies by tier and can block imports
API rate limit of 180 requests per minute requires throttled extraction
Workflows, bulk email, and custom reports are tier-gated features
Attachment files live in Google Drive, not Copper's own storage
| Severity | Issue |
|---|---|
| High | Contact limit enforcement varies by tier and can block imports |
| High | API rate limit of 180 requests per minute requires throttled extraction |
| Medium | Workflows, bulk email, and custom reports are tier-gated features |
| Medium | Attachment files live in Google Drive, not Copper's own storage |
Leaving Copper?
Where Copper customers move next
12 destinations Copper can migrate to.
How a Copper migration works
Four steps, Copper-specific
Connect
API key passed via three headers: X-PW-AccessToken (the key), X-PW-Application set to developer_api, and X-PW-UserEmail with the owner's email. OAuth 2.0 (Authorization Code Grant) is also supported for third-party integrations and tokens currently do not expire. into Copper. Scopes limited to read-only on the data we move.
Map
We translate Copper-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Copper quirks before production.
Migrate
Full migration with Copper rate-limit handling. Rollback available throughout.
FAQ
Copper migration FAQ
Answers to the questions buyers ask most during Copper migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Copper migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Copper.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Copper setup and destination — written quote back within a business day.