Jiminny can migrate your conversations from Fathom using Zapier. This allows you to seamlessly transfer your data and keep your workflows intact in Jiminny.
Migration Guide
Create a Zapier Account if not already existing. Only a monthly plan with sufficient Zaps to migrate the number of meetings is needed.
Generate a Jiminny API Key
You'll need this to connect Zapier to Jiminny so store it securely.Connect Jiminny and Fathom to Zapier using the Connection Wizard.
Create and Publish a Migration Zap
In Zapier, create a new Zap that triggers from Fathom "New Download Video" and passes the action to Jiminny "Upload Conversation". You'll need to map the fields accordingly. Note: you should choose to trigger downloads based on the wider team and not just your user when prompted.Test the Migration by creating a new Download Video in Fathom
Decide the Migration Scope
Consider which data you'd like to migrate over. For example:The period you’d like to cover (e.g. the last 6 months).
The team.
Request the Migration
Ask Fathom Support to bulk create New Download Video for your migration scope, and then a "retroactive Zapier trigger" for the same.
What Gets Migrated?
During the migration process, Jiminny will map Fathom users based on their email addresses. The following data will be copied:
Call metadata (time, duration, customer, attendees).
Conversation transcript with speaker separation.
Playable conversation, including video.
If the user doesn't exist in Jiminny (or hasn’t accepted an invitation), the conversation will not be migrated.
Important: Upon import, Jiminny won’t automatically generate call summaries or action items.
Themes, Topics, and Triggers
During onboarding, we’ll work together to configure your Themes, Topics, and Triggers in Jiminny.
You can export your trackers from Chorus, and we will help convert and import them into Jiminny.
Once your data is imported, all meetings will be analysed by Jiminny’s platform, and statistics and CI data will be available for coaching.