Chorus to Gong
Chorus to Gong, with rep attribution and speaker timing intact — and, on most engagements, without your recordings ever passing through us.
- Moving from
- Chorus
- Moving to
- Gong
- What you get
- A per-record account of what landed, and what did not
- Agreed up front
- 3 known exclusions, before any work starts
How we get the data out of Chorus
Chorus gives us structured access to your calls and their recordings. On most engagements those recordings move straight from Chorus into Gong without passing through us at all.
What we need from you before we start
- Access granted by a Chorus administrator whose permissions cover the whole call history — access granted too narrowly quietly returns fewer calls, so we check it against your expected count before starting
- A Gong administrator to grant us access to load into your instance
- Agreement on which Gong user departed reps’ calls should be attributed to
What comes across
Chorus is close to an ideal source: reliable access to calls and recordings, and transcripts whose speaker timings we can reuse even though the text itself cannot follow. The two real constraints are how broadly access has been granted, and the private recordings Chorus withholds from everyone.
Comes across
- The recordings themselves, playable in Gong
- Which rep owned each call, and who else was on it
- When each call happened, so your history stays in order
- Who spoke when — carried across even on single-channel recordings
- Links to the right accounts and opportunities
- Call titles, direction and duration
Doesn’t come across
- Chorus never releases recordings your team marked private, so they cannot migrate. Every one is listed in your reconciliation report rather than quietly omitted.
- Chorus transcript text, AI scores, trackers and comments do not carry into Gong. Gong re-transcribes ingested media and has no documented path to accept an external transcript.
- Calls under 60 seconds after silence trimming are accepted by Gong and then never appear in it. We predict these from Chorus duration metadata at scoping and agree the exclusion list before loading.
Every one of these is identified during scoping and agreed with you before the migration runs. The field-by-field detail sits in your scoping document, where it can be discussed rather than skimmed.
Questions people ask about this migration
Moving from Chorus?
Send us a rough record count and we’ll come back with a scope, a timeline, and the exclusions we’d expect — before you commit to anything.