How to Migrate from Gong to Fathom (Free, Step by Step)

Everything you need to move your team's call history from Gong to Fathom before your contract ends, and what to set up once you're in.

Quick answer: Fathom migrates your Gong call recordings, transcripts, and comments for free. You share a Gong API access key and secret key, tell us how to handle calls from former employees, and Fathom's team does the rest. Backing up your calls takes a day or two, and importing them into each teammate's account takes two to three weeks as your team signs up. Aim to start at least two weeks before your Gong contract ends. With an annual Fathom Business or Enterprise agreement, you also get Fathom free through the end of your Gong contract, up to six months.

Your Gong renewal is on the calendar, and the new quote is in your inbox. Somewhere in Gong sit years of customer calls your team still goes back to: the discovery call behind your biggest deal, the objection your best rep handles better than anyone, the onboarding call every new CSM should watch in week one.

That history is usually the reason teams hesitate to switch. It doesn't have to be. Here's how a Gong to Fathom migration works, what you'll need to pull together, and how to time it so nothing gets left behind.

What moves from Gong to Fathom

• Video call recordings, with no loss in audio or video quality.
• Transcripts and comments from each call.
• Call details, including attendees, dates, durations, and titles.
• Timestamps and highlights your team marked in Gong.
• Call visibility, your way. Keep each call's Gong visibility, or set every migrated call to private or to visible.

What doesn't move

• Audio-only calls. Fathom imports video recordings only, and tells you how many audio-only calls it skipped.
• Internal tags, folders, and alerts from Gong.
• Automatic Fathom summaries. Imported calls aren't re-summarized automatically. You can apply a Fathom summary to any migrated call from the app.

The migration also pulls your whole Gong library at once. Gong's API doesn't let anyone pull only internal or only external calls.

Before you start: what you'll need

1. A Gong API access key and secret key. A Gong technical administrator can generate both in Gong's API settings. The keys need access to every call you want to move.
2. A plan for former employees' calls. Decide whether calls from people who have left should go to a teammate or be left out. For current teammates who haven't joined Fathom yet, their calls can wait until they sign up. Fathom's team confirms the mapping with you before anything is imported.
3. Your call count and how far back it goes. Share your total number of Gong calls and roughly when your Gong data starts, by month and year. Gong's API allows 10,000 requests a day, so volume shapes the timeline.
4. Your contract end date and last day of API access. Gong API access ends within 30 days of your contract expiring. Confirm both dates, since Fathom needs to back up your calls before access closes.
5. A privacy decision. Choose whether migrated calls keep their Gong visibility, become private, or become visible to your team.

How to migrate from Gong to Fathom, step by step

Step 1: Request your free migration

Fill out the switching offer form. A Fathom rep follows up to scope your seats and timing. If you'd like proof before committing, Fathom can run a test import of a few specific calls first.

Step 2: Set up your Fathom workspace

Once your annual Business or Enterprise agreement is signed, your rep turns on Fathom for your team at no cost through the end of your Gong contract. An admin onboarding session covers sharing settings, permissions, and integrations.

Step 3: Share your Gong keys and decisions

Send over your API access key, secret key, and your decisions on former employees and privacy. Fathom's engineering team opens a migration ticket and keeps you updated while it runs.

Step 4: Fathom backs up your Gong calls

Fathom copies every call into its own cloud, usually within a day or two depending on volume. The backup is a one-time pull, so if your team keeps recording in Gong during the switch, your rep can time a final pull before your API access ends to catch calls from the overlap.

Step 5: Invite your team

Calls import into each teammate's Fathom account as they join, so send invites as soon as the workspace is ready. The faster your team signs up, the faster the import finishes. On Fathom Enterprise, your IT team can provision everyone at once with SCIM through Okta or Microsoft Entra ID, so the import isn't waiting on sign-ups.

Step 6: Check the results

Spot-check a few reps and accounts to confirm their calls are where they should be. If you'd like a record, ask for a CSV of imported calls (date, owner, URL, and title) before your Gong API access ends. Once the backup is confirmed, your Gong contract can end on schedule while calls keep landing as teammates join.

How long a Gong migration takes

The backup takes a day or two for most teams, depending on how many calls you have. The import takes two to three weeks, because calls attach to each teammate as they sign up. Aim to start at least two weeks before your Gong contract ends so the backup finishes with room to spare.

What switching from Gong costs

With an annual Fathom Business or Enterprise agreement, the migration is free and Fathom is free through the end of your Gong contract, up to six months. Longer remaining terms are reviewed case by case. The offer covers your team's paid Gong seats. After that, Fathom Business runs $25 per user per month, billed annually. See Fathom pricing for every plan.

On G2, Fathom users report an average ROI in 4 months, compared with 10 months for Gong. Or, as one reviewer put it: "A fraction of the price of Gong and absolutely better." For the full side-by-side, see Fathom vs. Gong.

What to set up once you're in Fathom

• Connect your CRM. Fathom Business syncs call notes and fields to HubSpot and Salesforce. Imported Gong calls don't sync automatically, which keeps duplicates out of your CRM. If you want historical calls attached to current deals, run an all-past-call sync. Browse every option on the integrations page.
• Set up Trackers to flag the topics your team cares about, like competitors or objections, across every call.
• Turn on Meeting Types so each call gets the right summary template and richer data for your integrations and API.
• Turn on scorecards to coach reps against the same criteria on every call.
• Search your full history. Ask Fathom answers questions across your team's calls, migrated calls with transcripts included. Through Fathom's MCP server, the same data works in AI assistants like Claude.

Running a security review before you switch? Fathom's Trust Center has the documentation your IT and security teams will ask for.

Plan your switch from Gong

The teams that switch smoothly start at least two weeks before their contract ends, send API keys early, and invite their reps on day one. Everything else, Fathom's team handles. Fathom users save an average of 38 minutes per meeting on notes and follow-up, and that starts the day your team is in.

Get your free Gong migration and Fathom free through the end of your contract.

FAQs about migrating from Gong to Fathom