Agency Migration Guide
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 to send to a client.
Get The Guide And The Calculator
The full Copper to HubSpot reference as a branded PDF you can send straight to a client, 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 guide as a PDF, the same guide unbranded in Markdown for your AI tool, and the full Excel effort calculator.
Copper to HubSpot is a high migration, typically 3-14 weeks. Of 62 features we mapped, 47 carry across as they are and 14 land with something lost. The work is not moving records: it is the 21 items nothing moves for you.
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
- HubSpot Free CRM for default field sync; Data Hub (Data Hub) Starter ($15/mo/seat) for custom field mappings; Enterprise for custom objects. Copper requires Starter, Basic, Professional, or Business plan.
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
Email address is the primary deduplication key. Copper People with social profile links (LinkedIn, Twitter) can have those preserved as custom properties. Copper's deep Gmail integration means many contacts may have been auto-created from email interactions - audit for quality before migration.
Companies
Two wayBecomes Companies
Company name and domain are used for deduplication. Copper auto-enriches company data from Google - verify this data is accurate before migration.
Opportunities
Two wayBecomes Deals
Opportunity pipeline stages must match HubSpot deal stage labels exactly. Copper pipeline configuration should be replicated in HubSpot before deal sync. Historical time-in-stage data can be preserved through migration tools but not via native sync.
Leads
Two wayBecomes Contacts
Copper Leads map to HubSpot Contacts, distinct from the People mapping. 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
Note transfer is supported. Documented in 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 transfer is supported. Documented in HubSpot's Smart Transfer data sync object mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Tasks
Two wayBecomes Tasks
Task transfer is supported. Documented in HubSpot's Smart Transfer data sync object mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Meeting Activities
Two wayBecomes Meetings
Meeting activity transfer is supported. Documented in 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
The native HubSpot Data Sync integration with Copper only syncs People (Contacts), Companies, and Opportunities (Deals). Leads, tasks, activities, projects, and other objects do NOT sync through the native integration.
Workaround: Use Smart Transfer for one-time data migration, CSV export/import, or third-party migration tools (MigrateMyCRM, Trujay) for additional objects.
Activities (calls, Meetings) Do Not Sync via Data Sync
Copper activities including phone calls, meetings, and logged interactions do not transfer through the native Data Sync. These must be migrated separately.
Workaround: Use Smart Transfer for one-time migration, third-party migration tools, or custom API scripts. Notes, calls, and meeting logs can be reconstructed as HubSpot Engagements.
Tasks and Projects Do Not Sync via Data Sync
Copper Tasks and Projects are not part of the native Data Sync. Copper's project management functionality doesn't have a direct equivalent in HubSpot CRM.
Workaround: Copper Projects can be migrated as HubSpot Deals or Custom Objects. Tasks can be imported via CSV or recreated as HubSpot Tasks.
Gmail Email History Requires Special Handling
Copper's deep Gmail integration means email history is stored differently than in other CRMs. Gmail-integrated activity metadata needs to be extracted and replicated as HubSpot timeline engagements to preserve full interaction history. Date-stamp corruption is a risk during email history migration.
Workaround: Use specialized migration tools that capture Copper-specific email metadata and recreate the full interaction history as HubSpot Engagements on the timeline.
Custom Objects Not Supported by Smart Transfer
The transfer of custom objects is not supported by HubSpot Smart Transfer. Copper custom object types and custom activity types require separate handling.
Workaround: Migrate via CSV export/import or custom API. Requires HubSpot Enterprise tier for custom objects.
Copper Leads Map to Contacts With Lifecycle Stage
Copper has a separate Leads object that doesn't directly sync via Data Sync. Leads must be migrated as HubSpot Contacts with appropriate lifecycle stage tags to distinguish them from converted contacts.
Workaround: Export Copper Leads and import as HubSpot Contacts with Lifecycle Stage set to 'Lead'.
Some Historical Data Types Are Restricted by HubSpot
HubSpot restricts automated imports for certain historical data types, particularly around complex workflows and proprietary activity history. Creative data-structuring may be needed to ensure no context is lost.
Workaround: Work with migration specialists or use HubSpot custom objects to architect data structures that match your specific sales motion.
Owner Reconciliation Depends on Email Matching
Record ownership mapping between Copper and HubSpot depends on email-based user matching. If Copper users don't have matching email addresses in HubSpot, records may lose ownership assignment.
Workaround: Create all HubSpot users with matching email addresses before migration. Build explicit user mapping table.
Copper Unique Field Types Require Conversion
Copper has unique field types (relationship types, connect fields, custom dropdowns) that may not have direct HubSpot property equivalents. Native schema mapping is needed to convert these into compatible HubSpot Property types.
Workaround: Map Copper field types to compatible HubSpot property types during the planning phase. Create custom properties as needed.
Free Tier Limited to Default Field Mappings Only
The free HubSpot Data Sync only syncs default/standard fields. Custom field mappings require a Data Hub (Data Hub) Starter subscription.
Workaround: Upgrade to Data Hub Starter ($15/month/seat) for custom field mapping capabilities.
One Copper Features HubSpot Cannot Replace
Not a workaround away. If a client depends on one of these, it belongs in the conversation before the contract.
Suggested Contacts
HubSpot does not proactively suggest contact creation from email interactions. Users add contacts manually via the Gmail extension.
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
Copper's project management module (Projects with tasks, milestones, and linked records) maps onto the HubSpot projects object, which carries pipelines, stages, board and Gantt views, templates and tasks on all plans. Budgets and resource allocation do not map, so confirm the client does not depend on them; Deals or Tickets remain alternatives for the lightest cases.
Copper Leads (separate From People)
Copper's Leads object is separate from People and must be migrated as HubSpot Contacts with lifecycle stage tagging.
Relationship Types and Linked Records
Copper's relationship types (linking contacts to companies or contacts to contacts) need to be recreated using HubSpot associations.
Tags
Copper's tag system needs to be replicated in HubSpot. Tags don't have a direct 1:1 equivalent in HubSpot.
Automation
Copper Automations
All Copper automation rules and triggers must be rebuilt from scratch in HubSpot. Automated engines cannot migrate business logic. Migration providers typically manually translate and rebuild automations natively in HubSpot.
Email Templates
Copper email templates (integrated with Gmail) must be recreated in HubSpot.
Activity Sets (task Templates)
Copper's activity sets (repeatable task sequences) must be recreated as HubSpot task templates or workflow-triggered task creation sequences.
Auto-enrichment From Google
Copper automatically enriches contact and company data from Google. This functionality needs to be replaced.
Reporting
Pipeline Reports and Dashboards
All Copper pipeline reports and dashboard configurations must be rebuilt in HubSpot. Report configurations do not transfer.
Revenue Forecasting
Copper's forecasting setup must be reconfigured in HubSpot.
Activity Reports
Copper's activity-based reports (call counts, email metrics, meeting tracking) must be rebuilt.
Sales And Marketing Config
Deal Pipelines and Stages
Copper pipeline and stage configuration must be replicated in HubSpot before data migration.
Web Forms
Any Copper web forms must be replaced with HubSpot forms.
Gmail Sidebar / Chrome Extension
Copper's Gmail sidebar and Chrome extension must be replaced with HubSpot's Gmail extension for email tracking, templates, meeting scheduling, and CRM sidebar functionality.
Google Calendar Integration
Copper's native Google Calendar integration must be replaced with HubSpot's calendar sync.
Google Drive Integration
Copper's native Google Drive file linking and management must be reconfigured with HubSpot.
Users And Permissions
User Roles and Permissions
Copper's permission structure must be recreated in HubSpot.
Team Structure
Copper team hierarchy must be recreated in HubSpot.
Integrations
Google Workspace Native Integration Replacement
Copper is deeply embedded in Google Workspace (Gmail, Calendar, Drive, Contacts). Moving to HubSpot means replacing this native Google integration with HubSpot's Google integrations, which are functional but not as seamlessly embedded. This is the single biggest workflow change for users.
Third-party Integrations
All Copper integrations and connected apps must be evaluated and replaced with HubSpot App Marketplace equivalents.
Zapier Automations Involving Copper
Any Zapier or Make automations referencing Copper must be updated to use HubSpot triggers and actions.
The Sequence
Sync First, Then Migrate
Order is the content here. These are a dependency chain, and running them out of order is a documented way these migrations fail.
- 1
Audit Copper Data
review People, Companies, Opportunities, Leads, Projects, Tasks, and Activities for data quality
- 2
Clean Data
remove duplicates, fix inconsistencies, validate email addresses (Copper may have auto-created low-quality contacts from Gmail)
- 3
Document All Active Automations, Email Templates, Activity Sets, Report Configurations, and Google Workspace Workflows
Document all active automations, email templates, activity sets, report configurations, and Google Workspace workflows
- 4
Map Copper Objects and Fields to HubSpot Equivalents in a Mapping Workbook
Map Copper objects and fields to HubSpot equivalents in a mapping workbook
- 5
Decide on Copper Projects Handling
map to HubSpot Deals, Tickets, or Custom Objects
- 6
Configure HubSpot
set up deal pipelines/stages, create custom properties, configure user accounts with matching emails
- 7
Install Copper Data Sync From HubSpot Marketplace and Initiate Smart Transfer
Install Copper Data Sync from HubSpot Marketplace and initiate Smart Transfer
- 8
Smart Transfer Audits Data and Creates Properties/pipelines Automatically Based on Copper Config
Smart Transfer audits data and creates properties/pipelines automatically based on Copper config
- 9
Select Objects and Data Types to Transfer; Review and Adjust Field Mappings
Select objects and data types to transfer; review and adjust field mappings
- 10
Run Smart Transfer to Sync People, Companies, and Opportunities
Run Smart Transfer to sync People, Companies, and Opportunities
- 11
Separately Migrate Leads (as Contacts With Lifecycle Stage), Tasks, Notes, and Activities via CSV or Migration Tools
Separately migrate Leads (as Contacts with lifecycle stage), Tasks, Notes, and Activities via CSV or migration tools
- 12
Migrate Projects Data Using Appropriate HubSpot Object Type
Migrate Projects data using appropriate HubSpot object type
- 13
Handle Email History
use specialized tools to preserve Gmail activity metadata as HubSpot timeline engagements
- 14
Install and Configure HubSpot Gmail Extension for All Users; Train on New Email Logging Workflow
Install and configure HubSpot Gmail Extension for all users; train on new email logging workflow
- 15
Rebuild Automations, Reports, Dashboards, and Email Templates in HubSpot
Rebuild automations, reports, dashboards, and email templates in HubSpot
- 16
Validate Data
spot-check records, verify associations, test automations, confirm email logging works
- 17
Train Team With Emphasis on Gmail/HubSpot Workflow Changes; Go Live
Train team with emphasis on Gmail/HubSpot workflow changes; 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 email required. The ranges come from the research above: every feature we mapped carries an effort figure, and this adds up the ones that apply to you.
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 and no agency markup, so add your own. 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 Email Logging Changes
Copper auto-logs Gmail interactions seamlessly; HubSpot requires the sales extension and explicit opt-in per email - this is the biggest user behavior change
Auto-created Contacts From Gmail
Copper may have auto-created many low-quality contacts from email interactions - audit and clean before migration
Google Workspace Workflow Disruption
users deeply embedded in Copper's Gmail sidebar will experience significant workflow changes
Copper Projects Map Onto the HubSpot Projects Object, Which Carries Pipelines, Stages, Board and Gantt Views and Tasks; What Does Not Map Is Budgets and Resource Allocation, So Confirm the Client Does Not Depend on Those
Copper Projects map onto the HubSpot projects object, which carries pipelines, stages, board and Gantt views and tasks; what does not map is budgets and resource allocation, so confirm the client does not depend on those.
Email History Date-stamp Corruption
Gmail-integrated activity metadata can get corrupted during migration if not handled properly
Owner Reconciliation
depends on email-based user matching - ensure all HubSpot users are created with matching emails before migration
Copper's Unique Field Types (relationship Types, Connect Fields) May Not Have Direct HubSpot Equivalents
Copper's unique field types (relationship types, connect fields) may not have direct HubSpot equivalents
Historical Activity Imports Restricted by HubSpot
creative data-structuring may be needed
Copper's Auto-enrichment From Google Stops - Need to Decide on HubSpot Breeze Intelligence as Replacement
Copper's auto-enrichment from Google stops - need to decide on HubSpot Breeze Intelligence as replacement
Questions
Copper To HubSpot, Answered
Yes. Data sync, two way, covering 8 objects. Smart transfer is supported. What it does not do is rebuild 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 is not by itself a long project.
Of 62 features we mapped, 47 (76%) carry across directly and 14 (23%) map partially, meaning something is lost or reshaped. 1 have no HubSpot equivalent at any tier.
21 items have to be rebuilt by hand, and 10 documented limitations are not surfaced by the connector at all. The full list of both is on this page.
HubSpot Free CRM for default field sync; Data Hub (Data Hub) Starter ($15/mo/seat) for custom field mappings; Enterprise for custom objects. Copper requires Starter, Basic, Professional, or Business plan.
1: Suggested Contacts. If a client depends on one, it belongs in the conversation before the contract.
Only in one direction. The sync is not bidirectional here, so a parallel period means picking a system of record and accepting drift in the other.
Ready to get started?
Let's do something great together.
Augment your agency's marketing team's bench with our end-to-end inbound and digital solutions and find out why we're "The HubSpot Agency for HubSpot Agencies."
Fill out this form, and someone from our Solutions team will be in touch with you soon!