This post is sponsored by Softr. Thanks to Softr for supporting No Code MBA.
Airtable is now part of Bending Spoons. That is worth noting, but it is not by itself a reason to rebuild the systems your team depends on. The practical question is still the same: is Airtable working for the way you need to work?
The short answer
If Airtable is working, your team is moving quickly, and the price and limits feel reasonable, you probably do not need to change anything right now. A rushed migration can create a long list of headaches: broken automations, messy linked records, permission mistakes, retraining, and time your team could have spent on the actual business.
That said, waiting does not mean ignoring it. Make a clean backup, write down the workflows you rely on, and have a simple exit plan. It is boring work, but it gives you options if pricing, support, or the product direction changes later.
When staying with Airtable makes sense
On September 4, 2026, Airtable announced that Bending Spoons had completed its acquisition of the company. Airtable’s announcement says Bending Spoons plans to invest in product, customer support, and go-to-market capabilities. That does not automatically make Airtable a worse product for your team.\n\nStay if your bases are reliable, your automations are doing what they should, and your team is not constantly fighting the tool. A migration should solve a real problem, not just scratch an itch created by a headline.
When Airtable is already getting in your way
A change in ownership can be a good nudge if you already had reasons to look elsewhere. Maybe paying for external collaborators is getting expensive. Maybe your bases are becoming hard to manage. Maybe the interfaces are not flexible enough, or your automations and API setup are starting to feel tight.
For example, Airtable documents a five requests per second, per base API limit. That is totally fine for plenty of workflows. It can become a real constraint, though, when Airtable sits behind a busy customer-facing app.
Here is the useful test: would you be comparing alternatives even if there had been no acquisition news? If the answer is yes, start testing on your own timeline. If the answer is no, back things up and keep an eye on the product instead of rebuilding something that is still working.
You may not need a full migration
You do not have to move every piece at once. One sensible option is to keep Airtable as your data source and improve the app people actually use. Softr can sit on top of an existing data source and give you a branded portal with logins, permissions, pages, and workflows. That lets you test a better customer or client experience before you sign up for a database migration. If you are deciding between tools for this kind of project, check out our guide to AI app builders for client portals.
A simple 30-day plan
Week one: export your key bases and make sure you can actually open the files. Keep copies of attachments too.
Week two: list the things that would hurt if they stopped working. Think automations, integrations, views, interfaces, permissions, and the people who own each workflow.
Week three: pick one annoying workflow and test an alternative. Do not start with the most complicated system in the company.
Week four: decide whether you have a problem worth solving now. If you do, scope a real migration. If you do not, you still leave with better backups and a clearer picture of your setup.
What a safe full migration looks like
Exporting a CSV is the easy bit. The real work is keeping relationships intact, cleaning up duplicate records, moving attachments, rebuilding automations, recreating roles, and checking that the right people can see the right data.
Start with a copy of your data. Write an acceptance checklist before you build. Give yourself a rollback path. And if you are trying to understand the difference between Airtable as a database and Softr as the app layer, read our Softr vs Airtable comparison.
Bottom line
Do not move because a news story made you nervous. Move because Airtable has become too expensive, too limiting, or simply no longer fits the app you need to run. The ownership change is a good reason to make your data portable and understand your options. It is not a reason to panic.
Frequently Asked Questions
Should I leave Airtable immediately?
Probably not. The acquisition is complete, but that alone is not a reason to leave. Back up your work, document key workflows, and compare alternatives only if you have real problems with cost, performance, access, or customization.
Can I use Softr without moving my Airtable data?
Yes. You can keep Airtable as the data source while using Softr for a branded portal or app layer. That is a good way to test a new experience before committing to a full data migration.
What should I back up before considering a migration?
Export your bases and attachments, then document linked tables, views, interfaces, automations, integrations, permissions, and who owns each workflow.
Advertiser disclosure: some links on this website are affiliate links, meaning No Code MBA may make a commission if you click through and purchase.