CommunityHire an ExpertSign Up
Start HereMigrate from Airtable

How to migrate from Airtable to Softr

Move your Airtable data and automations into Softr Databases, and migrate an existing Softr app that runs on Airtable.

Softr gives you two ways to move off Airtable, both from Migrate from Airtable in the left sidebar of Softr Studio. Pick the one that matches your setup:

Why switch to Softr Databases

Built to run operations at scale

Airtable performance can degrade as record counts, formulas, and linked data grow. Softr Databases are designed to manage data and power apps at scale, so systems stay fast and reliable as operations expand.

Scale without API limits

Softr Databases are native to the platform, so there are no external API rate limits throttling your app as your data and traffic grow. Record and storage limits scale with your plan.

Real business apps, not just data views

When you need logins, user roles, granular permissions, workflows, and flexible design, Softr gives you everything you need to turn your data into custom business apps.

No per-seat pricing or hidden costs

Airtable charges per seat and has strict record limits, even on its high-tier plans. Softr offers generous user and record limits without per-seat costs, which makes it easy to share apps across teams and clients.

Smarter AI Agents

Database AI Agents can trigger on record creation, on specific field updates, and on custom conditions, a level of control that isn’t available with external sources.

Your automations come with you

Airtable automations import as Softr workflows, which connect to tools like Slack, Gmail, HubSpot, QuickBooks, and DocuSign.

Before you start

A few minutes of prep saves a lot of rework later, whichever path you take.

1. Rehearse on a copy

If your base is large or business-critical, duplicate it in Airtable with a small amount of data and run the import on that first.

2. Clean up in Airtable first

The import brings your base across as it is. Merging duplicate tables, removing fields you no longer use, and fixing field types is easier before you migrate than after. See Lessons from a real migration.

3. Check your Airtable API allowance

Softr reads your base through Airtable’s API, so every migration uses your Airtable plan’s API calls. If your Airtable account has hit its API limit, the import can’t read the base and stops. Larger bases also take longer to import.

4. Know what needs a second look

Most fields, including linked records, attachments, and formulas, come across automatically. A few behave differently in Softr. See What transfers, and what to double-check.

Lessons from a real migration

Base Flows, the Softr agency that moved Child’s Play Charity off Airtable, migrated 4,000+ records in three weeks. These are the lessons from that project, and most of them are decisions you make before you import anything.

  • Consolidate redundant tables first. Merging separate tables that hold the same entity into one is usually the single biggest fix for duplicate records.
  • Dedupe before the migration, not after. Match suspected duplicates against a unique identifier, such as a tax ID or an account number, before anyone touches the new database. Names alone are misleading.
  • Fix field types on the way in. Numbers stored as text in Airtable will break rollups, sorting, and formulas once they’re live.
  • Freeze, don’t sync. A short data freeze with a manual catch-up list is simpler and safer than running a temporary Airtable-to-Softr sync.

Migrate your data and automations

Use this path to move an Airtable base into Softr Databases. Softr creates a new database with a copy of your tables, fields, and records, and brings your Airtable automations across as Softr workflows.

Import your Airtable base

Open Migrate from Airtable

In Softr Studio, click Migrate from Airtable in the left sidebar. On the Import base tab, click Import base.

Migrate from Airtable page in Softr Studio, with the sidebar item marked 1 and the Import base button marked 2

Migrate from Airtable in the left sidebar, and the Import base button.

Choose your Airtable account and base

In the Select data to import dialog, pick a connected Airtable account under Account, or choose Connect new account to add one. Then select the base under Base. The whole base is imported, along with any automations Softr finds in it.

Select data to import dialog showing the Account and Base dropdowns and the note that any automations found will also be imported

The Select data to import dialog, with an Airtable base selected.

Start the import

Click Start import. The base appears in the Import base list with the status Importing. Larger bases take longer, so give it a moment to finish.

Review the new database

