Bring your call history to Gong
Years of recorded conversations, moved into Gong and attributed to the right reps — so coaching, deal reviews and search work on your history from the day you switch, not just on the calls you record afterwards.
Reconciliation ledger, Chorus to Gong. 5 of 6 records shown reconciled at the destination. 1 held for review: below 60s minimum. Every record is accounted for.
What comes across, and what doesn’t
Every migration has losses. Ours are agreed before the work starts rather than discovered in a report afterwards, which is the only version of this that is worth paying for.
Comes across
- The recording itself, playable in Gong
- Which rep owned the call, and who else was on it
- When the call happened, so your history stays in order
- Who spoke when, including on single-channel recordings
- Links to the right accounts and opportunities
- Call title, direction and duration
Doesn’t come across
- Transcript text from your old platform
- AI summaries, scores and trackers
- Comments, snippets and shared collections
- Recordings your source platform marks private
- Calls under a minute long
Gong transcribes every recording itself and cannot accept an existing transcript, so the analysis your old platform produced stays with it. We export those transcripts into storage you own, so they remain searchable alongside Gong rather than disappearing.
Attribution is the part that can’t be fixed later
When a call is created in Gong, the rep who owned it and the people on it are set permanently. There is no later pass that repairs them. A migration that starts loading before those are resolved produces records that look fine in a count and are useless in a coaching report.
So we treat it as a gate. Every rep in the source is matched to a user in Gong before a single call is written, and anything we cannot match with confidence comes to you as a decision rather than a guess. The common case is reps who have left — their calls still matter for historical coaching, and you choose where they land.
The cost of skipping this is concrete: wrongly attributed calls have to be deleted and re-migrated, which means paying the full loading time twice.
A successful upload isn’t proof of a successful migration
Gong accepts calls that never become visible in its interface — anything under a minute, for instance. A migration that counts successful uploads will report a clean run while quietly losing every short call, and prospecting-heavy histories contain a great many of them.
We verify differently. Every record is read back out of Gong and checked — the call exists, the recording is attached, the owner is who we intended, the account links resolved. Only then does it count. What you receive at the end is a line per source record with its outcome, and a stated reason for anything that did not make it.
Where you’re moving from
- Chorus to GongChorus to Gong, with rep attribution and speaker timing intact — and, on most engagements, without your recordings ever passing through us.
- Clari Copilot to GongClari Copilot to Gong — a migration we have run end to end, with rep attribution and speaker timing preserved and every excluded record named.
- Gong to GongConsolidating two Gong instances after an acquisition, without losing either side’s history or double-counting the calls they shared.
- Zoom to GongZoom cloud recordings into Gong, with the host and participants resolved to real people rather than “Caller 1”.
Also on the way: Salesloft, Avoma, Fireflies, Jiminny, Modjo, tl;dv. We build the adapter once and it serves every customer who needs it, so if you are moving from something not listed here, tell us — it may already be in progress.
How long it takes
| Records | Typical elapsed time | What drives it |
|---|---|---|
| Under 10,000 | 2–3 weeks | Mostly scoping and validation; the loading itself is short |
| 10,000 – 50,000 | 3–5 weeks | Loading becomes the longest phase |
| 50,000 – 150,000 | 6–10 weeks | Paced so your live integrations keep working throughout |
| Over 150,000 | Scoped individually | Worth asking Gong to raise your limits — it is the single biggest lever on the timeline |
These are ranges because the honest answer depends on your source platform and how much of your capacity your existing integrations already use. We give you a specific timeline after scoping, before you commit to anything.
Questions we get asked
Tell us what you’re moving.
Send us the source platform and a rough call count. We’ll come back with a scope, a timeline, and what we’d need from you.