Short answer: you can move Gong call recordings and most metadata to Chorus, but you can't migrate them as a seamless one-click transfer, and some Gong-generated insights won't carry over intact. Recordings export cleanly. AI-derived analytics, scorecards, and deal intelligence are platform-specific and usually have to be rebuilt or archived separately.
What actually transfers and what doesn't
Migrating between conversation intelligence platforms isn't like exporting a CSV. The raw assets move; the derived intelligence mostly doesn't. Here's the honest breakdown.
| Data type | Transferable to Chorus? | Notes |
|---|---|---|
| Audio/video recordings | Yes | Export as MP3/MP4 via API or admin request |
| Call transcripts | Yes (as text) | Chorus re-transcribes; formatting differs |
| Call metadata (date, participants, deal) | Partial | Re-mapped to CRM, not 1:1 |
| Gong AI insights & trackers | No | Proprietary; rebuild in Chorus |
| Scorecards & coaching notes | No | Manual recreation only |
| Deal intelligence/forecasting | No | Tied to Gong's models |
Most teams get this wrong by assuming "history" means everything. In practice, your durable history is the recordings plus the CRM activity tied to them. The analytics layer is rented, not owned.
How to export your Gong history
Gong doesn't offer a native "migrate to competitor" button, for obvious reasons. You have two realistic paths.
1. Gong API export
Gong provides a public REST API that lets admins pull call recordings, transcripts, and metadata programmatically. You'll need an API key with the right scopes.
# Pull call list with media URLs
curl -X POST https://api.gong.io/v2/calls/extensive \
-H "Authorization: Basic $GONG_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"filter": {
"fromDateTime": "2023-01-01T00:00:00Z",
"toDateTime": "2024-12-31T00:00:00Z"
},
"contentSelector": {
"exposedFields": { "media": true, "transcript": true }
}
}'
Media URLs returned are time-limited, so download recordings promptly. Plan for rate limits on large libraries.
2. Admin bulk export request
For accounts with thousands of calls, ask your Gong CSM or support for a bulk data export. This is often the cleanest route for full historical archives and avoids hand-rolling pagination logic.
Getting recordings into Chorus
Chorus (now part of ZoomInfo) ingests calls primarily through live integrations with Zoom, web conferencing, and dialers. Importing historical third-party recordings is trickier.
- Bulk upload: Chorus support can ingest exported media files and re-process them through their transcription and AI engine. This regenerates Chorus-native insights on old calls.
- CRM re-association: Map each call back to the correct account, contact, and opportunity in Salesforce or HubSpot. If your CRM choice affects this, confirm field mapping before bulk import.
- Re-transcription cost: Re-running months of calls through Chorus's models takes time and may carry processing limits. Stagger the import.
The upside: because Chorus re-analyzes the audio, you get its own trackers, talk-time analytics, and keyword detection on historical calls — something a flat transcript export can't give you.
Preserving history when AI insights don't transfer
Gong's insights are the hardest loss. Trackers, deal warnings, and scorecards reflect Gong's models and your team's configuration. None of that exports as structured data into Chorus.
Practical mitigation:
- Export reporting snapshots as PDFs or CSVs before you cancel Gong. Keep them in a shared drive as a compliance archive.
- Document your tracker definitions so you can rebuild equivalents in Chorus.
- Re-create scorecards based on your coaching framework — a good moment to revisit how you run a sales discovery call and what good looks like.
- Run both platforms in parallel for 30–60 days so reps don't lose access mid-deal.
Compliance and data ownership
Before exporting, confirm two things. First, your contract terms — most conversation intelligence vendors give you a defined export window after cancellation. Don't cancel Gong before extracting data. Second, call recording consent and retention rules. If recordings contain regulated data, your security team should sign off on where exports live during migration.
Realistic timeline
For a mid-market team with one to two years of calls:
- Week 1–2: API/bulk export from Gong, validate file integrity
- Week 2–4: Chorus ingestion and re-processing
- Week 3–5: CRM re-association and QA
- Week 4–8: Parallel run, rebuild trackers and scorecards
Don't compress this. Rushed migrations lose call-to-deal associations, which is the history that actually matters for forecasting and coaching.
Key takeaways
- You can migrate Gong recordings and transcripts to Chorus, but not Gong's proprietary AI insights.
- Use the Gong API or a CSM bulk export; download time-limited media URLs promptly.
- Chorus re-transcribes and re-analyzes imported audio, regenerating its own native insights.
- Archive Gong reports, trackers, and scorecards as PDFs/CSVs before canceling.
- Run both tools in parallel and never cancel Gong before your export is verified.
The "without losing history" goal is achievable for the assets you truly own — your recordings and CRM links. Treat the analytics layer as something you rebuild, not migrate.