Migrating data between baserow instances

Baserow is an open-source alternative to tools like Airtable and Google Sheets. It allows users to create databases and manage data in a user-friendly, spreadsheet-like interface. With Baserow, you can store, share, and collaborate on data with your team, all while maintaining full control over your data as it's self-hosted. It offers features like row-level permissions, different field types, views (like table, gallery, kanban), and more. It also provides APIs for developers to build custom apps or integrations.

If you ever host it yourself and want to move between instances, this is a handy guide to export and import data from your baserow installation

Moving Data

Migrating and backing up data for selfhosted installations is currently sparsely documented. The result is stemming from different forums, google searches and combining the official docs.

1. Export data - this includes database and file storage

   • For docker all-in-one:

     docker-compose exec -it baserow ./baserow.sh backend-cmd manage export_workspace_applications {{old_workspace_id}} --indent

   • For selfhosted kubernetes exec into wsgi pod:

     cd /baserow/backend

     source ../venv/bin/activate

     ./baserow export_workspace_applications {{old_workspace_id}} --indent

2. Move data to new instance. Depending on your setup via docker cp or kubectl cp
3. Import data

   • For docker all-in-one:

     docker-compose exec -it baserow ./baserow.sh backend-cmd manage import_workspace_applications {{new_workspace_id}} {{filename exluding .zip or .json}}

   • For selfhosted kubernetes exec into wsgi pod:

     cd /baserow/backend

     source ../venv/bin/activate

     ./baserow import_workspace_applications {{new_workspace_id}} {{filename exluding .zip or .json}}

Note If you are working with self-hosted environment, there is only one workspace. So you need to insert one of the available workspace IDs.