Export self host -> import SaaS

Feedback
1

Hey guys,

I didn’t know where to post this, so I chose this section :blush:
I am writing from my phone and as a non native English speaking person forgive me some bad grammar and such :joy:

I love Baserow for my daily projects with N8n and other automations. I hate it that I can’t just export my docker hosted workspace and send it to others who are using SaaS.

Is it against ToS if I build my own solution via N8N to export and import to a cloud instance?

Thanks for answering on advance! Love your product!!

2

Hey @DominikHeiss, thank you for your kind words about Baserow—we appreciate your feedback a lot! :blue_heart:

It’s due to security reasons that we’re not allowing workspace imports from self-hosted versions to SaaS, but let me check with the team if there are any plans to add this possibility in the future (probably with additional checks). :slightly_smiling_face:

3

Hey, thanks for replying!

Yeah sure, I’ve read various comments about that and I do understand it.
It’s just a pita tbh :wink:
I can do that export/import feature myself with N8N…quite easy actually… I just wanted to check if you prohibit that!

I’m not doing anything shady…no code injection or whatever security concerns there may be… just plain old API creates and updates.

5

Okay, I finished my workflow today.

With that flow, I can:

  • export the whole Baserow schema of my docker or cloud instance into a central “mapping table”
  • automaticall create workspace + database and restore every table + their fields (after I imported that mapping-table)
  • sadly I have to start my workflow like 2-3-4 times (because I suck at coding)… but after that, even the most complex link_rows or lookup field types have been updated
  • it even switches the old IDs for the new ones
  • for automatic ID switching of every N8N baserow node I made a little web app (just upload ur workflow.csv and you get the mapped one)

Just my own personal victory until you’re giving us the option to export locally and import into the cloud instance :wink:

1 Like
6

@DominikHeiss thank you for sharing the workflow :raised_hands: