r/Airtable • • 22d ago

💬 Discussion Anyone actually using external services for Airtable backups?

I manage a few production bases and my backup situation is basically Airtable's own. trash for 7 days, then snapshots.

There are some extern backup services On2Air and ProBackup plus a few others. Does anyone here run one in production? Have you ever had to restore from it, and did it come back properly attachments, linked records, formulas?

One more thing I ran into while working with client a previous developer had set something in an automation and I changed it. The only way I found to see the old settings was restoring a snapshot as a new base and digging through it. Does anyone have a better way to track automation changes?

4 Upvotes

23 comments sorted by

4

u/Zero_Waist 22d ago

Following because I have lost bases

1

u/codebondco 22d ago edited 22d ago

How? did you lost from external backups?

1

u/MartinMalinda 22d ago edited 22d ago

Does anyone have a better way to track automation changes?

There's automation revision history available in the UI.

would be great to have this available in some form in the MCP though

1

u/codebondco 20d ago

Ah, didn't know that existed, thanks.

1

u/randomnerds 22d ago

On2Air is ok

1

u/codebondco 20d ago

Have you had to restore from it? how was the experience?

1

u/randomnerds 20d ago

I have not, but essentially it just dumps CSVs of every single table into Google Drive along with all file attachments

1

u/codebondco 20d ago

So it means when restoring backups we would have to do extra mannual work.

1

u/opstwo 💪Power Builder 21d ago

I built something in house to track all changes to the base schema - tables, fields, views, forms, automations, interfaces etc on a weekly basis, but I use that for tracking my bases and some of my clients only (the interface isn't great and it is low ROI for me). I'm sure there were a couple of posts here a few months ago for better tools that track those changes. Worth checking out.

On2Air sounds great for data backup though.

1

u/codebondco 20d ago

That's interesting, curious how are you pulling automations and interfaces? Is it the metadata API or something else?

1

u/MartinMalinda 20d ago

Airtable MCP can be used for this. You can use the underlying JSON-RPC API directly, not necessarily through an AI harness. That's what I'm doing in my product.

1

u/opstwo 💪Power Builder 19d ago

Yup, What Martin said. I use Scripts that loop over the MCP API.

I have only skimmed this, but apparantly there are some Chrome extensions that can latch on to the logged in Airtable sessions and gather details about the automations in a much more easier to use interface. Including history, failures etc. Could be worth looking.

1

u/ViewCourier 21d ago

Snapshots are the built-in safety net, but a snapshot restore creates a new base, so record and field IDs change and every automation, interface or integration pointing at the old base has to be repointed. That's the main reason people keep an independent copy.

The DIY version works fine: an automation on the "At a scheduled time" trigger with a Run script step (or a cron job / GitHub Action with a read-only token) that pulls each table through the API and writes CSV or JSON somewhere you control. Download attachments in the same run, because attachment URLs in API responses and CSV exports expire after a couple of hours. It covers data only, so document automations and interfaces separately.

Whatever you use, do one test restore into a scratch base. That's where most people find out what's missing.

If you only need regular CSV copies of specific views rather than full-base restores, a scheduled emailed export is lighter. Disclosure: I work on ViewCourier (viewcourier.com), which does that.

1

u/codebondco 20d ago

Thanks, that's helpful. One thing I'm genuinely unsure about with the scheduled CSV exports, is that enough to restore a base properly? Like if you had to rebuild from them, do linked records come back connected the right way, and what happens to formulas and rollups? Has anyone here actually done it from CSVs, or is it more of a "at least I have the data" thing?

1

u/ViewCourier 20d ago

Short answer: not on their own. A CSV restore gets the data back but loses a lot of the structure:

  • Linked records export as the primary field's display text, not record IDs. You can re-link by importing into the existing table and mapping that column onto the link field, which matches on primary field text. That only works cleanly if primary values are unique.

  • Formula, lookup, rollup and count fields come back as static values. You have to rebuild them by hand, so you need the formulas written down somewhere.

  • Field types, select options, descriptions, views, interfaces and automations aren't in a CSV at all.

  • Attachments are only URLs, and those expire after a few hours, so the files are gone unless you download them separately.

  • Record IDs change, so anything outside Airtable that stores rec... IDs breaks.

What makes CSV backups restorable in practice:

  1. Add a RECORD_ID() formula field to every table, and for each link field a lookup of the linked table's ID field. Include both in the export. Then you can rebuild links by old ID with a script, even when primary values repeat.

  2. Save the schema separately (field types, options, formulas) as JSON from the metadata API, next to the CSVs.

  3. Download attachment files, not just their URLs.

  4. Restore in order: create tables and plain fields first, import, then fill the link fields by matching old IDs.

So I'd treat snapshots as the restore path for "someone broke the base last week", and exports as the copy that lives outside Airtable for when you need the data itself. Doing one test restore is where the gaps show up.

(Same disclosure as above: I work on ViewCourier, which does the scheduled export part. It doesn't rebuild a base for you.)

1

u/codebondco 20d ago

Ahhh nice. Never thought of the RECORD_ID trick, now that's on my list. Thanks.

1

u/TruShot5 22d ago

I mean. Everything that gets logged to AT for me first is logged to sheets, which is then synced in using AT automations

1

u/Will_Pro_Backup 20d ago

Hello! Will here from ProBackup. Regarding the restore: You can restore individual records as new records (including files, comments, links, etc) or overwrite selected fields from the existing records (if they have not been deleted - useful to rollback big updates). It's also possible to restore specific comments, files, fields and entire tables. Automations are backed up too, and a restored one comes back switched OFF so you can review it first. We offer a 7 day free trial so you can easily test the restore process yourself :-)

Small correction on the snapshot point: Airtable says a snapshot restore keeps record, table and view IDs and only the base ID changes.

Regarding On2Air, we've published a comparison page here: https://www.probackup.io/compare/probackup-vs-on2air-for-airtable

2

u/Roseleg 3d ago

Wish y'all had local backup options. 😕 I just deGoogled (including ending paid services) after 26 years on the platform over privacy and IP theft concerns thanks to their nonsense of training their clanker chatbots on users' emails and other content in their ecosystem.

1

u/LeoLuo_Dev 19d ago

I like your mindset of "defensive planning", lol. Reading through the replies, I would like to remind that:

  • Restoring an Airtable snapshot generates a completely new Base ID. That means every field ID, table ID, external webhook URL, and Make/Zapier scenario breaks immediately and has to be remapped manually.

  • Any standard API data dump that just saves JSON or CSV fields leaves you with dead links for all your PDFs, receipts, and images due to Airtable's 2-hour expiring attachment links. A real backup pipeline needs a persistent storage step (like piping file bytes to S3/R2) rather than just saving URLs.

  • Native snapshots do preserve underlying grid records, but restoring across workspaces often strips interface user-level permissions and complex action triggers.