Gong to Gong
Consolidating two Gong instances after an acquisition, without losing either side’s history or double-counting the calls they shared.
- Moving from
- Gong
- 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 Gong
Both ends are Gong, so the two sides speak the same language and more survives the move than in any other migration. That symmetry helps; it does not make the job simple.
What we need from you before we start
- A Gong administrator to grant us access to load into your instance
- A user mapping between the two organizations, including reps who exist in both
- Workspace placement decisions where the destination has more than one workspace
What comes across
The one migration where source and destination are the same system, which sounds easier than it is. Both ends limit how fast data moves, where calls land in a multi-workspace destination has to be decided explicitly, and deduplicating the calls two organizations both hold is a genuine problem rather than a formality.
Comes across
- The recordings themselves, playable in the destination instance
- Which rep owned each call, mapped across the two organizations
- When each call happened, so both histories interleave correctly
- Who spoke when — this carries natively between Gong instances
- Account and opportunity links, where both organizations point at compatible records
Doesn’t come across
- Both instances limit how fast data moves, and reading from one competes with writing to the other. The schedule accounts for both rather than assuming either is free.
- Where the two organizations worked the same deals before the acquisition, the same call can exist on both sides. Loading naively double-counts it, so deduplication happens during identity resolution, before any load.
- Workspace placement is not expressed the same way as user or account mapping and has to be agreed up front for multi-workspace destinations.
- The 60-second minimum applies here exactly as it does to any other source, including to calls that are already sitting in a Gong instance today.
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 Gong?
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.