Metabase cloud how to#
Metabase cloud update#
Metabase cloud pro#
Metabase cloud download#

If you’re embedding Metabase in an application, be sure to update your code to reflect your new URL. People should be able to log in as usual and pick up right where they left off. Once you’ve confirmed everything is working, go ahead and tell everyone the new Metabase Cloud URL address they should use to log into Metabase. Tell your team about the new Metabase address

Metabase cloud how to#

See Authenticating with SAML for details on how to set these URLs.

Metabase cloud pro#

For Pro and Enterprise customers using SAML SSO, you’ll need to update your settings with your identity provider to change the Redirect URL and the Base URL to your new Metabase Cloud URL, otherwise your identity provider will still redirect people to your old (and shut down) Metabase instance.If you’re using Google Sign-in, you’ll need to go to Google Developers Console and add your new Metabase Cloud URL to the Authorized JavaScript Origins of the Google Auth Client ID.You should see all of your questions and dashboards just as you did in your self-hosted instance. After migrating to Metabase CloudĪfter a successful upload, some finishing touches and a restart is done automatically in a couple of minutes, and then you can log into your shiny new Metabase Cloud instance. If you’re still stuck, send us an email and we’ll help you troubleshoot. If anything goes sideways, follow any prompts the script outputs. If all goes well, the script will print Done!. The script will upload your application data to your new Metabase Cloud instance.

Warning: if you created any questions or dashboards in your Metabase Cloud instance, they will be overwritten when you upload the application data from your existing, self-hosted Metabase instance. Execute the script in your self-hosted environment There is one command for the Metabase JAR and a different one if you’re running Metabase via Docker.

Metabase cloud download#

You’ll get a command to run that will download a script to manage your migration. For migrations from Heroku, there are a few extra steps to running the script. If you’re running the JAR, you’ll need to make sure to set any MB_DB_* environment variables you normally use to configure your application database. If your self-hosted Metabase is running Docker, the environment variables will already be set. Visit your Metabase Store account and click Initiate Migration. The process itself is largely automated, but it’s unique to your instance. See Backing up Metabase Application Data. In the unlikely event that something goes wrong, you’ll want a backup. The idea here is to prevent people from creating more questions or dashboards that could put your instance in an inconsistent state during the migration. Shut down your Metabase instanceĪll you need to do is stop the Metabase JAR process or Docker container to make sure your Metabase has shut down. The migration process usually takes less than 15 minutes. Schedule some downtimeīe sure to let your users know that your Metabase instance will be unavailable for the duration of the migration (ideally during off-hours). In order to migrate, you’ll need shell access to your self-hosted Metabase environment, and your Metabase environment will need access to the Internet. There are some limitations to Metabase Cloud that may impact your migration. Prepare to migrate Understand the limitations And don’t stress if anything goes wrong, we’re here to help. Here’s how to migrate your existing Metabase instance to Metabase Cloud.