Gong to HubSpot
Revenue intelligence platform that records and analyzes calls, meetings and emails. It also covers deal and forecast views and engagement sequences (Gong Engage).
Gong data can move into HubSpot, landing mainly in Revenue Hub. 0 of 7 mapped objects move directly; 4 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Gong
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
Under 5,000 calls, under 20 users
Native sync plus manual rebuild of sequences.
Mid migration
5,000-50,000 calls, 20-100 users
Scripted transcript export, forecast and sequence rebuild.
Large migration
Over 50,000 calls, over 100 users
Quota negotiation, archive storage, and multi-team forecast redesign.
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 Gong: what you need to get in, what lands in HubSpot, and what will not.
REST over HTTPS, JSON (v2 API)
API Access Key and Secret, or an OAuth app.
Technical administrator role is needed to generate API keys.
Default 3 calls per second and 10,000 per day. Exceeding either returns HTTP 429 with a Retry-After header. The limit can be raised by contacting Gong.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Gong.
- You need: API Access Key and Secret, or an OAuth app.
- Permission: Technical administrator role is needed to generate API keys.
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.
- API: list calls, then fetch transcripts, metadata and recording URLs per call
- Manual download of recordings as audio or video from the Gong UI
- Outbound webhook rules
- Native HubSpot activity sync (calls, meetings, emails)
Limits: Default 3 calls per second and 10,000 per day. Exceeding either returns HTTP 429 with a Retry-After header. The limit can be raised by contacting Gong.
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 Gong
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Calls and meetings (metadata, participants, recording link) | Calls | partial | The native sync pushes call and meeting activities to HubSpot. Recordings and transcripts stay in Gong, so only links and highlights move. |
| Emails captured by Gong | Emails | partial | The native integration exports captured emails as activities. Whether history can be bulk-migrated is unverified. |
| Call transcripts | Notes | manual | Transcripts can be pulled via API (POST /v2/calls/transcript). Attaching them to HubSpot records needs custom scripting, for example as Notes or Files. |
| Deal warnings, scores and risk signals | Deals | manual | One third-party guide says these sync as custom deal properties. Another says Gong does not populate custom fields. HubSpot's own deal-risk and forecast tools must be rebuilt. |
| Action items from calls | Tasks | manual | Recreate as tasks. This is based on a third-party integration description. |
| Engage sequences and flows | Custom objects | no | Rebuild as HubSpot Sequences. Flow assignment is available via the API, but no bulk definition export is documented. |
| Forecast definitions | Deals | manual | Rebuild in HubSpot forecasting. No export path was found. |
What to expect
They are Gong-proprietary analytics. The API returns outputs such as trackers and scorecards, but HubSpot has no equivalent object to hold them.
The transcript stays in Gong, and HubSpot receives only a link back.
Forecast definitions are not exposed as an export path in the sources found.
There is no documented bulk definition export.
If Gong is partly retained, recordings stay there. Otherwise they need bulk API download and external storage.
Mismatched emails cause activities to fail to associate.
Export transcripts and recordings before the licence lapses, or keep a reduced Gong licence.
Chunk the export by date range, back off on HTTP 429, and ask Gong to raise the limit.
Disable the native sync before the import, or tag imported records and dedupe on call ID.
Define the replacement forecast and deal-risk process and agree metrics with sales leadership before cutover.
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 Gong API is documented by the vendor and the HubSpot sync is described in a HubSpot marketplace listing. Object mapping, forecast and deal-risk export, sequences, and governance rest on third-party guides and category-level knowledge, and I did not check Gong's current help centre pages for them.
Sources
Related migrations
Frequently asked questions
How do I migrate Gong to HubSpot?
1. Inventory which Gong features are in use: Conversations, Forecast, Deal boards, Engage. 2. Decide which of these stay in Gong, since specialist recording and coaching may remain. 3. Have a technical administrator generate an Access Key and Secret and confirm the API scopes. 4. Estimate call volume against the 10,000 per day quota and request a higher limit if needed.
What does not move from Gong to HubSpot?
AI analysis, trackers, scorecards and call scoring models and Native recordings playable in HubSpot. Plan to rebuild or retire these.
How long does a Gong to HubSpot migration take?
Small (Under 5,000 calls, under 20 users): 2-4 weeks. Mid (5,000-50,000 calls, 20-100 users): 4-8 weeks. Large (Over 50,000 calls, over 100 users): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Gong?
API Access Key and Secret, or an OAuth app. Technical administrator role is needed to generate API keys.
Is there a native HubSpot connector for Gong?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Gong data?
Check: Call recordings may include special-category or financial data and Recording consent laws vary by jurisdiction. Agree consent, retention and access rules before exporting.
Moving Gong 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