ProsperWorks to HubSpot
Google Workspace-native CRM, renamed from ProsperWorks to Copper in July 2018.
ProsperWorks data can move into HubSpot, landing mainly in Sales Hub. 3 of 7 mapped objects move directly (People, Companies and Opportunities); 4 items need manual work and 3 do not move. Plan roughly 1-3 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for ProsperWorks
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
<10k records
List export and CSV import.
Mid migration
10k-100k records
Includes activities and workflow rebuild.
Large migration
>100k records
Needs API extraction and a 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 ProsperWorks: what you need to get in, what lands in HubSpot, and what will not.
REST API (public)
Choose your route
How will you move the data?
No native connector was found.
- You need: To confirm
- Permission: To confirm
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.
- In-app list export of People, Companies and Opportunities to Excel (.xlsx) with filters and field selection
- Third-party replication via the official API (for example Flatly, which lists about 30 data sets)
Limits: To confirm
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: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In ProsperWorks
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People | Contacts | yes | Exported to xlsx from the People list, then imported to HubSpot via CSV/xlsx import. |
| Companies | Companies | yes | The export was documented for people, companies and opportunities; I did not verify the association columns. |
| Opportunities | Deals | yes | Export from list view with pipeline, stage, value, close date and status fields; the pipeline must be rebuilt in HubSpot first. |
| Activities (notes, calls, emails, meetings) | Notes, Calls, Emails, Meetings | partial | Whether the list export covers activity history is unconfirmed; it likely needs API extraction. |
| Tasks | Tasks | partial | Export coverage is unverified. |
| Users/owners | Owners (users) | manual | Users must be created in HubSpot first, then owner mapped by email. |
| Files (Drive-linked) | Files | manual | Copper indexes Google Drive files, so the files stay in Drive and need re-linking. |
What to expect
Rules are configuration, not exportable data; they must be rebuilt as HubSpot workflows.
Reports must be rebuilt in HubSpot reporting.
These must be recreated in HubSpot teams and permission sets.
Deal stage values must exist before the import.
Copper supports custom fields; types must be mapped.
Scope note flags this; coverage of the export is unverified.
Copper logs Gmail and Calendar activity natively.
Test an export and, if needed, extract via the API into association-ready files.
Export in filtered batches and reconcile counts.
Sequence the sync after the historical import.
Confirm the tenant and plan with the customer.
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.
ProsperWorks is the former name of Copper (rebranded 2018), and the product is still sold as Copper. I found no vendor API docs, no HubSpot docs and no Copper help-centre pages. Export and API details rest on third-party guides and category-level knowledge, so access and object mapping are not backed by vendor or HubSpot docs.
Sources
Related migrations
Frequently asked questions
How do I migrate ProsperWorks to HubSpot?
1. Confirm the account is on Copper (ex-ProsperWorks) and identify an admin user. 2. Inventory People, Companies, Opportunities, pipelines, custom fields and tags. 3. Test-export People, Companies and Opportunities to xlsx and check for ID and association columns. 4. Request or generate a Copper API key if API extraction is needed.
What data can move from ProsperWorks to HubSpot?
These objects move directly: People, Companies and Opportunities. Check the mapping table for partial and manual items.
What does not move from ProsperWorks to HubSpot?
Workflow automation rules, Reports and dashboards and Permissions and roles. Plan to rebuild or retire these.
How long does a ProsperWorks to HubSpot migration take?
Small (<10k records): 1-3 weeks. Mid (10k-100k records): 3-6 weeks. Large (>100k records): 6-12 weeks. These are planning estimates, not a quote.
What compliance issues apply when moving ProsperWorks data?
Check: Cross-industry; sensitive data may appear in free-text notes. Agree consent, retention and access rules before exporting.
Moving ProsperWorks 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