Skip to article
Bridge

Bring historical transcripts into Bridge without losing their context

Pick an import path based on what you need: a batch of past meetings, ongoing transcript sync, or one existing file. After importing, check the records and keep the context needed to read them correctly.

Decide which history is worth bringing over

Start with the job the old conversations will do. Are you collecting the decisions behind a current project, preparing a handoff, or putting all meeting records in one place? Importing every transcript you have can bury the history that matters.

For a customer rollout, start with the meetings that set scope and delivery conditions. Note which ones are missing. A collection with known gaps is more useful than one that only looks complete.

Choose connected import, sync or a one-off file

Bridge imports from Granola, Fireflies, Fathom, Zoom cloud recording transcripts and Google Meet transcripts. Connect in Account settings → Integrations → Notetakers. Choose how far back to import and whether to sync future transcripts. Imported meetings appear in Meetings → Completed.

With sync on, new transcripts arrive daily. Disconnect the source to stop. For a single file or a block of text, use New and choose upload or paste.

Your needPath to consider
Bring in a collection from a supported sourceConnected import with a chosen history range
Keep future transcripts coming from that sourceImport plus future sync
Bring in one recording or transcriptOne-off upload
Bring in existing textPaste the transcript (up to 20,000 characters)

Know what each path needs

Check what each source brings before you rely on it, and keep anything else you need in the original tool. If your source isn't on the list, use a one-off upload rather than expecting an automatic connection.

  • Uploading audio, video or transcript files, and pasting transcripts, needs a paid plan. Free users can still connect supported notetakers.
  • Pasted text can be up to 20,000 characters. Check the supported file formats before you prepare a file.
  • Granola, Fireflies and Fathom bring transcripts and notes. Zoom and Google Meet bring transcripts only.
  • You choose the history range when you connect, from the past month to all time.

Check the imported conversation before using it

When you upload or paste, Bridge shows the content for review and saves it to your meetings straight away. Look at the result. A meeting card existing doesn't mean the text is complete.

Check that the conversation matches the right event, includes the key decision and has sensible speaker labels. “We can do that next week” still needs to say who spoke and when. Importing can't make a vague commitment clear.

  • Compare a sample passage with the original.
  • Keep proposed dates apart from agreed dates.
  • Note any part of the conversation that's missing.

Keep the meaning of old decisions

In the rollout example, “we chose a staged launch” means little without the reason. Was it temporary while an approval was pending, or the final plan? Read the surrounding discussion before using an old decision to justify new work.

If a later meeting changed the decision, point readers to it. Old transcripts show what people said at the time, not what the plan is now.

Make the history easy to find

Once you trust the records, organize them around how colleagues will use them. A small project collection may be enough for a handoff. Add consistent labels when they make searching clearer.

If you turned on sync, check now and then that new arrivals still serve your purpose. More records only help if people can find the right one and understand its limits.

Sources & further reading