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.


telegraf [global-flags] config migrate [flags]


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


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!

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: