Once an organization decides to move from Gong to Zoom Revenue Accelerator (ZRA), it doesn’t take long for someone to ask the obvious question:
How long is this migration actually going to take?
It’s a fair question.
If your Gong environment contains hundreds or thousands of historical customer conversations, you probably don’t want the migration turning into a months-long engineering project.
But there isn’t one migration timeline that applies to every organization.
Moving 500 well-organized recordings is very different from moving 20,000 conversations collected over several years across hundreds of users.
So instead of asking only:
“How long does a Gong-to-ZRA migration take?”
A better question is:
“What determines how long our Gong-to-ZRA migration will take?”
Let’s break it down.
First, What Actually Happens During a Gong-to-ZRA Migration?
A migration isn’t simply:
Download recording → Upload recording → Done.
Historical conversations contain more than media files.
Depending on what your organization wants to preserve, the migration may involve retrieving:
- Recordings
- Transcripts
- Meeting metadata
- Hosts
- Participants
- Speaker information
- Conversation dates and titles
- Other available historical context
Gong provides APIs for retrieving information such as calls, users, participants, transcripts, media, and analyzed call data. Gong’s APIs also have usage limits, which need to be considered when processing larger environments.
On the destination side, Zoom provides APIs specifically for migrating historical recordings from external systems into ZRA. Its migration workflow supports recordings along with Gong-formatted transcript and metadata files, participant information, hosts, and speaker information.
So there are really several stages happening behind the scenes:
Analyze → Prepare → Extract → Migrate → Validate
And each one can affect the overall timeline.
1. Recording Volume Is the Obvious Starting Point
Let’s start with the easiest factor.
How many conversations are you actually migrating?
There is a significant difference between an environment containing:
500 recordings
and one containing:
5,000 recordings
and another containing:
50,000 recordings.
More recordings mean more source data to retrieve, more media to transfer, more conversations to create in ZRA, and more results to monitor and validate.
But recording count isn’t the only thing that matters.
Two companies could each have 5,000 recordings and still experience very different migration projects.
Why?
Because the condition of those 5,000 conversations matters too.
2. The Size of Your Recordings Matters
Five thousand ten-minute conversations and five thousand hour-long video meetings aren’t the same amount of data.
Media size affects how much information needs to be transferred between platforms.
Zoom’s ZRA migration APIs support common media formats including MOV, MP4, AVI, WMV, and H.264, and its Upload File API documents a maximum file size of 2 GB before multipart handling is required.
That means the number of recordings gives you one view of migration size.
The actual media volume gives you another.
When estimating a migration timeline, both are useful.
3. Source Data Accessibility Can Speed Things Up—or Slow Things Down
Before ZipZap can move a conversation, the required source information needs to be accessible.
That sounds obvious.
Until it isn’t.
Historical environments can contain recordings belonging to former employees, conversations with different permissions, missing transcripts, or information that isn’t available in exactly the same way across every call.
Gong’s API provides access to calls, users, transcripts, participants, and other call information, subject to the appropriate permissions and API limits. Gong currently documents default API limits of three calls per second and 10,000 API calls per day.
If the required data is accessible and consistent, the migration can move much more predictably.
If the source environment contains exceptions, those may need attention before or during migration.
This is one reason a pre-migration analysis can be so valuable.
It’s much easier to estimate a journey after you’ve looked at the map.
4. User Mapping Can Affect the Timeline
Recordings belong to people.
And those people need to be handled correctly when historical conversations move into ZRA.
Imagine an organization where every Gong user has a matching Zoom account using the same email address.
Nice.
Now imagine another organization where:
- Employees have left the company
- Email addresses have changed
- Accounts have been renamed
- Some historical users don’t exist in Zoom
- Certain conversations require different ownership rules
Same number of recordings.
Very different preparation.
Zoom’s migration guidance recommends using host information to associate imported conversations with the appropriate provisioned users. Users associated with migrated recordings also need the appropriate ZRA provisioning.
The cleaner your user mapping is before migration begins, the fewer ownership questions need to be resolved along the way.
5. Testing Is Part of the Timeline Too
It can be tempting to think:
“We have 5,000 recordings. Let’s just start moving all 5,000.”
That’s usually not the best first move.
Zoom recommends conducting a preliminary test using a limited number of recordings before proceeding with a broader migration.
Why?
Because a test migration gives you an opportunity to check whether:
- Recordings play correctly
- Hosts are associated properly
- Participants appear as expected
- Transcripts are available
- Speaker information is represented correctly
- Titles and dates are accurate
- Historical conversations appear the way your team expects
If something needs adjusting, discovering it with a small sample is considerably easier than discovering it after several thousand conversations have already moved.
Testing adds a little time at the beginning.
It can save considerably more time later.
So, How Long Can a ZipZap Migration Take?
Now we can get to the number everyone was looking for.
For a straightforward Gong-to-ZRA migration using ZipZap, approximately 5,000 recordings can typically be migrated in around 2–3 days once the environment is ready for migration.
That is an estimate rather than a universal guarantee.
The actual timeline can vary depending on factors such as:
- Recording sizes
- Source-data availability
- API constraints
- User mapping
- Transcript and metadata availability
- Environment readiness
- Validation requirements
- Unexpected exceptions in historical data
This is also why knowing the recording count alone isn’t enough to promise an exact migration completion date.
5,000 recordings tells us something.
5,000 recordings with a clear date range, accessible media, clean user mappings, available transcripts, and a prepared ZRA environment tells us considerably more.
What About Smaller Migrations?
For smaller environments, the actual data transfer may naturally require less time.
But that doesn’t mean you should skip preparation and testing.
Whether you’re moving 500 recordings or 5,000, the same basic principles still apply:
Understand the environment.
Prepare the users and access.
Test the migration.
Move the data.
Validate the result.
A smaller migration isn’t an excuse to skip the important parts.
It just means there may be fewer conversations waiting for you if something goes wrong.
What If You Have More Than 10,000 Recordings?
This is where the conversation changes.
ZipZap’s self-service experience is designed for straightforward migrations within its supported range.
For environments with more than 10,000 recordings, rather than providing a generic timeline based only on recording count, the migration should be assessed based on the actual environment and requirements.
Large migrations can introduce additional considerations around:
- Total media volume
- Number of users
- Historical date range
- Source-data accessibility
- Complex user mappings
- Custom requirements
- CRM relationships
- Validation requirements
- Other environment-specific considerations
In those situations, a Professional Services migration can be assessed and planned around the organization’s actual requirements.
Because once migration volumes become large enough, saying:
“You have X recordings, so it will take exactly Y days.”
isn’t particularly useful.
The environment matters.
Can You Make the Migration Faster?
Often, yes.
And surprisingly, the biggest improvements don’t necessarily come from transferring files faster.
They come from removing uncertainty before the migration starts.
Before beginning your Gong-to-ZRA migration, try to have clear answers to:
- How many recordings are being migrated?
- What historical date range should be included?
- Are the required recordings accessible?
- Are transcripts available?
- Which users own the historical conversations?
- Do those users exist in Zoom?
- How should former or inactive users be handled?
- Is the ZRA environment ready?
- Are the necessary credentials and permissions available?
- How will the migrated conversations be validated?
The fewer of those questions you need to answer halfway through the project, the smoother the migration can be.
Don’t Wait Until Your Gong Contract Is About to End
There’s one timeline that matters even more than the migration timeline:
How long you still have access to your Gong data.
If your organization is moving away from Gong, don’t leave the migration until the final few days of your existing agreement.
Zoom’s migration documentation notes that Gong media files, transcript files, and metadata files can be backed up to storage such as AWS S3 before a Gong license expires and migrated into ZRA afterward.
That can provide another migration path, but planning ahead is still much simpler than realizing on Friday afternoon that access disappears on Monday.
Know your contract timeline.
Understand your data.
And start preparing early enough to deal with anything unexpected.
The Transfer Isn’t the Whole Timeline
There’s one final thing worth remembering.
If ZipZap finishes transferring your recordings, that doesn’t necessarily mean your migration project should immediately be considered finished.
Validation matters.
Zoom’s documented success criteria for historical conversation migration include correct host association, visible participants, speaker names, and use of the source transcript where appropriate.
After migration, your team should inspect the destination environment and confirm that the historical conversations arrived as expected.
Think of the project as:
Preparation → Testing → Migration → Validation
rather than simply:
Migration
The actual transfer may only be one part of the journey.
So, What’s the Timeline for Your Migration?
If you’re looking for one universal number, there isn’t one.
But you can get a much better estimate once you understand your environment.
For a straightforward migration of around 5,000 recordings, ZipZap can typically complete the migration in approximately 2–3 days once the environment is ready.
For larger or more complex environments—particularly those with more than 10,000 recordings—the better approach is to assess the migration requirements and determine an appropriate Professional Services migration plan.
The important thing is not to guess based on how many recordings you think you have.
Find out.
Find Out What Your Gong-to-ZRA Migration Looks Like
ZipZap helps organizations understand their Gong environment before beginning a migration to Zoom Revenue Accelerator.
With a pre-migration analysis, you can identify your recording volume, historical scope, users, and other migration considerations before the transfer begins.
For straightforward migrations, ZipZap then provides a guided path for moving your historical conversations into ZRA.
And when the environment requires something more complex, the migration can be assessed for a Professional Services approach.
Because the best migration timeline isn’t the fastest number someone can promise you.
It’s the one based on what you’re actually migrating.
Ready to Estimate Your Gong-to-ZRA Migration?
Start by understanding what’s inside your Gong environment.
Run your pre-migration analysis with ZipZap and get a clearer picture of your migration before the first recording moves.