Documentation

influxd downgrade

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

Use the influxd downgrade command to downgrade the metadata schema used by influxd to match the metadata schema of a older release.

InfluxDB does not guarantee backwards-compatibility with earlier releases. Attempting to start an older influxd binary with a BoltDB or SQLite file that has been migrated to a newer schema will result in a startup error. This command downgrades metadata schemas to match the schemas of an older release and allows the older influxd binary to boot successfully.

Run this command prior to downgrading the influxd binary.

Usage

influxd downgrade [flags] <target-version>

Flags

FlagDescriptionInput type
--bolt-pathPath to BoltDB database (default is ~/.influxdbv2/influxd.bolt)string
-h--helpHelp for downgrade
--log-levelLog level (debug, info (default), warn or error)string
--sqlite-pathPath to SQLite database (default is influxd.sqlite in the bolt path directory)string

Examples

Downgrade to InfluxDB 2.0
influxd downgrade 2.0

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

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