When the import finishes, open the new database and work through the review checklist. It lists anything that didn’t carry over exactly, how to fix each item, and links to the field in Airtable. Then spot-check record counts, linked records, and attachments.

The import failed

A failed import shows Failed in the Import base list. Hover the retry icon in that row to see why, then click it to try again once you’ve fixed the cause.

  • This base could not be read - check that the Airtable connection still has access to it. Check that the base still exists and that Softr has access to it (see the note in step 2). This also happens when your Airtable account has used up its API calls; wait for the allowance to reset or upgrade your Airtable plan, then retry.
  • Could not read this Airtable account’s bases. The connection is no longer authorised or its token could not be refreshed. Reconnect the Airtable account from Integrations, then try again.

For other Airtable errors, see Troubleshooting Airtable Errors and Airtable API call limit exceeded.

What transfers, and what to double-check

Most Airtable fields map to an equivalent Softr field and keep their values and settings. The fields below need a closer look after the import, and most of them appear in the review checklist.

Airtable fieldIn SoftrWhat to check
Single line text, Long text, Number, Currency, Percent, Duration, Email, Phone, URL, Attachment, AutonumberMatching field typeNothing. Values and settings carry across, and attachments are copied into Softr’s storage.
Single select, Multiple selectSelectNothing. Options keep their order and colors.
Checkbox, RatingCheckbox, RatingNothing. Icons and colors carry across.
Date, Date and timeDateThe time zone carries across, but Airtable’s display format (US, European, ISO) doesn’t.
Long text with rich textLong text (Markdown)Formatting comes across as Markdown. Images and @mentions inside the text don’t.
Created time, Last modified timeCreated at, Last updated atAirtable’s original timestamps are kept, and Last modified keeps the fields it was watching.
Created by, Last modified by, CollaboratorCreated by, Last updated by, UserPeople come across by name and email. Invite them to your workspace and the fields link to their accounts.
Link to another recordRelated recordLinks are preserved. If you limited which records could be linked, that condition doesn’t carry over.
FormulaFormulaSoftr uses Airtable-compatible syntax, so most formulas work unchanged. Rewrite any that the checklist flags as using an unsupported function. See the Formula glossary.
LookupLookupAirtable doesn’t expose a lookup’s filter, sort, or limit, so a lookup may show more values than it did in Airtable. Compare a few records.
RollupRollupAirtable doesn’t expose the rollup’s calculation, so Softr works it out from your data. Confirm the result and add back any filter.
CountRollup (count)A count that only counted some linked records in Airtable will read higher. Add the condition as a rollup filter.
AI fieldField with an AI agentThe generated values come across. Check the prompt before turning the agent on.
Button, BarcodeNot migratedAdd a URL or formula field if you need the button’s link in Softr.

Review your imported automations

Each Airtable automation comes across as a draft workflow in Softr. Drafts don’t run until you turn them on, so nothing fires while you’re still checking.

For each workflow:

  1. Open it and fix any step marked Step incomplete.
  2. Check that the trigger and each step point at the right table and fields in your new database.
  3. Test it, then turn it on.
  4. Turn off the matching automation in Airtable, so the two don’t both run.

A few parts of an Airtable automation need rebuilding rather than reviewing:

  • Scripts. A Run script step becomes a Run custom code step, but Airtable’s scripting API doesn’t exist in Softr, so the script itself needs rewriting.
  • Steps with no Softr equivalent. Actions for tools Softr doesn’t connect to, such as Microsoft Teams, GitHub, or Outlook calendar events, can’t be recreated as-is. Rebuild them with another integration or a Call API step.
  • Scheduled triggers. Check the schedule and time zone of any At scheduled time trigger.

Build your app on the new database

Your data now lives in Softr Databases. To put an app on top of it, create or open an app and connect its blocks to the new database. If you already have a classic Softr app on Airtable, use Migrate an existing Softr app instead.

Migrate an existing Softr app

