How to export Gong conversation data when switching to another revenue intelligence platform

To export Gong conversation data when switching platforms, use the Gong Public API to pull calls, transcripts, and analytics programmatically, or request a bulk data export through Gong support. The API gives you structured JSON for recordings, transcripts, participants, and call metadata, which you can then map into your new revenue intelligence tool.

Most teams underestimate how much cleanup the migration takes. Gong stores conversation data across several object types — calls, transcripts, trackers, scorecards — and they don't all come out in one tidy file. Plan for a phased export.

What data lives inside Gong

Before exporting, know what you're actually moving. Gong holds more than recordings.

The core objects are call recordings (audio/video), transcripts with speaker labels and timestamps, call metadata (participants, date, duration, deal association), interaction stats (talk ratio, longest monologue, question count), trackers and keyword hits, scorecards, and CRM sync fields. Some of this is reconstructable in a new tool; some isn't. Sentiment scores and Gong-proprietary analytics generally don't transfer because each platform calculates them differently.

Method 1: Gong Public API

The Gong Public API is the most reliable route for a structured, repeatable export. You'll need a paid Gong plan with API access and a set of API credentials (an Access Key and Access Key Secret) generated under your company settings.

Authentication uses Basic Auth with those keys. Key endpoints you'll lean on:

• GET /v2/calls — list calls with filters for date range and workspace
• POST /v2/calls/extensive — retrieve detailed call objects including metadata and parties
• POST /v2/calls/transcript — pull full transcripts by call ID
• GET /v2/users — map Gong users to your new platform's reps

A typical export loops through /v2/calls to collect call IDs, then batches those IDs into /v2/calls/transcript and /v2/calls/extensive requests. Here's a minimal example:

curl -X POST https://api.gong.io/v2/calls/transcript \
  -H "Authorization: Basic $(echo -n 'ACCESS_KEY:SECRET' | base64)" \
  -H "Content-Type: application/json" \
  -d '{"filter": {"callIds": ["7782342274025502000"]}}'

The API returns JSON. Watch the rate limits — Gong caps requests (historically around 3 requests/second and a daily ceiling), so build retry logic with exponential backoff for 429 responses. The full schema is documented in the Gong API reference, which you should pull up before writing any code.

Getting the actual audio and video

The API exposes call media via a media URL field on the call object, but those URLs are time-limited. If you need to archive recordings long-term, download the media files immediately after fetching each URL rather than storing the link.

Generate Proposals with AI in seconds.

Try now

Method 2: Bulk export request through Gong

If you don't have engineering bandwidth, contact Gong support and request a bulk data export. This is common during offboarding. Gong can provide a data dump, though the format and completeness vary by contract. Read your agreement — some plans guarantee data portability on termination, others don't.

Start this conversation early. Bulk exports can take days to weeks depending on data volume, and you don't want recordings deleted under retention policy before you've pulled them.

Mapping data into the new platform

Getting data out is half the job. The harder half is making it useful in your new tool. Most revenue intelligence platforms — Chorus, Clari Copilot, Avoma, Fathom — accept transcript imports but won't ingest Gong's proprietary analytics.

Budget time to rebuild trackers and scorecards from scratch. They rarely survive migration. The same discipline that helps when you evaluate prospecting platform limits applies here: list what you actually use before assuming the new tool replicates it.

A practical migration sequence

Run the export as a project, not a one-shot script.

1. Audit what data you need — recent calls only, or full history? This drives cost and time.
2. Generate API credentials and test against a small date range.
3. Export transcripts and metadata first; they're text and small.
4. Pull media URLs and download recordings in parallel batches.
5. Validate counts — number of calls exported should match Gong's UI.
6. Map fields to your new platform's import schema.
7. Run a pilot import with one team before the full cutover.

Keep both systems live during cutover. Don't cancel Gong until you've verified the import and your reps confirm the new tool works for daily calls. Sales teams that lose call history mid-quarter lose deal context, and that hurts pipeline.

Compliance and data handling

Call recordings often contain PII and customer conversations covered by consent laws. When you export and re-import, you're moving sensitive data — handle it under your existing data processing agreements. Delete intermediate export files from local machines and storage buckets once the migration is confirmed. If you operate in the EU, treat this as a GDPR-relevant transfer and document the lawful basis.

Key takeaways

Use the Gong Public API for structured, repeatable exports of calls, transcripts, and metadata, and request a bulk export from support if you lack engineering resources. Expect proprietary analytics, sentiment, and trackers to not transfer — plan to rebuild them. Export early, validate counts, run both platforms in parallel during cutover, and treat recordings as sensitive data throughout the move.