Documentation

influxd upgrade

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

Use the influxd upgrade command to upgrade an instance of InfluxDB 1.x to InfluxDB 2.8. This command copies all data in databases and retention policies (used in 1.x) over to buckets (used in 2.8).

Be sure to back up all data before upgrading with influx upgrade.

This command performs the following actions:

  1. Creates the InfluxDB 2.x configuration file using 1.x configuration file options. Unsupported 1.x options are reported to standard output. If the configuration file is not available, the 1.x database folder can be passed via th --v1-dir flag.
  2. Copies and upgrades 1.x database files.

The target 2.x database directory is specified by the --engine-path option. If changed, the bolt path can be specified by the --bolt-path option.

Usage

influxd upgrade [flags]
influxd upgrade [command]

Flags

FlagDescriptionInput type
-m--bolt-pathPath for boltdb database (default ~/.influxdbv2/influxd.bolt)string
-b--bucketPrimary bucket namestring
--config-fileCustom InfluxDB 1.x config file path (default ~/.influxdb/influxdb.conf)string
--continuous-query-export-pathPath for exported 1.x continuous queries (default ~/continuous_queries.txt)string
-e--engine-pathPath for persistent engine files (default ~/.influxdbv2/engine)string
-f--forceSkip the confirmation prompt
-h--helpHelp for influxd upgrade
-c--influx-configs-pathPath for 2.x influx CLI configurations file (default ~/.influxdbv2/configs)
--log-levelSupported log levels are debug, info, warn, and error (default info)string
--log-pathCustom log file path (default ~/upgrade.log)string
-o--orgPrimary organization namestring
--overwrite-existing-v2Overwrite existing files at the output paths instead of aborting the upgrade process
-p--passwordPassword for usernamestring
-r--retentionDuration bucket will retain data (default 0; retains data infinitely)string
-t--tokenToken for username. If not specified, a token is auto-generated.string
-u--usernamePrimary usernamestring
--v1-dirPath to source 1.x db directory containing meta, data, and wal sub-folders (default ~/.influxdb)string
--v2-config-pathDestination path for upgraded 2.x configuration file (default ~/.influxdbv2/config.toml)string
-v--verboseVerbose output

Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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