GoldMine to HubSpot
GoldMine is a long-running on-premises contact and sales CRM. It keeps data in SQL tables (Contact1/2, ContSupp, ContHist, Cal, OpMgr, MailBox).
GoldMine data can move into HubSpot, landing mainly in Sales Hub. 1 of 10 mapped objects move directly (Contact1/Contact2 (contacts, user-defined fields)); 4 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 10-24 weeks for a large one.
Migration checklist for GoldMine
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 doneAfter
0 of 6 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 contacts, light history
Wizard or SQL to CSV import.
Mid migration
10k-100k contacts with history and opportunities
SQL extraction plus engagement loading.
Large migration
>100k contacts, multi-GB with emails and documents
Scripted ETL and 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 GoldMine: what you need to get in, what lands in HubSpot, and what will not.
No public REST API identified; direct SQL database access plus the built-in export wizard
Read access to the GoldMine SQL database or a GoldMine user able to run exports; HubSpot private app token or import access on the target side.
GoldMine admin or master user, plus DB read rights. HubSpot Super Admin or import permission.
Choose your route
How will you move the data?
No native connector was found.
- You need: Read access to the GoldMine SQL database or a GoldMine user able to run exports; HubSpot private app token or import access on the target side.
- Permission: GoldMine admin or master user, plus DB read rights. HubSpot Super Admin or import 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.
- Import/Export Wizard: Export Contact Records to an ASCII file, then rename it to .csv
- SQL queries or views against the backend database, the approach one migration vendor calls the best
- SQL Query tab in Premium Edition to list data from ContSupp and other tables
- GoldMine reports (Contact, Calendar, Analysis)
- Third-party ETL or migration services
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: 10-24 weeks, usually phased.
Talk to a partnerWhere each object lands
In GoldMine
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contact1/Contact2 (contacts, user-defined fields) | Contacts | yes | The wizard exports Contact1/Contact2 fields. Primary email sits in ContSupp, so SQL is needed to join it. |
| Company (field on Contact1) | Companies | partial | Company is a field on the contact record, not a separate object. Companies must be deduplicated and associated manually. |
| Additional contacts, details, referrals (ContSupp) | Contacts | partial | The export wizard cannot reach ContSupp, so SQL is needed. Treat these as extra contacts or custom properties. |
| Opportunity/Project Manager (OpMgr, OpMgrFld) | Deals | partial | The OpMgr table holds opportunities and related records. Stages must be mapped to a HubSpot pipeline. |
| History (ContHist: completed calls, appointments, notes) | Notes | partial | Can be loaded as Calls, Meetings, Notes or Emails engagements through SQL extraction and API or import. Association back to contacts via AccountNo. |
| Pending activities (Cal) | Tasks | partial | Pending appointments, calls and to-dos can map to Tasks or Meetings. |
| Emails (MailBox) | Emails | partial | Linked emails are stored in the MailBox table. Loading them needs custom work. |
| Users | Contacts | manual | Users must be created in HubSpot and mapped to owners by hand. The partner mapping lists collaborators as users/owners. |
| Contact groups / lists | Contacts | partial | Can become static or active lists, or properties. |
| Linked documents | Files | manual | Linked documents are stored as ContSupp references. File retrieval is not covered by the sources. |
What to expect
These are stored as definitions in GoldMine tables with no HubSpot equivalent; rebuild them as Workflows.
HubSpot permission sets and teams need to be designed from scratch.
Rebuild them as HubSpot reports, dashboards and lists.
The data is spread across several tables.
A partner case study found decades of inconsistent data.
The OpMgr stage and user values need translating.
The wizard exports only Contact1/2 fields, so activity and association export coverage must be checked.
Use SQL extraction across Contact1/2, ContSupp, ContHist, Cal and OpMgr.
Run a SQL check for contacts with more than one primary email before import.
Use an ETL tool or a custom API load.
Confirm the edition and version and review its table definitions.
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.
The export paths (Import/Export Wizard, SQL) and the table structure are backed by vendor-era training material and practitioner guides. I found no HubSpot native connector and no current vendor API docs. Object mapping rests on partner guides, not HubSpot docs.
Sources
Related migrations
Frequently asked questions
How do I migrate GoldMine to HubSpot?
1. Confirm the GoldMine edition (Premium or Corporate) and whether the DB is SQL Server. 2. Get read-only SQL credentials and take a database backup. 3. Inventory the Contact1/2, ContSupp, ContHist, Cal, OpMgr and MailBox tables and record counts. 4. List the UDFs (ContUDef) and decide which become HubSpot properties.
What data can move from GoldMine to HubSpot?
These objects move directly: Contact1/Contact2 (contacts, user-defined fields). Check the mapping table for partial and manual items.
What does not move from GoldMine to HubSpot?
Automated processes (tracks) and alerts, GoldMine users' security and permission settings and Reports, forms, filters and queries. Plan to rebuild or retire these.
How long does a GoldMine to HubSpot migration take?
Small (<10k contacts, light history): 2-4 weeks. Mid (10k-100k contacts with history and opportunities): 4-10 weeks. Large (>100k contacts, multi-GB with emails and documents): 10-24 weeks. These are planning estimates, not a quote.
What access do I need to export from GoldMine?
Read access to the GoldMine SQL database or a GoldMine user able to run exports; HubSpot private app token or import access on the target side. GoldMine admin or master user, plus DB read rights. HubSpot Super Admin or import permission.
Is there a native HubSpot connector for GoldMine?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving GoldMine data?
Check: Free-text notes and linked documents may hold health, financial or minors' data; review before moving.. Agree consent, retention and access rules before exporting.
Moving GoldMine 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