Redash Migration - HOSSTED

Redash Migration is shutting down their Hosted-Redash service, meaning, all customer data in will be deleted within thirty days after access to the service ends on November 30, 2021. This means you need to migrate away from hosted-redash ASAP as you will not be able to migrate after December 30, 2021.

Redash is encouraging its users to migrate to the open-source version of Redash, which you can host for yourself free of charge. This means moving away from your hosted-redash solution to be hosted locally or using an alternative cloud hosting service such as AWS, MS Azure, Google Cloud, or others.

Getting down to it, you need to run the actual migration of the data (queries, dashboards, alerts, etc). You can use the Redash “Redash-Migration tool”, carefully following the instructions (btw, it’s a good read in any event).

To build your new redash server you can use the new HOSSTED.COM Cloud App to migrate your Redash to ms-Azure or AWS cloud using the newly developed Hossted Redash Migration tool where your deployment is one click away! is an open-source cloud deployment system that uses technology to automate the deployment of more than 50 Open Source applications that are bundled with Excellent Product Support. You practically receive an Enterprise-Ready Redash with Support, Monitoring, and Integration, running on ms-Azure or AWS cloud servers.

Once you “Click-to-Deploy” the Hossted Redash Migration you will have an instance ready for “Redash Migration” packaged with:

  • Ticket Support & Live chat
  • Custom URL
  • Built-in SSL
  • Connection to Active Directory
  • Migration Service
  • 24×7 uptime monitoring
  • Notifications for security and other updates
  • Access to educational support content library

In practice, this means that not only does the installation of the Open-Source application on the cloud turn out to be an easy task, you also have access to the best available DevOps Experts for any support need you may have as long as you are running this application.


Redash Migration with hossted – Step-by-Step tutorial


To make it easier for our customers to run the integration, here is the Redash  “Redash-Migration tool” augmented with screenshots from running the migration process.


  1. Install new instance on-prem or using

    • This instance will be your destination for the migration. Here you will need to create a new user for the migration to work properly

    • redash-migrate assumes your destination is a fresh instance of Redash. But the destination cannot be entirely blank because you need at least one admin user to already exist at the destination. As part of the init command, you will be asked to provide the user id for your admin user at both the origin and the destination instance.

    • It is our recommendation not to create any other users in the destination instance before using redash-migrate, since you will need to manually add them to the meta-data file meta.json so that it can associate their id at the origin instance with their id at the destination.

  2. Install python 

  3. Install pip

  4. Install redash-toolbelt which provides the redash-migrate executable

pip install –upgrade redash-toolbelt

  1. Run redash-migrate init


  • redash-migrate uses a file called meta.json to track its state between command executions. And it updates meta.json after each command executes.

  • Run redash-migrate init command before you begin the migration process. It will create the meta.json file in your working directory and then prompt you to answer several questions about how to authenticate against your origin and destination instances. Once finished, you can check the settings of the meta.json file to ensure the correct information is provided. Basic settings are:

  • Origin_url: The base URL for your origin Redash instance. For example:

  • Origin_admin_api_key: The API key for an admin user on your origin instance.

  • Destination_url: The base URL for your destination Redash instance. For example:http://localhost

  • Preserve_invite_links: Whether or not to write user invitation links into meta.json. If false, users logging in to the destination instance for the first time will need to click the “I forgot my password” link to receive an email. If true, invite links will be written to meta.json. These links can be used to set a new password directly without using the forgotten password workflow. The value is true.

  • ⚠️  Warning: Do not share your meta.json file with anyone. It contains administrator API keys for your Redash instance. This information is private. If you do share it, reset the admin API keys for your Redash instances immediately.

  1. Create a migrate-user in with admin privileges

  2. Collect all the needed data from

    • Collect the redash URL

    • Collect redash token from a user token

  3. Create datastore in a new instance

  4. Run Redash-migrate data sources (here it didn’t work at first because access to a data-source (mongo) was initially blocked by firewall)

  5. Run Redash-migrate check-data-sources

  6. Run Redash-migrate users


  1. Run Redash-migrate groups


  1. Run Redash-migrate queries


  1. Run Redash-migrate visualizations


  1. Install Redash-migrate dashboards


  1. Run Redash-migrate alerts


  2. Run Redash-migrate favorites


You are now ready to use your new Redash!

Need more help? Contact us at


Skip to content