Copper to HubSpot
Copper, formerly Prosperworks, is a Google Workspace-centric CRM with People, Companies, Leads, Opportunities, Projects and Tasks.
Copper data can move into HubSpot, landing mainly in Sales Hub. 3 of 9 mapped objects move directly (People, Companies and Opportunities); 5 items need manual work and 2 do not move. Plan roughly 1-3 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Copper
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<25k records
CSV or Excel import with staged associations.
Mid migration
25k-250k records
Tool-assisted migration with activities and workflow rebuild.
Large migration
>250k records
API extraction, custom objects for Projects, phased cutover.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Copper: what you need to get in, what lands in HubSpot, and what will not.
REST (JSON) Developer API
An API key generated in Copper settings, plus the email of the key owner. OAuth is available for apps.
Admins can export all data by default. Other users need the 'Data Export' permission.
A third-party guide reports 180 requests per minute, with HTTP 429 on excess. This is not confirmed in the official docs I reviewed.
Choose your route
How will you move the data?
No native connector was found.
- You need: An API key generated in Copper settings, plus the email of the key owner. OAuth is available for apps.
- Permission: Admins can export all data by default. Other users need the 'Data Export' permission.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Settings > Export Data for People, Companies, Opportunities, Projects, Tasks and Leads
- Filtered list export from list views, delivered as an Excel file by email
- REST API search and list endpoints, including Activities, Users, custom field definitions, related items and file lists
Limits: A third-party guide reports 180 requests per minute, with HTTP 429 on excess. This is not confirmed in the official docs I reviewed.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Copper
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People | Contacts | yes | Included in the Excel export and the API. |
| Companies | Companies | yes | Associate companies to contacts and deals on import using unique keys. |
| Opportunities | Deals | yes | A community case imported contacts and deals together using a unique identifier, then associated companies in a second pass. |
| Leads | Contacts | partial | HubSpot has no separate Leads object like Copper's, so the lead status must be mapped to a property or lifecycle stage. |
| Tasks | Tasks | partial | Exportable from Copper. Migration tools list tasks as migratable. |
| Projects | Custom objects | manual | Exportable, but HubSpot has no standard project equivalent. Use a custom object or a pipeline. |
| Activities (notes, calls, emails, meetings) | Notes | partial | The Activities API exists. Coverage for email and meeting history is not in the standard Excel export, so audit it. Tools claim to migrate notes and activities. |
| Users (record owners) | Contacts | partial | Map owners to HubSpot users by email. The Users API lists user IDs, names and emails. |
| Pipelines and stages | Deals | manual | Recreate the pipelines and stages in HubSpot before import. |
What to expect
They are not exposed in the export or the API documentation I reviewed, so they must be rebuilt as HubSpot workflows.
HubSpot has no contact-tag system, so tags need an explicit mapping to properties or lists.
Neither the Excel export nor the API documentation covers them.
Copper user permissions are not carried over by data export.
These have no clean HubSpot equivalent.
Records auto-created from Gmail activity can inflate HubSpot contact counts.
The Excel export lists record types only. Associations need a unique key or an API pull.
Carry Copper IDs as unique-key properties and import in stages, as in the community case.
Pull Activities via the API or use a migration tool, then reconcile counts.
Filter records before export.
Define target properties first.
Batch requests and back off on 429 responses.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export paths and API access are backed by Copper docs and help pages. HubSpot-side mapping, activity export coverage, certifications and residency rest on third-party guides or category knowledge, and no HubSpot doc or native connector was confirmed.
Sources
Related migrations
Frequently asked questions
How do I migrate Copper to HubSpot?
1. Check that the exporting user has the Data Export permission or is an admin. 2. Export People, Companies, Opportunities, Projects, Tasks and Leads as a backup. 3. Generate a Copper API key and test the Activities and Users endpoints. 4. Inventory custom fields, tags, pipelines and connect fields in Copper.
What data can move from Copper to HubSpot?
These objects move directly: People, Companies and Opportunities. Check the mapping table for partial and manual items.
What does not move from Copper to HubSpot?
Copper automations (workflow rules) and templates and Copper tags as a tag system. Plan to rebuild or retire these.
How long does a Copper to HubSpot migration take?
Small (<25k records): 1-3 weeks. Mid (25k-250k records): 3-8 weeks. Large (>250k records): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Copper?
An API key generated in Copper settings, plus the email of the key owner. OAuth is available for apps. Admins can export all data by default. Other users need the 'Data Export' permission.
What compliance issues apply when moving Copper data?
Check: Email content may include sensitive data; review before import.. Agree consent, retention and access rules before exporting.
Moving Copper into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner