Documentation

Migrate to an account in a new region

The following guide provides instructions on migrating data and resources from an existing InfluxDB Cloud account to a new InfluxDB account in another InfluxDB Cloud region.

Create a new account in a new region

InfluxDB organizations are bound to a specific cloud provider and region. Create a new InfluxDB Cloud account in the region you want to migrate to.

Migrate Data

If you want to migrate data from your current InfluxDB Cloud account to your new destination InfluxDB Cloud account, there is documentation available that walks through the migration. The specific process varies depending on whether your destination account is powered by our current database engine, Time-Structured Merge Tree (TSM) or our new database engine, InfluxDB v3.

To benefit from the InfluxDB v3 storage engine’s unlimited cardinality and support for SQL, migrate your data to InfluxDB Cloud Serverless.

To see which storage engine your organization uses, find the InfluxDB Cloud powered by link in your InfluxDB Cloud organization homepage version information. If your organization is using TSM, you’ll see TSM followed by the version number. If Serverless, you’ll see InfluxDB Cloud Serverless followed by the version number.

Dual write into both organizations

Depending on the duration of your retention policy for storing data it may be easier to temporarily dual write into both the source and destination accounts for an overlapping period until the destination account holds all desired data.

Migrate Resources

Resources include, but are not limited to the following:

  • buckets
  • dashboards
  • notification rules
  • tasks
  • labels
  • variables

If you have resources that you want to migrate to your destination account (rather than recreating these resources in the destination account) you can do the following:

  1. Download and install the 2.x influx CLI.

  2. Set up InfluxDB connection configurations for both your source and destination InfluxDB Cloud accounts. Use the influx config create command and provide the following for each connection:

    # Create your source connection configuration and set it to active
    $ influx config create \
      --config-name source \
      --host-url https://cloud2.influxdata.com \
      --org <your-source-org> \
      --token <your-source-auth-token> \
      --active
    
    # Create your destination connection configuration
    $ influx config create \
      --config-name destination \
      --host-url https://cloud2.influxdata.com \
      --org <your-destination-org> \
      --token <your-destination-auth-token>
    
  3. Use the influx export all command to export all resources from your source account to an InfluxDB template.

    influx export all
    
  4. Use the influx config command to switch to your destination connection configuration. Provide the name of the configuration to switch to:

    influx config destination
    
  5. Use influx template apply command to apply the exported InfluxDB template created in the previous step to your destination account:

    influx apply --file path/to/template.json
    

Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud powered by TSM