This article explains how to move your recorded calls from Fathom into Jiminny using Zapier. It is for admins planning a migration.
Before you start
You need a Zapier account on a monthly plan with enough tasks to cover the number of calls you are migrating.
Every person whose calls you want to import must exist as a user in Jiminny, with the same email address they used in Fathom. This includes people who have left: add them and then deactivate them. See Managing users.
Note: A call is skipped if its recorder's email does not match a user in your Jiminny organisation.
Migrating your calls
The migration uses a Zap that sends each Fathom recording to Jiminny. Fathom then replays that Zap for your past calls, so you build and test it first.
Generate a Jiminny API Key. You need it to connect Zapier to Jiminny, so store it securely.
Connect Jiminny and Fathom to Zapier using the Connection Wizard.
Create the migration Zap. Use the Fathom trigger New Download Video and the Jiminny action Upload Conversation, then map the fields. When prompted, choose to trigger on downloads from the wider team, not just your own user.
Add any filters or lookups you need. See Choosing what to migrate below.
Publish and test the Zap by creating a new download video in Fathom and checking the call appears in Jiminny.
Request the migration. Ask Fathom Support to bulk create New Download Video for your migration scope and then run a retroactive Zapier trigger for the same calls. This replays your Zap for each past call.
Note: Running the Zap again for a call that has already been imported does not create a second copy.
Choosing what to migrate
Decide the scope before you contact Fathom Support, for example the time period (such as the last six months) and which teams to include.
Avoiding duplicate calls
If some of your team already record with Jiminny, the same meeting may exist in both tools. Jiminny cannot tell that a Fathom recording and a Jiminny recording are the same meeting, so both copies are kept. To avoid this, leave those users out of the migration, or only include their calls from before they started using Jiminny. A Zapier Filter step on the recorder's email or the call date does this.
Note: If duplicates do get through, delete the imported copy in Jiminny. A deleted call is not imported again if the Zap runs for it later.
Calls recorded by people who have left
You can import these calls in one of two ways:
Keep them under the original recorder. Add the person to Jiminny and deactivate them. Their calls import under their name.
Assign them to a current team member. Add a Zapier Formatter lookup table step that replaces the former employee's email with the current team member's email before the Upload Conversation action.
Linking calls to your CRM
An imported call links to a CRM record only when the Zap passes that record's ID, such as a HubSpot contact, company or deal ID. If no ID is passed, or the record is not found in your CRM, the call still imports without a CRM link.
What gets migrated
Jiminny matches Fathom users to Jiminny users by email address. For each call, the following is copied:
Call details (title, time, duration and recorder)
The transcript, with speakers separated
The recording, including video
Note: Imported calls do not get AI summaries or action items, either at import or afterwards. Transcripts and conversation statistics are available for coaching.
Setting up Themes, Topics and Triggers
During onboarding, we work with you to configure your Themes, Topics and Triggers in Jiminny. If you have trackers set up in Fathom, share them with us and we will help recreate them. See Importing your Themes and Topics.
Once your calls are imported, Jiminny analyses them and their statistics become available for coaching.