Your Gong account may contain years of customer conversations.
Sales calls. Product discussions. Discovery meetings. Negotiations. Follow-ups. Transcripts your team still searches months later.
So when your organization decides to move to Zoom Revenue Accelerator (ZRA), one question tends to come up very quickly:
Are we going to lose all of that history?
A Gong-to-ZRA migration can preserve much of the historical conversation data your teams rely on, including recordings, transcripts, participants, speaker information, and key meeting metadata. Zoom provides dedicated APIs for bringing historical recordings from external systems into ZRA and specifically supports Gong-formatted transcript and metadata files.
But there is an important distinction:
Migrating your conversation history does not necessarily mean every feature, insight, or object in Gong becomes an identical feature or object in ZRA.
Let’s break down what that actually means.
Your Recordings: The Foundation of the Migration
Let’s start with the obvious one.
Your historical Gong call and meeting recordings can be brought into the Zoom Revenue Accelerator as conversations.
Zoom’s migration APIs support common recording formats including MP4, MOV, AVI, WMV, and H.264. Once the media and associated information are added, the recording can become part of the historical conversation library inside ZRA.
But moving the recording alone isn’t necessarily enough.
Imagine opening a recording six months later and seeing the video but not knowing who hosted it, who participated, when it happened, or what the meeting was about.
Technically, you still have the recording.
Practically, you’ve lost a lot of its value.
That’s why the information surrounding the recording matters just as much as the recording itself.
Your Transcripts: They Can Come With You Too
Transcripts are often one of the most valuable parts of a conversation intelligence platform.
Instead of watching an entire hour-long meeting to find one important discussion, teams can search or review the transcript and jump back into the context they need.
Zoom supports the upload of the original Gong transcript alongside the recording. When a source transcript is provided correctly, ZRA can use that source transcript rather than generating a new one from the media.
That means your existing conversation history doesn’t necessarily have to start again from a blank transcript after migration.
And what if the original transcript isn’t available?
ZRA can generate a transcript from the migrated media file. Zoom notes, however, that speaker identification can vary depending on the recording format and available speaker information.
So while the recording is the foundation, preserving the original transcript where possible can help maintain more of the historical conversation context.
Speaker Information: Knowing Who Said What
A transcript without speaker context can get confusing very quickly.
“Let’s move forward with that pricing.”
Great.
But was that your salesperson or the customer?
This is why speaker attribution matters.
During migration, participant and speaker information can be included so ZRA can represent the people involved in the conversation more accurately. Zoom’s migration guidance supports participant information and speaker-related data, and its documented success criteria include host association, visible participants, and speaker names in the migrated conversation.
This is also one of the reasons you should validate speaker information before migrating your entire dataset.
A five-person sales meeting is much more useful when you can tell which person actually said what.
Meeting Metadata: The Context Around the Conversation
Every recording has a story around it.
Who hosted it?
When did it happen?
What was the meeting called?
Who attended?
Historical migration can preserve important metadata that helps answer those questions.
Depending on the migration method and available source information, ZRA supports conversation information such as:
- Conversation title or topic
- Meeting start time
- Meeting end time
- Host
- Participants
- Conversation type
- Primary language
- Speaker-related information
Zoom also supports Gong-formatted metadata files as part of its migration workflow.
This metadata may look less exciting than the recording itself, but it is what turns a collection of media files into a usable conversation history.
What About CRM and Deal Context?
This is where migrations become a little more interesting.
Conversation intelligence platforms don’t operate in isolation. Sales teams often use conversations alongside CRM information, opportunities, accounts, contacts, and deals.
ZRA has its own CRM and deal structures, and its APIs include support for associating conversations with deal information. For example, Zoom’s conversation API supports a deal_id, while ZRA also exposes APIs for CRM accounts and deal information.
However, this should not be interpreted as “everything connected to Gong’s CRM environment automatically transfers into ZRA.”
CRM preservation depends on factors such as:
- Which CRM your organization uses
- How the CRM is configured in ZRA
- Whether the corresponding opportunities or deals exist
- How historical conversations were associated with those records
- Whether IDs and relationships can be mapped correctly
- What CRM context is actually required after migration
In other words, CRM relationships need to be treated as a mapping problem, not simply a file-transfer problem.
If maintaining deal context is important to your organization, it should be identified during migration planning rather than discovered after the conversations have already been moved.
Does Every Gong Insight Transfer to ZRA?
This is one of the most important questions to clarify before a migration.
Gong contains more than recordings and transcripts. Its APIs expose analyzed call information such as topics, trackers, comments, scorecards, participants, and transcripts.
That does not mean every Gong-specific insight has a direct equivalent that can simply be imported into ZRA.
Zoom’s documented external-recording migration workflow focuses on the conversation itself and supports information around it, such as the media, transcripts, metadata, hosts, participants, and speaker information.
So items such as Gong-specific:
- Scorecards
- Trackers
- Coaching configurations
- Comments
- Platform-specific AI insights
- Custom analytics
should not automatically be assumed to migrate as equivalent ZRA objects.
This doesn’t mean the historical conversation loses its usefulness.
It means the migration should distinguish between portable conversation data and platform-specific intelligence.
That’s a very useful distinction to make before anyone presses the big imaginary “Migrate Everything” button.
What About Former Employees?
Historical conversations may belong to people who are no longer with your organization.
That’s normal especially when you’re migrating several years of data.
The challenge is deciding how those conversations should appear once they reach ZRA.
Zoom recommends using host information to associate imported conversations with the appropriate users, and users receiving migrated recordings may need to be properly provisioned in ZRA.
Before migration, your team should therefore identify:
- Active users
- Inactive users
- Former employees
- Users whose email addresses have changed
- Accounts that don’t have a direct match in Zoom
Then decide how historical ownership should be handled.
Otherwise, a technically successful migration can still leave you with a surprisingly confusing conversation library.
What If Some Gong Data Isn’t Available?
Another reality of historical migrations is that the source environment isn’t always perfectly clean.
Some recordings may be unavailable.
Some users may no longer exist.
Some conversations may not contain the expected transcript or metadata.
And access permissions can affect what can actually be retrieved from the source environment.
This is exactly why a pre-migration analysis is useful.
Instead of discovering these gaps halfway through the migration, analyze the Gong environment first and determine what data is actually available.
That gives you a much more realistic answer to:
“What can we preserve?”
rather than simply:
“What do we hope to preserve?”
A Simple Way to Think About It
When evaluating your historical Gong data, think about it in four layers:
Recording
The actual audio or video conversation.
Transcript
What was said during the conversation.
Context
Who participated, who hosted, when it happened, the topic, and other important metadata.
Business Relationship
How that conversation relates to users, customers, opportunities, or deals.
A good migration strategy considers all four.
Because preserving the video while losing everything around it isn’t really preserving the conversation experience.
Why Testing Matters
Before migrating thousands of historical conversations, run a controlled test.
Zoom itself recommends testing the migration process with a limited number of recordings before performing a broader migration.
Your test set should ideally include different situations:
- A normal customer call
- A call with multiple speakers
- A conversation with a transcript
- A conversation connected to an important deal
- A recording owned by an active employee
- An older historical conversation
Then inspect the result inside ZRA.
Can you play the recording?
Is the transcript searchable?
Are speakers represented correctly?
Is the host right?
Are the meeting details accurate?
Does the conversation retain the business context your team expected?
A small test can answer those questions before they become thousands of problems.
The Goal Isn’t to Move Everything. It’s to Preserve What Matters.
The most successful migrations aren’t necessarily the ones that move the largest amount of data.
They’re the ones that preserve the information teams actually need after the transition.
For most organizations moving from Gong to ZRA, that means understanding their historical recordings, transcripts, users, metadata, and relevant business context before starting the migration.
Once you know what exists, what matters, and what can be mapped into ZRA, the migration becomes much easier to plan.
See What Can Be Migrated Before You Start
ZipZap helps organizations analyze their Gong environment before beginning a migration to Zoom Revenue Accelerator.
With pre-migration analysis, you can understand your conversation volume, available historical data, users, and potential migration considerations before committing to the full move.
Because the best time to discover a migration issue is before the migration starts, not halfway through it.
Thinking About Moving Your Gong History to ZRA?
Start by understanding what is actually inside your environment.
Run your pre-migration analysis with ZipZap and get a clearer picture of your migration before moving your data.