The export button works today. It might not work the day you actually need it.

Nobody reads a notetaker's export documentation on the day they sign up. They read it, if they read it at all, on the day they are already leaving — usually with a renewal date already visible on a calendar and less patience than the process deserves. That is backwards, and it is the single most common reason people lose something they did not mean to: not because a vendor deleted it maliciously, but because the export had a plan gate, a format gap or a time limit nobody checked until it was already a problem.

What usually carries across, and what usually does not

Every cloud notetaker is different in the specifics, but the shape of what survives an export and what does not is close to universal across the category:

The right column is the one worth reading twice. A transcript exported as a plain file is genuinely portable — any text editor, any future tool can open it. A cross-meeting search index, a CRM record that got written to automatically, or a shared team folder is not something any export reconstructs; it is a property of the service you are leaving, and it ends when your relationship with that service does.

Three tools, checked the same day, three different shapes

The specifics differ enough between vendors that a general warning is not enough on its own — the actual mechanics matter. Three are worth naming because their export processes were checked directly for this library and each catches people in a different way.

Full detail, sequencing and links for each of these three are in their own pages: migrating from Granola, migrating from Otter, and migrating from Fireflies. For a tool not named here, the principle is the same even though the exact mechanism will differ: find that vendor's own export or data-request page, read it before you need it, and check whether your specific plan tier is gated out of any part of it.

The audio is the part people forget

Of the three checked above, one — Granola's CSV — does not include the original audio at all; it is text only, the summary and the transcript inside a spreadsheet column. Otter's export can include an mp3, but only as one format choice among several, easy to skip if you are only thinking about the words. Fireflies' per-meeting download offers mp3 directly, and its account-wide export bundles both mp3 and mp4 automatically.

The pattern across all three is that the transcript is the thing people remember to ask for, because it is the thing they read. The audio is the thing that actually settles a dispute about an exact wording, a tone, or a specific commitment, and it is disproportionately likely to be the file nobody thought to pull. If any meeting in your history has a legal, clinical or contractual reason the original recording might matter later, treat that one specifically — confirm the export includes audio, not just text, before the account it lives in closes.

Plans gate features, and free tiers are gated hardest

Fireflies' own knowledge base states plainly that per-meeting downloads require a Pro plan or higher — a free-plan account does not get the download option on an individual meeting at all, and has to use the separate account-wide request instead. That is not a hidden trick; it is documented, but it is the kind of documentation nobody reads until the day they need the button that is not there.

The general lesson is not specific to Fireflies: before assuming an export works the way a paid user's screenshot in some other article shows it, check what your own plan tier actually includes. A downgrade, a trial that reverted to free, or a team plan a company controls can all mean the export path available to you is narrower than the one most documentation assumes.

Links and windows expire

Fireflies' account-wide export link is valid for seven days once it arrives, and processing itself takes 24 to 48 hours before that clock even starts — meaning the practical window from request to a working file, worst case, is closer to nine days than one. Granola's export email link is valid for 24 hours, with one export allowed per account per day, so a missed window means waiting until the next day to try again, not the next hour. Neither of these numbers is unusual for the category; time-limited links are the normal design, and the way people get caught by them is requesting an export the day a subscription is scheduled to end rather than a week or two before.

The general rule this suggests: whatever cancellation date is on the calendar, request every export at least a week ahead of it, and treat the first attempt as the one that might fail — a spam-filtered confirmation email, an expired link, or a plan that turns out not to include the feature you assumed it did. A week of slack turns any of those into a minor delay instead of a permanently missed archive.

Team and seat accounts need a different order

A solo account is a straightforward export-then-cancel. A shared or team account is not, for a reason that shows up in more than one vendor's own documentation: exports are frequently scoped to the person doing the exporting, not the whole organisation. Granola's own policy is that nobody, including a workspace admin, can export a colleague's notes on their behalf outside its Enterprise tier. A removed seat, in most of these tools, cannot retroactively generate the export it should have made before it was removed.

