Having an Enterprise Dedicated plan means migrating your app and its data from the main cluster to your dedicated server. This process is handled by Bubble, ensuring that your users will not experience downtime or performance degradation.
However, due to the wide variety of apps and solutions supported by Bubble, we recommend going through a preparation checklist to ensure your app works as expected from the moment it migrates to the dedicated instance.
In this article series, we'll look into the migration process, and how we'll work with you to make it as seamless as possible.
1 - Preparing for migration
1 - Preparing for migration
This article serves as a guide to getting started with the Enterprise plan after you've completed the upgrade. For a broader understanding of the Enterprise plan, we recommend exploring the introductory article series linked below:
Article: Bubble for Enterprise
The first step to having an Enterprise Dedicated plan is migrating your app and its data from the main cluster onto your dedicated server.
Before we get your apps moved onto your new dedicated server, we will have a call to discuss expectations for the process. We will also work with you to schedule a time for the migration to occur.
In order to ensure there's plenty of time to complete the migration with monitoring, we schedule them to start any time between 9:00am - 2:00pm ET Monday through Thursday.
To do
Look through any database views you have.
All your data will still be there once your app is on your dedicated server, but any of the custom views you have set up won't get carried over. If there are any custom views that you are using often, make a note of what the constraints and visible fields are so that you can easily set it up again later.
Check your API URLs.
If you are using the API URL that includes “bubbleapps.io,” for example appname.bubbleapps.io/api/1.1/wf/workflow, those urls won’t work any more once your app is on a dedicated server. The base url for an app on a dedicated server is different from the structure used for apps on the main cluster, so make sure to change any references to your app’s apis to reference your app’s custom domain, or if you don’t have a custom domain set up, make a note of where you are referencing that old url so that you can change it later.
Consider moving paid plugins to perpetual licenses.
Plugins with perpetual licenses will continue to function as expected once you are migrated, but you'll need to resubscribe to any plugins that are on subscriptions once you are on your dedicated server.
Check for “testing” plugins.
Testing plugins are plugins where your app is the test app for that plugin. You can tell if you have a test plugin if you see “(testing)” written next to the plugin name in the plugins tab. We recommend against using them in your live app even on the main cluster, but using them is especially dangerous on dedicated environments because it creates an increased level of dependency on the main cluster. If you have any that you are not using, please remove them from your app. If you are using any, considering publishing them and using the published version instead. A private license works well for this option.
Consider wiping your database change history.
If you have a particularly large database, we may recommend that you wipe your database change history to limit the amount of data that needs to be transferred onto your dedicated server. This will allow us to make sure we can complete the migration in a single day. This process won’t delete any of your current data, but it will prevent you from doing point-in-time restorations of your database, so if you want to revert your database to a previous time that would no longer be possible.
2 - During migration
2 - During migration
You'll get an email from us at the scheduled date and time for the migration informing you that the process is starting. We'll let you know when it’s done and you can access your dedicated server.
If you are on a Premium Plus support plan you'll get access to a slack channel where we will send real time updates about the migration as it progresses and let you know when it’s done. Your users on your live app won't experience any changes and will be able to keep using the app throughout the migration process.
Note: Once we start the migration process, any changes that are made in your editor will not carry over.
We recommend pausing development since any work will be lost.
3 - Post-migration
3 - Post-migration
A few days after the migration, we'll have another call to go over the different functionality you have access to in the dedicated editor experience. We’ll also use this time to answer any questions you may have after exploring your app on your dedicated server.
To do
Log in to your dedicated server.
When the migration is done, we'll send you a link to log into your server. Before you can access your apps on the server, you need to go to that link and click “Login with Bubble.” If you don’t do this step, you'll see a “user not authorized” message when trying to access your app’s editor.
Make sure your Bubble software is up to date.
Open up your app on the dedicated server and you'll see a new icon in the upper toolbar. This is your Dedicated Manager. If it’s blue, that means a new Bubble version is available. In this case, click on the icon and then click “Upgrade.” This update can take a few hours and your app may not perform as intended until this update is complete. Check out the “Dedicated Manager” section of this packet for more information.
Reconnect any plugins that may have been disconnected.
You'll need to re-subscribe to any plugins that were on subscription licenses.
Check your Sendgrid integration.
Sendgrid settings get disconnected during migration, and will need to be reconnected if you have a custom sendgrid key. You'll need to deploy to live to make sure those updated settings get pushed to the live version of your app.