Use this path if you have a classic Softr app that reads its data from Airtable. Classic apps are the apps created before November 2026, and they show a Classic tag in All projects. Softr moves the app to Softr Databases in three steps:

  1. Import Airtable data to Softr Databases. Softr imports the tables your app uses, and the tables they link to. Each Airtable base becomes its own Softr database.
  2. Duplicate your app. Softr makes a copy of your app. The original stays unchanged.
  3. Connect data to app. Softr updates the copy to use the new Softr databases.

Start the migration

Choose the app

Click Migrate from Airtable in the left sidebar, open the Migrate app tab, and click Convert app. Under App, select the app you want to migrate, then click Convert app. Only apps that use Airtable as a data source are listed.

Migrate from Airtable page on the Migrate app tab, with the tab marked 1 and the Convert app button marked 2

The Migrate app tab and its Convert app button.

You can also start from the app itself:

  • When you open the app, Softr can show the Migrate this app from Airtable to Softr Databases dialog.
  • In the left sidebar of the app editor, click Migrate.
  • In the Data tab of the app editor, open an Airtable base and click Migrate to Softr Database.

Data tab header for an Airtable base, with the Migrate to Softr Database button outlined

The Migrate to Softr Database button in the Data tab.

Start the migration

In the Migrate this app from Airtable to Softr Databases dialog, click Start migration.

Migrate this app from Airtable to Softr Databases dialog with the Start migration button outlined

Click Start migration to begin.

Wait for the three steps to finish

Softr shows each step as it runs. The migration can take a few minutes, and Softr lets you know when the copy is ready to review.

Migrating dialog listing Import Airtable data to Softr Databases, Duplicate your app, and Connect data to app

The migration runs in three steps: import the data, duplicate the app, and connect the data to the copy.

If the app can’t be migrated yet

Before the migration starts, Softr checks the app. If a check fails, the dialog shows This app can’t be migrated yet, and you can’t click Start migration.

Migration dialog showing the warning This app can't be migrated yet, with a See how to fix button

When a check fails, Start migration stays disabled.

The message doesn’t say which check failed. Softr runs the two checks in the order below and stops at the first one that fails, so fix them in this order, then open the dialog again.

CheckSign that this check fails
1. Convert the app to the new app versionThe app shows Can’t convert yet in the app list when you click Convert app. Or, the bottom-right corner of the app editor shows Convert to new app version or Finish conversion.
2. Update old blocks that read AirtableA block that reads Airtable data shows Block update available or This legacy block is no longer supported at the bottom of its settings panel.

1. Convert the app to the new app version

Apps made before February 12, 2025 use the legacy app version, and the migration works only for apps on the new app version. If you started the conversion but didn’t finish it, the app still counts as not converted.

Start the conversion

Open the app. Softr may ask Convert current app to the new version? straight away. If it doesn’t, click Convert to new app version in the bottom-right corner of the app editor. Click How does conversion work?, then click Start converting.

Finish the conversion

When the conversion is done, click Finish conversion in the bottom-right corner of the app editor. The checklist shows the pages that still have blocks the new app version doesn’t support, usually header, footer, and user account blocks. Remove them.

Verify

Click Verify. When the checklist shows All set!, the conversion is finished.

Softr saves a snapshot of your app before the conversion, which you can go back to from Settings > App History. Your published app keeps working while you convert. For more details, see Migrating App Versions.

2. Update old blocks that read Airtable

Older block versions can’t show data from Softr Databases, so if an older block reads data from Airtable, the migration can’t start. These blocks count:

  • Blocks that read data from Airtable, on any page of the app. Hidden blocks count too.
  • Sign-up, user profile, and onboarding blocks, if your app users come from an Airtable table.

Blocks on deleted pages don’t count.

Check each block

Open each page. Click each block that reads Airtable data, hidden blocks included, and look at the bottom of the block settings panel.

If you see Block update available

Click View details.

  • If the dialog shows Update now, click it. Softr updates the block and keeps its settings.
  • If the dialog shows Add new version to app, click it. Softr adds the new version as a separate block. Set up the new block, then delete the old one.

If you see This legacy block is no longer supported

Click Add and add the new version of the block from the block library. Set it up, then delete the old block.

Delete old blocks you don't use

You don’t have to update an old block that you don’t use. You can delete it instead, which is often the fastest fix for hidden blocks.

For more details, see Block Version Update.

If the migration didn’t finish

If the migration stops after it starts, the app shows Failed in the Migrate app list. Hover the retry icon in that row to see what went wrong, fix the cause, then click the icon to try again.

The message names each Airtable base by its ID, for example appAbC123dEf456gH. To find the base, open it in Airtable: the ID is the part of the URL that starts with app. Softr checks only the tables your app uses and the tables they link to.

Two fields share this name

The message looks like this: table 'Projects', field 'Status': Two fields share this name, so references to it cannot be remapped unambiguously.

Two fields in the same Airtable table have the same name. Upper and lower case don’t count as different, so Status and status are the same name.

Open the table in Airtable and rename one of the two fields, preferably the one your app doesn’t use. If you rename a field that your app uses, blocks in your original app that use it can stop working.

Two tables share this name

The message ends with Two tables share this name, so field references cannot be remapped unambiguously.

Two tables in the same Airtable base have the same name. Upper and lower case don’t count as different. Rename one of the two tables in Airtable.

Softr can't read the Airtable base

The message looks like this: This application cannot be migrated - data source appAbC123dEf456gH could not be read - check that the connection still has access to it. You can also see No tables were returned for this Airtable base.

The Airtable connection that the app uses can’t read the base. To fix it:

  1. In Airtable, make sure the base still exists and that you have access to it.
  2. Make sure your Airtable account hasn’t used up its API calls for the month.
  3. In Softr, open a block that uses the base and go to its Source tab. Open the Base dropdown and click Edit bases Softr can access.
  4. In Airtable, give Softr access to the base. We recommend All current and future bases in all current and future workspaces.

For more help, see Airtable and Troubleshooting Airtable Errors.

A table or field is over the limit

A Softr database can have up to 512 tables, and a table can have up to 512 fields. If you see one of these messages, the base or a table is over the limit:

  • Base has 530 tables, the limit for a tablespace is 512
  • Table has 530 fields, the limit is 512

For a table with too many fields, delete the fields you don’t use in Airtable. For a base with too many tables, contact support.

A field can't be imported

You can see one of these messages:

  • Field has no type, which the import cannot translate
  • A message that starts with Field cannot be translated and would abort the import
  • No field of this table can be imported, so the table cannot be created

Contact support and include the full message.

Something went wrong, please try again

These messages are usually temporary:

  • Importing data source appAbC123dEf456gH failed, please try again
  • Could not copy the application's workflows, please try again
  • Could not start the migration, please try again

Start the migration again. If you get the same message again, contact support.

If you don’t see the migration option

The app editor shows the Migrate item, the Migrate to Softr Database button, and the migration dialog only when all of these are true:

  • You can edit the app. Workspace guests can’t start a migration.
  • The app reads data from Airtable.
  • The app isn’t a copy made by a migration, and it doesn’t already have one. To find the copy, go to Migrate from Airtable > Migrate app.
  • The app is a classic Softr app, created before November 2026.

After the migration

When the migration is done, Softr tells you that your app is migrated. The new app is a copy that uses Softr Databases. Before you publish it:

  • Review your data. If Softr shows Review data import, click it and work through the checklist. See What transfers, and what to double-check.
  • Check your workflows. The copy gets its own copies of the app’s workflows, but their steps still use Airtable. Update them to use Softr Databases.
  • Test as your users. Preview the app as a user in each user group and confirm they see exactly what they should, and nothing they shouldn’t.
  • Move your domain. Remove your custom domain from the original app and add it to the copy.

Get help

If you can’t find the cause of a problem, email support@softr.io. Include the link to your app and the full text of any message you see.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.