Can you export a whole Airtable base? CSV, snapshots and limits

1. What can you actually export from Airtable?

Four routes exist and they answer different questions. Only one of them produces a file you can open, and it is the most limited of the four.

2. How do you export an Airtable table as CSV?

Exporting happens from a view, not from the table or the base:

1. Open the base containing the grid view you want.
2. Click the down arrow to the right of the view name.
3. Select Download CSV.

Three constraints are worth knowing before you rely on the result.

It has to be a grid view. Airtable's other view types do not offer a CSV download, so a base organised around a calendar or a kanban still needs a grid view to export from. Creating one is enough - it does not have to be the view anyone uses.

It is web and desktop only. Airtable states that "exporting grid views to CSVs is only available on our web and desktop applications", so there is no way to do this from the mobile app.

The view's filters come with it. The export contains the records the view shows, not the records the table holds. Airtable's own advice is direct: if you want everything, make sure the view you export has no filters on it. This is the single most common way people end up with a partial export and do not notice - the file looks complete because nothing announces the rows that were filtered out.

3. Why is there no "export base" button?

Because a base is not a spreadsheet. Airtable's value is that a record in one table points at records in another - a project links to its client, a task links to its owner, an invoice links to its line items. A CSV has no way to express that. It has rows and columns and nothing else.

So when a linked record field is exported, it flattens: you get the text of the linked records' primary fields, separated by commas, in one cell. The link becomes a string. Reimport that file somewhere and you have the names of the things that used to be connected, but not the connections. Nothing is corrupted and nothing warns you; the structure simply is not in the file.

This is why Airtable asks you to download each table separately rather than offering one button. A whole-base export would have to either invent a format to hold the relationships, or hand you a folder of flat files whose links have already dissolved. It does neither, so it does not offer the button.

One exception exists, and it is priced accordingly. Airtable's eDiscovery API, on Enterprise Scale, does export a base whole: JSON by default, or a URL to a zip containing two CSVs per table, one for the records and one for the comments. Bases are exported one at a time and a request must finish within ten minutes. It is built for legal discovery rather than migration, and it is not available on any other plan.

The practical consequence for everyone else: if your base is genuinely relational, a CSV export is a snapshot of its contents, not a copy of the base. For a single flat table - a content calendar, an inventory list - the export is a faithful copy and this section does not apply to you.

4. What does an Airtable CSV export leave behind?

Airtable is specific about this. Everything visible in the view comes across as a field value, and four things are excluded outright:

• Record-level comments. The discussion attached to a record is not in the file at all. On a base used for collaboration rather than storage, this is usually the most valuable thing lost.
• Field descriptions. The notes explaining what a field is for stay behind, so whoever opens the file inherits column headers with no context.
• Base guide content. Any documentation written into the base itself.
• Data stored solely in extensions. If an extension holds state that is not written back to a field, that state is not exported.

Attachments are a separate and more awkward case. They do appear in the CSV, as a filename and a URL rather than a file - but Airtable notes that "as of November 8th, 2022, attachment URLs obtained via CSV export will expire after a few hours". The column looks populated, the links work while you are testing, and they are dead by the time anyone needs them.

That matters most in the case where an export feels most urgent. If you are exporting because you are leaving, a CSV full of expired URLs is not an archive of your files. Download the attachments you actually need separately, and do it before you close the account rather than after.

5. Why is "Download CSV" missing from my view?

If the option is not where this guide says it should be, it has almost certainly been switched off rather than moved. There are two ways that happens.

You are looking at a shared view. Whoever shared it can prevent collaborators from copying base data, and that setting removes the CSV download along with it. You are not missing a permission on your own account; you are inside someone else's view with copying disabled.

Your admin has blocked exports. On Business and Enterprise Scale plans, Airtable gives admins export controls that restrict CSV downloads, printing, and copying sensitive data. The block can be scoped to non-members with a domain allowlist, or applied to "all collaborators, including internal members" - so an ordinary employee on a paid plan can find CSV export simply unavailable, working as configured.

Neither is something you can work around from the view. If you need the data and the button is gone, the conversation is with whoever administers the workspace.

6. Are Airtable snapshots a backup?

Not in the sense most people mean by the word. A snapshot is a restore point that lives inside Airtable: it is taken automatically based on how much you use the base - roughly daily on an active one, less often on a quiet one - and it lets you roll a base back to how it looked. What it does not do is hand you a file.

How far back you can go depends on the plan. The Team plan keeps 365 days of revision and snapshot history. Enterprise Scale defaults to three years and can be configured up to ten. The free plan is the one to watch: its retention window is two weeks, and Airtable warns that when you downgrade, snapshots outside the new window "are removed and can't be recovered, even if you upgrade later".

One useful detail if you do restore: a base restored from a snapshot loses its revision history, but it does keep record comments - the very thing a CSV export throws away.

So snapshots and exports protect against different things. A snapshot protects you from a bad afternoon. It does not protect you from losing access to the account, because it cannot leave the account. If what you want is a copy you hold, the CSV files and the attachments you downloaded separately are it.

7. How do you move an Airtable base to Excel, Google Sheets, Notion or ClickUp?