If a team is leaving a tool together, the order that avoids losing anything is: every person exports their own history first, while every seat is still active, and only once every export is confirmed does anyone start removing seats or cancelling the plan. An admin doing a single export at the end, after seats are already gone, is the most common way a team loses a departed colleague's meetings permanently.

Admin rights over a colleague's meetings are not consistent either

The team-account problem above has a second layer worth naming: even while everyone's seat is still active, what one person can export on another person's behalf differs by vendor and is not something to assume. Granola's own policy is that nobody — including a workspace admin — can export a colleague's notes on their behalf outside its Enterprise tier, so a departing employee has to run their own export before their seat is removed, full stop. Fireflies takes a different approach: its own knowledge base states a workspace admin can download the transcript, summary, audio and video of any meeting recorded in the workspace, but only meetings whose privacy setting the admin can actually see — a meeting marked private to its owner or restricted to a channel stays out of reach regardless of admin status.

Neither shape is wrong, and neither is safe to assume applies to a third tool you have not checked. The practical consequence is the same either way: find out, while every seat is still active, whether an admin can rescue a departing colleague's meetings after the fact or whether that window closes the moment the seat does. If the answer is the latter, the departing person's own export has to happen before anyone touches their access, not after.

The sequence, whatever tool you are leaving

1. Find the export mechanism before you need it. Every vendor's help documentation has a page for this; read it now, not on the day of cancellation.
2. Check what your specific plan includes. Some downloads are gated by tier, and assuming a free plan works the way a paid plan's documentation describes is the single most common mistake.
3. Export the audio, not only the transcript, for anything where the exact recording might matter later — a client commitment, a quote, an interview. If the export format is text-only, decide now whether that is acceptable for those specific meetings.
4. Request every export with at least a week of runway before any scheduled cancellation, so an expired link or an unread confirmation email is a delay rather than a loss.
5. On a team account, get everyone's individual export done first, before any seat is removed or the plan is downgraded.
6. Verify the export before you cancel anything — open a few files, check the count against what you expected, and only then close the account.
7. Start the next tool on a real meeting, not a test recording. Whatever comes next, the switch is only proven by using it on something that actually matters.

Plain formats outlast the app that made them

One more pattern is worth naming before the sequence, because it changes which export option to pick when a tool offers more than one. A proprietary export — a format only that vendor's own app can reopen, or a bundle that depends on a companion tool to make sense of — is only as durable as your willingness to keep that companion tool around. A plain text transcript, a standard PDF or DOCX, and an ordinary MP3 or MP4 will all still open on whatever computer you own in five years, independent of whether the vendor that produced them still exists.

Given a choice between an export format built around a specific viewer and a plain one, take the plain one, even if it looks less polished. The convenience a vendor's own viewer adds is real but temporary — it lasts exactly as long as your relationship with that vendor does — and the whole point of exporting before cancelling is to stop depending on that relationship at all.

What none of this replaces

Exporting your own files is not the same question as what a vendor already did with a recording before you asked for it out. A training policy, a retention window, or a sub-processor list is a separate thing to read on that vendor's own site if it matters to you — an export settles what you can walk away with, not what already happened while the account was open. See what happens to recordings when an app shuts down for the harder version of this question, when the vendor itself is the one disappearing rather than you cancelling on your own terms.

None of this is a promise about what any specific vendor's export will contain by the time you read this — prices, formats and plan gates change, and the right move is always to check that vendor's own current documentation on the day you actually need it, not a description written before.

Where the export goes afterward

Once the files are saved, they need somewhere to live that does not depend on the next tool's own account system either. If the destination is Coii AudioNotes, there is nothing to import the old export into — new recordings become files in a folder from the moment they are made, with no account, no subscription and no future export request standing between you and them. The old export stays exactly where you put it, readable on its own, permanently. Compare the full detail for Granola , Otter or Fireflies if you have not settled on where you are moving to yet, or download Coii AudioNotes and try the next thirty days of meetings before deciding anything about the ones already exported.