Migration Reference
Copper to HubSpot Migration
What actually transfers, what quietly does not, and what has to be rebuilt by hand.
We mapped Copper against HubSpot feature by feature: 62 features, 8 synced objects, 10 documented traps and 21 items that have to be rebuilt. The whole map is on this page, ungated.
The PDF is the same reference, formatted for a procurement file.
Get The Reference And The Calculator
The full Copper to HubSpot reference as a PDF, plus the Excel calculator we scope these migrations with: every one of the 62 features as a row, enter your counts, get hours.
Three files: the reference as a PDF, the same reference in Markdown for your AI tool, and the full Excel effort calculator.
Copper to HubSpot is a high migration, typically 3-14 weeks. Of the 62 features we mapped, 47 carry across as they are and 14 land with something lost: the 21 items nothing moves for you is what will actually set your timeline, not the sync.
Migration Scorecard
- Migration complexity
- High
- Typical timeline
- 3-14 weeks
- Recommended method
- Smart transfer
- Native sync
- Data sync, two way
- Smart transfer
- Supported
- HubSpot subscription
- Default field sync runs on the free HubSpot CRM; custom field mappings need Data Hub Starter at $15 a month per seat, and custom objects need Enterprise above that. Copper has its own floor on the other side too: the plan has to be Starter, Basic, Professional or Business, so confirm both tiers before assuming the free CRM alone is enough.
Feature parity across 62 capabilities
- Maps directly: 47 (76%)
- Maps partially: 14 (23%)
- No equivalent: 1 (2%)
8
Objects synced natively
10
Limitations and traps
21
Manual rebuild items
4
Source editions covered
Where this comes from: Our own research corpus, verified 2026-08-01, behind every number on this page.
The Eight Objects That Sync Natively
What the connector moves for you, and which way each one flows.
People
Two wayBecomes Contacts
Deduplication runs on email address above everything else, and any LinkedIn or Twitter profile link sitting on a Copper Person can be preserved as a custom property rather than dropped. Because Copper's deep Gmail integration tends to auto-create contacts from ordinary email traffic, audit that list for quality before it moves: a team working mostly from a phone rarely has time to clean up records the inbox created on its own.
Companies
Two wayBecomes Companies
Company name paired with domain drives deduplication here too, and since Copper auto-enriches company data straight from Google, that enrichment is worth verifying for accuracy before it becomes the record of truth in HubSpot rather than after.
Opportunities
Two wayBecomes Deals
Every Opportunity pipeline stage has to match its HubSpot deal stage label exactly, which means replicating the Copper pipeline configuration in HubSpot before a single deal syncs across. Historical time-in-stage detail can survive the move through a migration tool, but the native sync alone will not carry it.
Leads
Two wayBecomes Contacts
Leads map to HubSpot Contacts too, but on a separate path from the People mapping above it, documented in HubSpot's Smart Transfer data sync object mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Notes
Two wayBecomes Notes
Notes are one of the more straightforward transfers on this list, supported directly per HubSpot's Smart Transfer data sync object mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Phone Call Activities
Two wayBecomes Calls
Call activity carries across as well, confirmed in the same HubSpot Smart Transfer data sync object mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Tasks
Two wayBecomes Tasks
Tasks transfer too, listed among the supported objects in HubSpot's own Smart Transfer data sync mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Meeting Activities
Two wayBecomes Meetings
Meeting activity is supported in the same transfer, per HubSpot's Smart Transfer data sync object mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Ten Things the Sync Does Not Tell You
Each one is documented, and each one has ended a migration in a bad week.
Only Contacts, Companies, and Deals Sync via Native Data Sync
Leads, tasks, activities, Projects and everything else Copper tracks stay out of the native HubSpot Data Sync integration entirely: only People, Companies and Opportunities cross automatically, arriving on the HubSpot side as Contacts, Companies and Deals.
Workaround: Everything the native sync leaves behind still has a path across: Smart Transfer handles a one-time migration, CSV export and import covers the simpler cases, and a third-party tool such as MigrateMyCRM or Trujay picks up the rest.
Activities (calls, Meetings) Do Not Sync via Data Sync
Every phone call, meeting and logged interaction Copper tracks as an activity has to be migrated on its own path: none of it moves through the native Data Sync.
Workaround: Smart Transfer, a third-party migration tool or a custom API script are the three routes across, and once notes, calls and meeting logs land, they can be rebuilt as HubSpot Engagements on the record's timeline rather than left behind.
Tasks and Projects Do Not Sync via Data Sync
Tasks and Projects both sit outside the native Data Sync, and Projects specifically has no direct match on the HubSpot side: Copper's project management functionality is a shape HubSpot's core CRM simply does not carry.
Workaround: Decide where Projects should land: HubSpot Deals or Custom Objects are both workable homes for it. Bring Tasks across separately, either through a CSV import or by rebuilding them directly as HubSpot Tasks.
Gmail Email History Requires Special Handling
Because Copper stores email history the way Gmail does rather than the way a standalone CRM would, that history needs deliberate extraction and rebuilding as HubSpot timeline engagements to survive the move at all, and the metadata carries a genuine risk of date-stamp corruption in transit.
Workaround: A specialised migration tool built to read Copper's own email metadata is what recreates that interaction history intact as HubSpot Engagements on the timeline; a generic export rarely captures the same detail.
Custom Objects Not Supported by Smart Transfer
Whatever custom object types or custom activity types exist in Copper, Smart Transfer will not carry any of them across: that transfer simply is not supported, and each one needs handling on its own.
Workaround: A CSV export and import, or a custom API build, is the only way through, and HubSpot Enterprise is a prerequisite for custom objects to exist on the receiving end at all, worth confirming before the tier is chosen rather than after.
Copper Leads Map to Contacts With Lifecycle Stage
Leads live as their own object in Copper, separate from People, and that object does not sync through Data Sync at all: each one has to be migrated as a HubSpot Contact carrying a lifecycle stage tag that marks it apart from an already-converted contact.
Workaround: Export the Leads out of Copper and bring them into HubSpot as Contacts, with Lifecycle Stage set to 'Lead' on the way in.
Some Historical Data Types Are Restricted by HubSpot
Certain historical data types run into HubSpot's own restrictions on automated import, complex workflows and proprietary activity history among them, so no context should be assumed to survive the move without some genuinely creative data-structuring on the way in.
Workaround: Bring in migration specialists, or use HubSpot custom objects to architect a data structure that actually fits how the sales process runs here rather than forcing it into the nearest standard field.
Owner Reconciliation Depends on Email Matching
Ownership of a record depends entirely on matching a Copper user's email address to a HubSpot one, so any Copper user without a corresponding HubSpot address loses that ownership assignment on the way across, a real risk where the same person sits under more than one Google Workspace domain across a multi-entity group.
Workaround: Create every HubSpot user with a matching email address before migration starts, and build an explicit mapping table rather than trusting the match to happen on its own, checking it against whichever address each person actually uses day to day, not just the one on file.
Copper Unique Field Types Require Conversion
Relationship types, connect fields and custom dropdowns are all Copper field types with no guaranteed HubSpot property to land in, so a native schema mapping exercise is what converts each one into something HubSpot can actually hold.
Workaround: Map every Copper field type to a compatible HubSpot property during the planning phase, before a single record moves, and build custom properties wherever the existing set falls short.
Free Tier Limited to Default Field Mappings Only
The free tier of HubSpot Data Sync stops at default and standard fields: mapping a custom field at all requires a Data Hub Starter subscription, not a setting to switch on within the free product.
Workaround: Data Hub Starter, at $15 a month per seat, is what turns custom field mapping on; put that line in the original budget rather than discovering it once the free tier's limits are already being hit.
One Copper Feature HubSpot Cannot Replace
No workaround closes these. Each one is a capability you would be giving up, so decide who in the business can live without it before you commit to a date.
Suggested Contacts
HubSpot will not proactively flag a frequently-emailed address that is not yet in the CRM the way Copper does: adding that person as a contact is a manual step through the Gmail extension rather than a suggestion that surfaces on its own.
The 21 Items That Get Rebuilt by Hand
This is the list that separates a quote that holds from one that does not.
Data And Objects
Copper Projects
Projects, complete with tasks, milestones and linked records, maps onto HubSpot's own projects object, which carries pipelines, stages, board and Gantt views, templates and tasks on every plan. Budgets and resource allocation are where that mapping stops, so confirm those are not something the business actually depends on before assuming parity; for the lightest cases, Deals or Tickets remain workable alternatives.
HubSpot: Deals, Tickets, or Custom Objects
Look carefully at how Projects is actually being used before settling on a HubSpot mapping: where it is tracking delivery after a sale closes, Service Hub Tickets or a dedicated project management integration is usually the better fit than forcing it into the projects object.
Copper Leads (separate From People)
Leads sit apart from People as their own object in Copper, and migrating them means landing each one as a HubSpot Contact carrying the right lifecycle stage tag.
HubSpot: Contacts with Lifecycle Stage = Lead
Export from Copper and bring the records into HubSpot with the lifecycle stage set correctly on import, rather than fixing it afterwards record by record.
Relationship Types and Linked Records
Relationship types, the links Copper draws between contacts and companies or between two contacts, have to be rebuilt using HubSpot associations instead.
HubSpot: HubSpot Association Labels
Association labels sit behind a specific plan tier, so pull the actual requirement from the feature table before designing the relationship structure around them.
Tags
Tags need replicating in HubSpot by some other mechanism, since nothing there maps one-to-one onto Copper's tag system.
HubSpot: HubSpot multi-select properties or static lists
Decide deliberately whether each tag becomes a property, a static list membership, or both, rather than defaulting to whichever is fastest to set up.
Automation
Copper Automations
Nothing about Copper's automation rules and triggers carries its own logic across: an automated engine cannot migrate business logic, so every rule gets rebuilt from nothing inside HubSpot, and migration providers typically do that translation and rebuild by hand rather than any tool doing it automatically.
HubSpot: HubSpot Workflows
Document every active Copper automation before migration starts, since nothing will remind you what used to run once it is gone. HubSpot's workflow engine is significantly more capable than Copper's, so treat the rebuild as room to improve rather than a plain like-for-like copy.
Email Templates
Every Copper email template, built as it is around Gmail, has to be recreated directly in HubSpot rather than carried across.
HubSpot: HubSpot Email Templates and Snippets
No automatic migration path exists for templates: a Gmail-based one needs rebuilding by hand inside HubSpot's own template builder, worth budgeting for properly where a bilingual team is involved, since an Arabic version needs its own right-to-left layout rather than an English template with the text swapped in.
Activity Sets (task Templates)
Activity sets, the repeatable task sequences Copper runs, need recreating too: either as HubSpot task templates or as workflow-triggered sequences that spawn the same tasks automatically.
HubSpot: HubSpot Task Queues / Workflow-triggered tasks
Auto-enrichment From Google
Copper's automatic enrichment of contact and company data from Google does not carry over as a feature; something has to replace it once the migration is done.
HubSpot: HubSpot Breeze Intelligence (paid add-on)
HubSpot Breeze Intelligence is the direct replacement, but it runs on a per-credit charge rather than the enrichment Copper simply included, a genuine new cost line to budget for rather than a straight swap.
Reporting
Pipeline Reports and Dashboards
Nothing about a Copper pipeline report or dashboard configuration transfers: every one of them gets rebuilt from nothing inside HubSpot.
HubSpot: HubSpot Custom Reports and Dashboards
HubSpot's reporting genuinely goes further than Copper's did, so use the rebuild as an opportunity to build a better report rather than reproducing the old one exactly.
Revenue Forecasting
Whatever forecasting setup existed in Copper has to be reconfigured from scratch inside HubSpot.
HubSpot: HubSpot Forecasting Tool (Sales Hub)
Activity Reports
Call counts, email metrics and meeting tracking, the activity-based reports Copper ran, all need rebuilding on the HubSpot side.
HubSpot: HubSpot Activity Reports
Sales And Marketing Config
Deal Pipelines and Stages
Pipeline and stage configuration has to exist in HubSpot, replicated from Copper, before a single record of deal data is allowed to migrate.
HubSpot: HubSpot Deal Pipelines
Get this configured before deal data migrates, not after, or the stage values arriving from Copper will have nothing correct to land against.
Web Forms
Any web form currently running through Copper has to be replaced with a HubSpot form; nothing carries the old one across automatically.
HubSpot: HubSpot Forms
Update every website embed code to point at the new HubSpot forms once they are live, so nothing on the site keeps quietly submitting to the old ones.
Gmail Sidebar / Chrome Extension
The Gmail sidebar and Chrome extension Copper's users actually work from all day has to be replaced with HubSpot's own Gmail extension, which covers email tracking, templates, meeting scheduling and the CRM sidebar in its place.
HubSpot: HubSpot Sales Extension for Gmail
The critical difference sits in how logging actually happens: Copper logs a Gmail interaction almost without anyone noticing, while HubSpot only logs an email sent through the CRM or through the sales extension with the 'Log' checkbox ticked, an extra deliberate step that a team working mostly from a phone is the most likely to skip.
Google Calendar Integration
Copper's native Google Calendar integration has to give way to HubSpot's own calendar sync and Meetings tool.
HubSpot: HubSpot Google Calendar Integration / Meetings Tool
HubSpot does support Google Calendar sync, but the day-to-day experience of using it differs from what Copper's native integration offered, worth setting expectations on before go-live rather than after.
Google Drive Integration
File linking and management through Google Drive, native to Copper, needs reconfiguring on the HubSpot side instead.
HubSpot: HubSpot Google Drive Integration
HubSpot's own Google Drive integration covers document management here, so the capability survives the move even if the exact setup does not carry across automatically.
Users And Permissions
User Roles and Permissions
Copper's permission structure does not transfer either: it has to be recreated from scratch directly inside HubSpot.
HubSpot: HubSpot Teams, Roles, and Permission Sets
HubSpot's permission model actually offers more granularity than Copper's did, worth using deliberately rather than reproducing the coarser structure that existed before, especially where a multi-entity Gulf group needs one country hub kept out of another entity's records.
Team Structure
Team hierarchy carries the same requirement: whatever structure existed in Copper needs recreating inside HubSpot rather than importing.
HubSpot: HubSpot Teams
Integrations
Google Workspace Native Integration Replacement
Gmail, Calendar, Drive and Contacts are where Copper actually lives, and that is by design: a team that chose Copper chose it specifically so nobody had to leave the inbox to work the pipeline. Moving to HubSpot means replacing that native embedding with HubSpot's own Google integrations, which do the job but sit a step further from the inbox than Copper offered, and that step is the real question behind this migration: whether a sales team that has only ever worked from Gmail, often from a phone rather than a desktop, will actually open a separate system once the sync stops holding the two together.
HubSpot: HubSpot Gmail Extension + Google Calendar Sync + Google Drive Integration
This is usually where a Copper migration meets the most resistance, so weight the training accordingly: focus it squarely on the new Gmail-to-HubSpot workflow rather than treating it as one module among several.
Third-party Integrations
Every integration and connected app currently plugged into Copper needs evaluating on its own, then replacing with whatever the HubSpot App Marketplace offers in its place.
HubSpot: HubSpot App Marketplace integrations
HubSpot's marketplace runs to over 1,500 apps, a considerably wider ecosystem than Copper's own integration list, so most of what needs replacing usually has somewhere to land.
Zapier Automations Involving Copper
Any Zapier or Make automation that currently references Copper needs updating to fire HubSpot triggers and actions instead.
HubSpot: Native HubSpot Workflows or updated Zapier/Make automations
The Sequence
Sync First, Then Migrate
Order is the content here. These steps form a dependency chain, and running them out of sequence is a documented way this kind of migration fails.
- 1
Audit the Copper Data
review People, Companies, Opportunities, Leads, Projects, Tasks and Activities together for data quality before anything is scheduled to move
- 2
Clean the Data
remove duplicates, fix inconsistencies and validate email addresses, since Copper's Gmail integration may well have auto-created a fair number of low-quality contacts on its own
- 3
Document Every Active Automation, Email Template, Activity Set, Report Configuration and Google Workspace Workflow Currently in Use, Before the Audit Is Called Finished
Document every active automation, email template, activity set, report configuration and Google Workspace workflow currently in use, before the audit is called finished
- 4
Build a Mapping Workbook That Carries Every Copper Object and Field Across to Its HubSpot Equivalent
Build a mapping workbook that carries every Copper object and field across to its HubSpot equivalent
- 5
Decide How Projects Should Land, HubSpot Deals, Tickets or Custom Objects Are All Workable, Before Configuration Begins Rather Than Partway Through It
Decide how Projects should land, HubSpot Deals, Tickets or Custom Objects are all workable, before configuration begins rather than partway through it
- 6
Configure HubSpot Itself
set up the deal pipelines and stages, create the custom properties, and configure user accounts with emails that actually match Copper's
- 7
Install Copper Data Sync From the HubSpot Marketplace and Start Smart Transfer Running
Install Copper Data Sync from the HubSpot Marketplace and start Smart Transfer running
- 8
Let Smart Transfer Run Its Own Audit
it creates properties and pipelines automatically based on how Copper was already configured
- 9
Choose the Objects and Data Types the Transfer Will Carry, Then Review and Adjust the Field Mappings It Proposes
Choose the objects and data types the transfer will carry, then review and adjust the field mappings it proposes
- 10
Run Smart Transfer to Sync People, Companies and Opportunities Across
Run Smart Transfer to sync People, Companies and Opportunities across
- 11
Migrate Leads, Tasks, Notes and Activities on a Separate Track From the Main Sync, Bringing Leads Across as Contacts Carrying a Lifecycle Stage, by CSV or a Migration Tool
Migrate Leads, Tasks, Notes and Activities on a separate track from the main sync, bringing Leads across as Contacts carrying a lifecycle stage, by CSV or a migration tool
- 12
Migrate the Projects Data Itself Into Whichever HubSpot Object Type Was Chosen for It
Migrate the Projects data itself into whichever HubSpot object type was chosen for it
- 13
Handle the Email History Separately
specialised tools are what preserve Gmail activity metadata as HubSpot timeline engagements rather than losing it in a generic export
- 14
Install and Configure the HubSpot Gmail Extension for Every User, Then Train the Team on the New Email Logging Workflow Specifically, Since This Is the Step Most Often Skipped on a Phone Rather Than a Desktop
Install and configure the HubSpot Gmail Extension for every user, then train the team on the new email logging workflow specifically, since this is the step most often skipped on a phone rather than a desktop
- 15
Rebuild the Automations, Reports, Dashboards and Email Templates Directly Inside HubSpot
Rebuild the automations, reports, dashboards and email templates directly inside HubSpot
- 16
Validate the Data
spot-check records, verify associations, test the automations and confirm that email logging is actually working as expected
- 17
Train the Team With Real Weight Given to the Gmail-to-HubSpot Workflow Changes Specifically, Then Go Live
Train the team with real weight given to the Gmail-to-HubSpot workflow changes specifically, then go live
Typically 3-14 weeks end to end, depending on how much of the source configuration is actually in use.
Effort Estimator
How Big Is This Migration?
A handful of questions, no sign-up required. The ranges come from the research above: every feature we mapped carries an effort figure, and this totals the ones that apply to your instance.
Estimated Effort
Answer a couple of questions and an hours range appears here.
Built from our research on 62 Copper features. It is a range, not a quote.
A planning range, not a quote. It is delivery effort only, with no project management line. What moves it most in practice is data quality.
What Goes Wrong Most Often
The failures that show up again and again, in roughly the order they bite.
Gmail Logging Is Where the Biggest Behavioural Change Sits
Copper logged Gmail interactions on its own with no user action required, while HubSpot needs the sales extension installed and a deliberate opt-in on each email
Contacts Auto-created From Gmail Traffic Are Worth a Proper Audit Before Migration, Since Copper's Own Auto-creation Habit Can Leave a Real Number of Low-quality Records Sitting in the Data
Contacts auto-created from Gmail traffic are worth a proper audit before migration, since Copper's own auto-creation habit can leave a real number of low-quality records sitting in the data
Workflow Disruption Around Google Workspace Is Worth Planning for Directly
anyone who has only ever worked from Copper's Gmail sidebar is going to feel this migration as a genuine change to how the working day runs, not a cosmetic one
Projects Maps Onto HubSpot's Own Projects Object Well Enough for Pipelines, Stages, Board and Gantt Views and Tasks, but Budgets and Resource Allocation Are Where the Mapping Stops, So Confirm Those Genuinely Are Not Depended on Before Assuming the Fit Is Complete
Projects maps onto HubSpot's own projects object well enough for pipelines, stages, board and Gantt views and tasks, but budgets and resource allocation are where the mapping stops, so confirm those genuinely are not depended on before assuming the fit is complete
Date-stamp Corruption Is a Real Risk in the Email History Migration Specifically
Gmail-integrated activity metadata can come across damaged if the transfer is not handled with real care
Owner Reconciliation Rests Entirely on Email-based User Matching, So Every HubSpot User Needs Creating With a Matching Email Address Before Migration, Not Worked Out Afterwards From Whatever Records Fail to Attach
Owner reconciliation rests entirely on email-based user matching, so every HubSpot user needs creating with a matching email address before migration, not worked out afterwards from whatever records fail to attach
Relationship Types and Connect Fields, Copper's Own Field Types, May Simply Have No HubSpot Equivalent to Map to at All
Relationship types and connect fields, Copper's own field types, may simply have no HubSpot equivalent to map to at all
HubSpot's Own Restrictions on Historical Activity Imports May Call for Genuinely Creative Data-structuring to Work Around, Rather Than a Standard Import Doing the Job Unassisted
HubSpot's own restrictions on historical activity imports may call for genuinely creative data-structuring to work around, rather than a standard import doing the job unassisted
Auto-enrichment From Google, Something Copper Simply Included, Stops the Moment the Migration Happens, So HubSpot Breeze Intelligence Needs a Deliberate Decision as Its Replacement Rather Than an Assumption That Enrichment Just Continues
Auto-enrichment from Google, something Copper simply included, stops the moment the migration happens, so HubSpot Breeze Intelligence needs a deliberate decision as its replacement rather than an assumption that enrichment just continues
Questions
Copper To HubSpot, Answered
Yes. Data sync, two way, covering 8 objects. Smart transfer is supported. What it will not do is rebuild your configuration: that is the 21 items below.
Typically 3-14 weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database on its own will not extend the timeline.
Of 62 features we mapped, 47 (76%) carry across directly and 14 (23%) map partially, meaning something is lost or reshaped along the way. 1 has no HubSpot equivalent at any tier, worth raising before sign-off rather than after.
21 items have to be rebuilt by hand, and 10 documented limitations are not surfaced by the connector at all. Both lists are on this page, in full, for whoever is scoping the work.
Default field sync runs on the free HubSpot CRM; custom field mappings need Data Hub Starter at $15 a month per seat, and custom objects need Enterprise above that. Copper has its own floor on the other side too: the plan has to be Starter, Basic, Professional or Business, so confirm both tiers before assuming the free CRM alone is enough.
1: Suggested Contacts. If your team depends on one of these, settle it before you sign rather than discovering it at cutover, when the alternative is a custom build.
Only in one direction. The sync is not bidirectional here, so running both systems means choosing a system of record up front and accepting drift in the other.
Ready to Get Started?
Plan Your Migration
Tell us which platform you are leaving, how much of it is custom, and when you need to be live in HubSpot. We will tell you what transfers directly, what needs rebuilding, and how long the move actually takes.