I was hoping to find some information about the possibility to transfer subapps (Teams plan) to other Bubble users.
We are operating a multi-tennant app but want to give customers the option to have their own sub-app. Besides from some practical advantages(custom domain, dedictaed database) and disadvantages (accumulating plugin costs like Charts etc…) on of the main purposes - for us at least - of a segregated setup is the potential to transfer the app to a customer in full and with ease if for example we would ceize our activities.
For this to work it is essential that a sub-app can be transferred (like a standalone app) so users can use the sub-app regardless of other customers.
Tricky thing is I can’t find any info or vids about this. ANyone know how this works and where more info is available?
Yes, a sub-app created under the Bubble Teams plan can be transferred to another user as a completely independent, standalone application, using the standard Application Rights transfer process found in its own Settings.
You have peace of mind with this strategy! Sub-apps, despite being created within your main app’s workspace on the Teams plan, are treated as entirely distinct applications regarding ownership. This means if you ever cease your operations or sell off a client’s portion of the business, you can go into the specific sub-app’s Settings → General tab, use the Application Rights feature, and initiate a transfer to the customer’s Bubble account. The sub-app is then completely detached and self-sufficient, allowing your customer to manage their custom domain, database, and dedicated environment without relying on your continued subscription.
Are there other operational or legal considerations for your multi-tenant structure you’d like to clarify? I can help with best practices for Bubble’s multi-tenancy!
My database of course has some system data (for example a list of Countries) and customer data. When setting up a subapp I only want part of the ‘parent’ database to transfer to the subapp. Any idea how this is done?
2FA
The mainapp uses Bubble’s native 2FA.. I’m afraid that I will have to select a growth plan for the subapp just to use the 2FA features?
For partial data transfer, you must clean the parent app’s Live database, leaving only system data, before creating the sub-app; and regarding 2FA, the native feature requires the sub-app to be on a Growth Plan or higher, making a custom Twilio/TOTP solution the cost-effective alternative.
Was what I was afraid of. We have a multi-tennant app so the subapp is an exception.
Workaround would then be the API where we have an admin page that allows us to push certain data types into the production database of the subapp, or sync via csv uploads but i guess there are 100s of reasons not to choose that way.
I’m not a fan of the API solution as i’m terrified of leaking API keys given the way they are stored in open input fields within Bubble
That’s a very understandable concern, and you are absolutely right to be cautious about exposing API keys in client-side input fields that is a significant security risk.
The good news is that there is a secure way to manage this data transfer.
Instead of using an admin page to push data directly from the client side, the professional solution is to use Bubble’s Backend Workflows (API Workflows). This keeps the API keys securely hidden on the server, ensuring they are never exposed to the client or the browser.
I am very strong with API Connector configurations and building secure, server-side data sync processes between different Bubble applications (using one app’s Backend Workflows to write to another app’s database). I would be happy to help you architect a secure and reliable solution for this multi-tenant data management.
Let’s jump on a quick call to map out this secure sync method. DM me to schedule!
