Baserow makes Airtable migration seamless; import your entire base structure and data with one click, then enjoy open-source flexibility.
Migrate your Airtable bases to Baserow in minutes with automatic field type conversion and data preservation. Learn what transfers, what needs reconfiguration, and how to prepare for a smooth migration.
Switching from Airtable to Baserow doesn’t mean starting from scratch. Baserow’s import feature automatically converts your Airtable bases into Baserow databases, preserving your tables, data, views, and most field configurations.
The process takes just minutes and handles field type conversions automatically, so you can focus on customizing your new database rather than rebuilding it.
You’ll need a public share link to your entire Airtable base. If you can’t find the share option, check your Airtable permissions. See Airtable’s documentation for detailed help.
Ensure you have a Baserow workspace ready, and verify you have permissions in the workspace. Check storage availability if importing large bases with many attachments
You’ll see a progress indicator during import. An Airtable base with many files can slow down the import. Enabling “Skip importing files” skips the import of the files.
This will import most of the data, but there are incompatibilities. A table named “Airtable import report” will therefore be added, containing a list of things that were not or partially imported.
Once complete, your new database opens automatically with all imported data ready to use.

If the import responds with “The Airtable base requires authentication.” then it could be that the organizational settings in Airtable prevent accessing the Airtable base without authenticating first. To do this, the session and signature must be manually extracted.
https://airtable.com.__Host-airtable-session and __Host-airtable-session.sig cookie values, and paste them in the inputs.✅ All tables – Complete table structure with all records
✅ Field types – Converted to Baserow equivalents
✅ Table relationships – Link to another record becomes Link to table
✅ Attachments and files – All uploaded files preserved
✅ Views – Grid views with filters, sorts, and grouping
✅ Field properties – Formatting, options, and configurations
✅ Row data – All records with their complete information
❌ Automations – Rebuild using Baserow automations
❌ Custom interfaces – Recreate with Application Builder
❌ Integrations – Reconnect using Baserow API
❌ Row comments – Not imported; start fresh in Baserow
❌ Revision history – Historical changes not preserved
❌ Field descriptions – Add manually after import
❌ Access controls – Reconfigure permissions
Baserow automatically converts Airtable field types to their closest equivalents. Most conversions are direct matches, but some require understanding the differences:
| Airtable field | Baserow field | Notes |
|---|---|---|
| Single line text | Single line text | Perfect match |
| Long text | Long text | Perfect match |
| Single select | Single select | Colors may differ slightly |
| Multiple select | Multiple select | Colors may differ slightly |
| Checkbox | Boolean | Same functionality |
| URL | URL | Perfect match |
| Date | Date | Converts to ISO format |
| Phone number | Phone number | Perfect match |
| Perfect match | ||
| Rating | Rating | Perfect match |
| Attachment | File | All files preserved |
| Link to another record | Link to table | Relationships maintained |
| Created time | Created on | Timestamps preserved |
| Last modified time | Last modified | Timestamps preserved |
Number fields retain formatting like decimal places and thousand separators, but large number abbreviations (1K, 1M) won’t be preserved.
| Airtable field | Baserow field | How it converts |
|---|---|---|
| Number | Number | Decimal places and separators preserved |
| Currency | Number | Symbol becomes prefix (e.g., “$” before values) |
| Percent | Number | “%” becomes suffix (e.g., “75%”) |
| Duration | Number | Converts to numeric seconds/minutes |
These Airtable field types don’t have direct Baserow equivalents and will not be imported. Before importing, you can change these fields to text or number fields in Airtable to preserve the data, then recreate the functionality in Baserow after import:
Check each table to confirm all rows imported and compare record counts between Airtable and Baserow. Spot-check records for accuracy and test linked records. Review Baserow’s import report to identify items requiring manual recreation.
Rebuild formula fields using Baserow formulas or Baserow AI. Document Airtable automations and recreate them with webhooks or workflow tools like Zapier, Make, and n8n. Recreate custom interfaces via Application Builder, forms with Baserow forms, and public views for sharing.
Set up Kanban, Calendar, or Timeline views, along with personal views, filters, and sorts. Add workspace members, configure role-based permissions, and create teams for collaboration.
If the import function does not fit your needs, there are several alternative approaches. One option is to start fresh using templates. You can browse Baserow templates tailored to similar use cases, customize them instead of importing from Airtable, and take advantage of designs optimized for Baserow.
Another approach is manual recreation. This involves creating a database from scratch while optionally importing only the data via CSV. This method allows you to rebuild the structure while redesigning and optimizing your workflow.
A hybrid approach combines both strategies. You can import an existing base for structure and data, then use a template to add new features, giving you the flexibility to leverage the strengths of both methods.
Import time depends on your base size. Small bases (under 1,000 rows) complete in seconds, medium bases (1,000-10,000 rows) take 1-2 minutes, and large bases (10,000+ rows) may take several minutes. File attachments add to import time since they’re downloaded and re-uploaded to Baserow.
No. The import process only reads your Airtable data using the public share link. Your original Airtable base remains completely unchanged. You can continue using Airtable during and after the import process.
No, you must import bases one at a time. Each Airtable base becomes a separate Baserow database. If you have multiple related bases in Airtable, import them individually, then consider using Link to table fields to connect them in Baserow.
If import fails, you’ll see an error message explaining the issue. Common causes include invalid share links, Airtable permission issues, or network problems. Try generating a new share link and importing again. If problems persist, contact support with your error message and base details.
Yes, you can import an Airtable base as many times as needed. Each import creates a new, independent Baserow database. This is useful for testing migrations or creating separate databases for different purposes (production vs. testing, different time periods, etc.).
This is caused by the share link isn’t properly formatted or has expired. Generate a new share link in Airtable and ensure you’re copying the entire URL
This is caused by the share link might be for a view, not the entire base. Make sure you’re sharing the whole base, not just a single view or table
This is caused by formula fields aren’t imported automatically. This is expected behavior. Recreate formulas using Baserow formula syntax
This is caused by large files that may time out during transfer. Import smaller batches or check your network connection. Very large files (over 100MB) may need manual upload
This is because Baserow uses a slightly different color palette. This is cosmetic and doesn’t affect functionality. You can manually adjust colors in single/multiple select fields after import
Now that you’ve imported from Airtable, explore these resources:
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions; we’re ready to assist you.