Nothing on this list has a dedicated Airtable importer. Every route below is the CSV file from section 2, which means the destination inherits whatever that file already lost - and one rule holds everywhere: a CSV-based migration cannot carry your relationships, because a CSV has no way to express them. What differs is whether that matters where you are going.

Airtable to Excel or Google Sheets

This is where most exports are going, and it is the one case where the CSV is the right tool rather than a compromise. A worksheet is flat and so is the file, so nothing is lost that the format could have carried. In Excel you open the downloaded file directly; in Google Sheets it is File → Import → Upload. Google's ceiling is 10 million cells per spreadsheet, which a large base with many long-text fields can genuinely reach.

Two Airtable-specific things survive the trip badly. Attachment columns arrive as URLs that stop working within hours, so the spreadsheet records the names of your files and no way to reach them. And a linked record field arrives as the text of the linked records' primary fields - which means that if two records share a primary field value, the spreadsheet cannot tell you which one was linked. Neither of these announces itself; the columns look populated.

Airtable to Notion

Notion is the closest thing Airtable has to a peer and it has no Airtable importer - its documented direct imports are Evernote, Trello, Quip, Google Docs, Confluence, Asana and monday.com. The route is CSV, and Notion is blunt about the consequence: a CSV import "can't create new relations", and cannot create rollups or formulas either. The links that flattened into text on the way out of Airtable cannot be rebuilt on the way in; someone recreates them by hand from a file that no longer records what pointed at what.

Two practical limits: imports are capped at 5 MB per file on Notion's free plan and 50 MB on paid plans, and "imports add rows. They don't update existing rows, so watch for duplicates" - so a retry after a failed import leaves two copies rather than a corrected one. If you are weighing the two tools rather than committing, it is worth knowing what comes back out the other side: exporting from Notion has its own set of trade-offs, and only one of its formats carries your comments.

Airtable to ClickUp or Asana

Neither has an Airtable importer either. ClickUp routes you through its Spreadsheets Importer, which accepts .csv along with .xls, .xlsx, .xml, .json, .tsv and .txt and maps your columns onto ClickUp fields; ClickUp is clear that Airtable automations, linked-record formulas and scripts are not importable and have to be rebuilt. Asana's CSV import reads task name, description, section, assignee and collaborators, which an Airtable export maps onto reasonably well - but the loss there is upstream rather than in Asana, because Airtable's CSV omits record comments entirely.

Both are worth a pilot with one table before committing the base. The thing to check afterwards is not whether the rows arrived - they will - but whether anything depended on a link, a rollup or a formula, because those are what the file could not carry.

Destination importers were checked against each vendor's documentation on August 13, 2026.

8. How do you move an Airtable base into Breeze?

If the goal is to run the work somewhere else rather than to archive it, the CSV route works against you: it is the one path that has already dropped the comments and dissolved the links before the destination ever sees the data. Any tool that imports from a spreadsheet inherits those losses, however good its importer is.

Breeze reads your Airtable account directly instead. It connects with read access, shows what it is about to do, and leaves everything in Airtable untouched - and because it reads the API rather than a spreadsheet, it brings across the record comments that the CSV export excludes.

Choosing which field becomes your columns

Airtable does not tell an importer which field holds your statuses, because in a base that is just another field. So Breeze asks. Whichever field you pick becomes the columns of the Breeze board, which means a table with a Status or Phase single-select turns into a working board rather than an undifferentiated list.

Running the import

In Breeze, open the menu in the top-right corner, select Settings, open the Import tab and select Import next to Airtable. The wizard runs in five steps: connect, choose the tables, pick the field that becomes your columns, match people, and review before anything is written.

Only a Breeze account owner or admin can import a whole workspace as new projects. Importing a single table into a project you already have works from that project's settings instead.

What comes across from Airtable

Two honest limits. Airtable's attachments are skipped rather than linked, for the same expiry reason that makes the CSV column useless - so download anything you need to keep before you close the account. And because Airtable has no notion of a subtask, there are none to bring across.

Large imports keep running in the background, and Breeze emails you when they finish and tells you what it could not bring. Importing the same table again offers to update the project it created last time rather than making a second copy, and it never deletes what you have added in Breeze.

Still deciding rather than moving? Compare the practical differences in Breeze vs Airtable, or look at other Airtable alternatives. Exporting is worth doing even if you stay - it gives you a copy you hold and shows you which parts of your base are portable.

Common questions about exporting Airtable data

Does an Airtable CSV export include attachments?

Only as a filename and a URL, and those URLs expire a few hours after the export. The files themselves are not in the download, so save anything you need separately.

Can you export Airtable from the mobile app?

No. Airtable says exporting grid views to CSV is available only on its web and desktop applications.

Does Breeze need an Airtable CSV file?

No. Breeze connects to Airtable with read access, so it never touches an export file - which is why it can bring across record comments that a CSV leaves behind.

A CSV is a copy of your data, not of your base

Use a grid view CSV for a spreadsheet or a report, and remember it holds field values and nothing else. Use snapshots to undo mistakes, not to keep a copy. Download attachments yourself before you need them, because the links in the file will not wait.

And if you are moving the work rather than filing it, skip the file. See exactly what Breeze imports from Airtable, then try it with one table before you move the rest of the base.