Skip to main content

How to: a hacky work around for Airtable record limits using synced bases

  • February 28, 2026
  • 1 reply
  • 21 views

TheTimeSavingCo
Forum|alt.badge.img+31

I faced this problem as we had to track daily metrics for each employee, which ended up generating dozens of records a day.  This became a problem pretty quickly for obvious reasons

As a workaround, I ended up setting up a system to archive the old data while leaving the original base alone, and the steps are pretty much:

  1. Create a new base for archiving purposes
  2. Create a synced view and sync it to the new base
    1. In the sync settings, toggle on ‘Leave records when they are deleted or hidden in the source’
  3. Create a heartbeat in the destination base
    1. This is important as syncs only happen on bases that have activity on them
  4. Set up an automation in the main base to delete the old records


---

1. Create a new base for archiving purposes

I’m pretty sure everyone knows how to do this one, so I’m just going to skip it heh

 

2. Create a synced view and sync it to the new base

  1. Click ‘Share and sync’
  2. Click ‘Sync data to another base’
  3. Toggle on ‘Allow data in this view to be synced to other bases’
  4. Optional but recommended: Set a password for this shared link
  1. Copy the shared view link:

     

  2. In the archive base, set up the sync and toggle on ‘Leave records when they are deleted or hidden in source’
    1. This way we can delete records from our main base without worrying about it

 

3. Create a heartbeat in the destination base

The only thing we’re trying to do here is make sure the base has activity on it so that it’ll sync over any new data from the source, and so we can do this any way we want, really

I usually just set up an automation that runs once a day, and its action is to update a date field with that date.  And so I have a table with one record in it and a Date field:

And an automation that fires once a day to update the Date field with the current Date:

 

4. Set up an automation in the main base to delete the old records

In the main base, create an automation that runs on a schedule and its actions will be to find the records that aren’t useful anymore and delete them.  To do this, you’ll use an automation with a ‘Find Record’ step to get those records, followed by a ‘Run a Script’ action to delete them

To set up the ‘Run a Script’ action, we’ll first add in two input variables:

  1. recordIds: The record IDs of the records we found with the ‘Find Record’ step:
  1. tableId: The table ID of the table we’ll be deleting records from:

And for the script, we’ll just paste this in:

let {recordIds, tableId} = input.config()

while (recordIds.length > 0) {
await base.getTable(tableId).deleteRecordsAsync(recordIds.slice(0, 50));
recordIds = recordIds.slice(50);
}

And that’s it!  Let me know if you encounter any issues and I’ll do my best to help!

1 reply

ScottWorld
Forum|alt.badge.img+35
  • Genius
  • February 28, 2026

Yes, very cool workaround but one key thing to note:

The new base will have the same exact record limits as the old base.

So, depending on how many records an organization is archiving, this new base may not be able to serve as their “forever archive” because it simply doubles the amount of records allowed by distributing the total set of records across 2 bases.

Once they get to 2x the record limit, then a 3rd base needs to be introduced. Once they get to 3x the record limit, then a 4th base needs to be introduced. And so on.

Once they get to that point, then they will be forced to search through multiple different archive bases to find the records they’re looking for, which makes things more challenging.

Now granted, there are probably very few organizations that would ever reach 2x their original record limit, but it happened to a large client of mine who is processing tens of thousands of records every single month.

Before they started working with me, they went down the path of dividing up all their archived records across multiple bases and it became a real hassle for them to track down archived records.

So, in their case, I set them up with an automated archiving solution using Make’s Airtable integrations and Make’s Google Sheets integrations, which automatically archives their records to a single Google Sheets spreadsheet every night.

So all of their records are now combined into one unified spreadsheet for easy searching purposes.

Once again, this would likely only happen to a small percentage of organizations, but it’s good for larger organizations to be aware of this limitation.

- ScottWorld, Expert Airtable Consultant