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 3.

To benefit from the InfluxDB 3 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!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2

InfluxDB Cloud powered by TSM