Documentation

telegraf config migrate

The telegraf config migrate command reads the configuration files specified in the --config or --config-directory and attempts to migrate plugins or options that are currently deprecated to the recommended replacements. If no configuration file is explicitly specified, the command reads the default locations and uses those configuration files.

Migrated files are stored with a .migrated suffix at the location of the source configuration files. If migrating remote configurations, the migrated configuration is stored in the current directory using the URL as the filename with a .migrated suffix.

Test migrated configuration files

We strongly recommend testing migrated configuration files before using them in production.

Usage

telegraf [global-flags] config migrate [flags]

Flags

FlagDescription
--forceForces overwriting of an existing migration file
-h--helpShow command help

Examples

Migrate a single configuration file

To migrate the file mysettings.conf, run the following command:

telegraf --config mysettings.conf config migrate

Migrate a configuration directory

To migrate all configurations files in the ~/telegraf/conf/ directory, use the following command:

telegraf --config-directory ~/telegraf/conf/ config migrate

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