Clari Copilot to Gong
Clari Copilot to Gong — a migration we have run end to end, with rep attribution and speaker timing preserved and every excluded record named.
- Moving from
- Clari Copilot
- Moving to
- Gong
- What you get
- A per-record account of what landed, and what did not
- Agreed up front
- 4 known exclusions, before any work starts
How we get the data out of Clari Copilot
Clari Copilot gives us structured access to your recorded calls, their participants and their transcripts. We have run this migration end to end, so what we quote comes from what it actually took rather than from documentation.
What we need from you before we start
- Access credentials generated by a Clari administrator
- A Gong administrator to grant us access to load into your instance
- Agreement on which Gong user inherits calls owned by reps who have since left
What comes across
Clari is a well-behaved source: reliable access to calls and recordings, and transcripts whose speaker timings survive even though their text cannot follow into Gong. What shapes the engagement is how fast a large history can be read out, and the short-call floor that catches every prospecting-heavy archive.
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, reconstructed from the Clari transcript timings
- Links to accounts and opportunities where Clari holds them
- Call titles, direction and duration
Doesn’t come across
- Clari limits how fast its data can be read out, so a large history is collected over several days. We plan that alongside the loading schedule rather than discovering it midway.
- Clari transcript text, AI summaries, scores and topic tracking do not carry into Gong. Gong re-transcribes every recording it ingests and has no documented path to accept an external transcript. We deliver the Clari transcripts as a searchable sidecar export into storage you own.
- Calls under 60 seconds after silence trimming are accepted by Gong and then never appear in it. We predict these from Clari duration metadata during scoping and agree the exclusion list before loading.
- Where a Clari call has no retrievable recording — deleted media, or a call recorded outside Copilot — there is nothing to migrate. Those records are listed by ID rather than silently dropped.
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 Clari Copilot?
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.