Guide · Undo a bulk edit
How to undo a bulk edit in Airtable
A paste landed one column off. A find-and-replace matched more than it should. An automation ran on every record instead of the new ones. The records are all still there, but a field now holds the wrong thing. Here's how to get the old values back, quickest first.
Last updated October 15, 2026
First: stop it happening again
If an automation did it, turn the automation off before anything else, or it may run again while you're fixing things. The same goes for an integration or a script that writes to the base on a schedule.
1. Undo, if it was you, just now
Ctrl+Z (⌘+Z on a Mac) reverses your own recent actions in the base you have open, a big paste included. It can't reverse an automation run, a script, an API integration or a teammate's edit. If undo doesn't bring it back, move on to the next step rather than undoing other work trying.
2. A handful of records: revision history
Expand a record and open its revision history: the earlier value is there, with who changed it and when. Copy it back by hand. History is kept for 2 weeks on Free, 1 year on Team, 2 years on Business and 3 years on Enterprise Scale. It's the right tool for five records and a slow one for two hundred, because each record is opened on its own.
3. Many records: get a copy of the column from before
You need the field's old values for every affected record, in one place. Two ways to get them:
- A snapshot from before the edit. Restore it as a new base (restoring never overwrites the original), open the table there, and you have the old column. See how snapshots work for the steps and how long each plan keeps them.
- An outside copy from before the edit, such as last night's backup as a CSV. This also works when the snapshot you'd need has expired, or when you're on a plan that keeps them for only 2 weeks.
4. Put the old values back without retyping
Paste the column back
- In the old copy, make a view with a unique field (an ID, an email, an order number) and the overwritten field, sorted by the unique field.
- In your live table, make the same view: same unique field, same sort, and a filter that shows exactly the affected records and nothing else.
- Check that the first few and last few rows line up in both. If the counts differ, stop: something was added or deleted since, and a paste would land on the wrong rows.
- Copy the old column and paste it over the live one, starting at the first row.
- Spot-check a few records against the old copy.
Or merge from a CSV
On a paid plan, the CSV import extension can merge rows into existing records, matched on a field with unique values. Export the old copy to a CSV with just the unique field and the overwritten field, then import it with merge turned on. It only touches the field you include, and it handles thousands of rows at once (up to 25,000 rows and 5 MB per file). The CSV restore guide covers the import in detail.
One caution for both: paste or merge only the field that was damaged. Bringing back every column would also undo the good edits people made since the old copy was taken.
Before the next one
- Take a manual snapshot before a big import, a bulk update or an automation you've just written. It costs a click.
- Test new automations on a copy of the base, or on a view filtered to one test record, before pointing them at the real thing.
- Add a “Last modified by” field to tables that matter, so you can see who or what touched a record last.
- Get told the same day. A bulk edit found the next morning is a quick fix; one found three weeks later has three weeks of good edits mixed in.
How Nightclerk handles it
Every night's backup is compared with the night before. When one field changes on 25 or more records that are at least 30% of a table, or on 200 or more records in any table, you get an alert by email or Slack. It names the field, how many records changed, how many were left empty, and a few “before → after” examples. Deleting a field that held values on that many records counts too, since Airtable's trash keeps a deleted field for only 7 days. The receipt lists every changed record with its old and new value, and the warning has two buttons: one downloads that field's old values for just the records that changed, as a CSV ready to paste or merge back; the other opens the table as it was the night before. You can click through a month of receipts on a sample base without signing up.
Questions
Can I undo an Airtable automation?
Not with an undo button. Undo only covers your own recent actions. To reverse an automation's changes, take the earlier values from each record's revision history, from a snapshot restored as a new base, or from an outside copy, then paste or merge them back.
How far back can I get old values?
Record revision history goes back 2 weeks on Free, 1 year on Team, 2 years on Business and 3 years on Enterprise Scale. Snapshots are kept for the same periods. An outside backup keeps whatever its plan keeps.
Does Airtable warn me when many records change at once?
Not by itself. You can build an automation that emails when a record is updated, but it runs once per record and can't tell one edit from three hundred. A daily backup that compares each day with the last can.
Will pasting old values back change the records' history?
Yes, it's a new edit like any other: each record's revision history will show your paste as the latest change, with the earlier values still listed below it.
Sources, checked October 15, 2026: Airtable: record revision history · Airtable: taking and restoring base snapshots · Airtable: CSV import extension. Nightclerk is not affiliated with Airtable. Compare backup options.