Import complete workspaces from ZIP files to migrate between Baserow instances, restore backups, or duplicate workspace configurations.
The import process preserves databases, applications, dashboards, and structure while requiring post-import configuration for members and automations.
Workspace imports give you the flexibility to transfer your Baserow work between instances, restore from backups, or replicate configurations across teams.
Whether you’re migrating from development to production, moving between Baserow Cloud and Self-hosted, or sharing workspace templates with colleagues, the import process ensures your databases, applications, and dashboards transfer completely and accurately.
Importing a workspace is useful in several scenarios:
Ensure your workspace import starts with proper preparation:
Learn how to export workspaces →
Import as a new workspace to create a separate workspace, or merge with an existing workspace to add content to the current workspace. You can also choose to import the structure only or include all row data.
After completion, verify the imported content by checking databases, tables, applications, dashboards, and views to ensure everything transferred correctly.
After importing a workspace, several steps are required to make it fully operational. Document dependencies before exporting, including database applications, external integrations, and webhooks that may need recreation.
Invite members: Imports don’t include collaborators or permissions. Add team members and assign roles via Workspace Settings → Members. Guide to inviting collaborators →
Reconnect integrations: Webhooks and external services don’t transfer. Recreate webhooks and reconnect integrations.
Republish applications: Reconfigure published applications and custom domains, as these settings don’t carry over automatically.
Test everything: Validate functionality in a staging environment first. Check navigation, forms, linked fields, formulas, and permissions before using in production.
Upload timeout or connection lost
Large files may exceed upload timeouts, especially with slow internet connections. Try compressing very large workspaces by exporting structure-only first, splitting large workspaces into smaller database-level exports, or using a faster network connection for upload.
Start with structure-only imports when setting up new environments or sharing templates. Import full data separately if needed. This reduces file size and speeds up initial configuration.
Workspace name conflicts
If a workspace with the imported name already exists, Baserow may rename the imported workspace by adding numbers or timestamps. You can rename it after import completes. Check workspace names carefully to avoid confusion.
Keep export files organized with clear naming conventions indicating workspace name, export date, whether data is included, and purpose (backup, migration, template).
Missing data or incomplete import
If imported workspaces lack expected data, verify the export included data (not just structure), check that the export completed successfully before import, and ensure the target instance has sufficient storage. Re-export and retry if necessary.
Modules don’t function correctly
Baserow modules rely on specific database structures and data sources. If applications fail after import, verify all required databases and tables imported successfully, check that data source configurations point to the correct tables, and review element settings for broken references.
No. Workspace imports only work with Baserow export files. For Airtable migrations, use Baserow’s dedicated Airtable import tool, which handles database structure and data conversion.
Workspace member lists and permissions don’t transfer. You must manually invite collaborators and assign roles after importing. This ensures you control who has access in the new instance.
Yes. Each import creates a new copy unless you explicitly merge with an existing workspace. Multiple imports are useful for testing, creating copies for different teams, or maintaining separate development and production versions.
No. Published applications require reconfiguration, including setting up publishing, configuring custom domains if used, and verifying that authentication works correctly. Applications import successfully, but aren’t automatically published.
Import time varies dramatically. Small workspaces import in under a minute. Large workspaces with thousands of rows and file attachments may take 10-30 minutes or longer. Progress indicators show status during processing.
Security restrictions prevent importing files from unknown sources. Malicious imports could contain harmful configurations or expose security vulnerabilities. You can import existing Baserow data by uploading the .zip file from another Baserow instance. It’s not possible to import a zip file from an untrusted source.
Yes. Imported workspaces, databases, and rows count toward your subscription plan limits. Ensure your plan has sufficient capacity before importing large workspaces.
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.
Contact support for questions about Baserow or help with your account