Documentation

chronoctl migrate

The migrate command lets you migrate your Chronograf configuration store.

By default, Chronograf is delivered with BoltDB as a data store. For information on migrating from BoltDB to an etcd cluster as a data store, see Migrating to a Chronograf HA configuration.

Usage

chronoctl migrate [flags]

Flags

FlagDescriptionInput type
-f--fromFull path to BoltDB file or etcd (e.g. bolt:///path/to/chronograf-v1.db or etcd://user:pass@localhost:2379 (default: chronograf-v1.db)string
-t--toFull path to BoltDB file or etcd (e.g. bolt:///path/to/chronograf-v1.db or etcd://user:pass@localhost:2379 (default: etcd://localhost:2379)string

Provide etcd authentication credentials

If authentication is enabled on etcd, use the standard URI basic authentication format to define a username and password. For example:

etcd://username:password@localhost:2379

Provide etcd TLS credentials

If TLS is enabled on etcd, provide your TLS certificate credentials using the following query parameters in your etcd URL:

  • cert: Path to client certificate file or PEM file
  • key: Path to client key file
  • ca: Path to trusted CA certificates
etcd://127.0.0.1:2379?cert=/tmp/client.crt&key=/tst/client.key&ca=/tst/ca.crt

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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