Documentation

Upgrade from InfluxDB 3 Core

Upgrade from InfluxDB 3 Core to InfluxDB 3 Enterprise. Your existing data and plugins are compatible with Enterprise–no data migration is required.

Downgrading is not supported

After upgrading to InfluxDB 3 Enterprise, you cannot downgrade back to InfluxDB 3 Core. Enterprise makes catalog changes that are incompatible with Core. To revert to Core, you must restore from a backup taken before the upgrade.

Before upgrading, back up your data directory.

Before you begin

  1. Back up your data: Create a backup of your InfluxDB 3 Core data directory before upgrading. For more information, see Back up and restore data.

  2. Note your current configuration: Record your Core startup options, including --data-dir, --object-store, --plugin-dir, and any other configuration. You’ll use the same data directory with Enterprise.

    For a complete list of configuration options, see the influxdb3 serve CLI reference. If you use a cloud object store (S3, Azure, or Google Cloud Storage), see Configure object storage.

  3. Choose a license type: Decide which InfluxDB 3 Enterprise license you need:

    • Trial: 30-day full-featured trial
    • At-Home: Free for hobbyist use (2 CPU limit, single-node only)
    • Commercial: For production and commercial use

    For more information about licenses, see Manage your license.

Upgrade to Enterprise

Choose your installation method:

Stop InfluxDB 3 Core

Stop the running Core process:

# If running in foreground, press Ctrl+C
# If running in background, find and stop the process
pkill -f "influxdb3 serve"

Install InfluxDB 3 Enterprise

Run the quick install script for Enterprise:

curl -O https://www.influxdata.com/d/install_influxdb3.sh \
&& sh install_influxdb3.sh enterprise

Start InfluxDB 3 Enterprise

Start Enterprise with your existing data directory. Enterprise requires a --cluster-id option that Core doesn’t use:

influxdb3 serve \
  --node-id 
NODE_ID
\
--cluster-id
CLUSTER_ID
\
--object-store file \ --data-dir
DATA_DIR
\
--license-email
EMAIL_ADDRESS

Replace the following:

  • NODE_ID: Your existing node identifier from Core
  • CLUSTER_ID: A new cluster identifier for Enterprise–for example, cluster0
  • DATA_DIR: The same data directory you used with Core
  • EMAIL_ADDRESS: Your email address for license activation

When prompted, select your license type (trial or home), then verify your email address.

Verify the upgrade

After starting Enterprise, verify the upgrade was successful:

# Check the version
influxdb3 --version

# Verify your license
influxdb3 show license --host http://localhost:8181

Query your existing data to confirm it’s accessible.

Stop the Core container

docker stop 
CORE_CONTAINER_NAME

Replace CORE_CONTAINER_NAME with the name of your InfluxDB 3 Core container.

Pull the Enterprise image

docker pull influxdb:3-enterprise

Start InfluxDB 3 Enterprise

Start Enterprise using the same data volume. Enterprise requires a --cluster-id option and license configuration:

docker run -d \
  --name influxdb3-enterprise \
  -p 8181:8181 \
  -e INFLUXDB3_ENTERPRISE_LICENSE_EMAIL=
EMAIL_ADDRESS
\
-v
DATA_VOLUME
:/var/lib/influxdb3/data \
-v
PLUGIN_VOLUME
:/var/lib/influxdb3/plugins \
influxdb:3-enterprise \ influxdb3 serve \ --node-id
NODE_ID
\
--cluster-id
CLUSTER_ID
\
--object-store file \ --data-dir /var/lib/influxdb3/data

Replace the following:

  • EMAIL_ADDRESS: Your email address for license activation
  • DATA_VOLUME: The same data volume you used with Core
  • PLUGIN_VOLUME: The same plugin volume you used with Core
  • NODE_ID: Your existing node identifier from Core
  • CLUSTER_ID: A new cluster identifier for Enterprise–for example, cluster0

License activation in Docker

You must provide INFLUXDB3_ENTERPRISE_LICENSE_EMAIL as an environment variable because the interactive license prompt doesn’t work in containers. After starting the container, check your email and click the verification link.

Using Docker Compose

Verify the upgrade

After starting Enterprise, verify the upgrade was successful:

# Check the version
docker exec influxdb3-enterprise \
  influxdb3 --version

# Verify your license
docker exec influxdb3-enterprise \
  influxdb3 show license --host http://localhost:8181
# Check the version
docker compose exec influxdb3-enterprise \
  influxdb3 --version

# Verify your license
docker compose exec influxdb3-enterprise \
  influxdb3 show license --host http://localhost:8181

Query your existing data to confirm it’s accessible.

Stop InfluxDB 3 Core

sudo systemctl stop influxdb3-core

Install InfluxDB 3 Enterprise

First, remove the Core package (this doesn’t remove your data or configuration):

DEB-based systems (Debian, Ubuntu)

RPM-based systems (RHEL, CentOS, Fedora)

Configure InfluxDB 3 Enterprise

The Enterprise package installs a self-documenting configuration file at /etc/influxdb3/influxdb3-enterprise.conf. Merge your Core settings into this file rather than overwriting it.

  1. View the settings you configured in Core:

    # Show uncommented (active) settings from Core configuration
    sudo grep -E '^ *[^#]' /etc/influxdb3/influxdb3-core.conf
  2. Merge Core settings into the Enterprise configuration:

    # Back up the original Enterprise configuration
    sudo cp /etc/influxdb3/influxdb3-enterprise.conf \
            /etc/influxdb3/influxdb3-enterprise.conf.orig
    
    # Merge settings from Core into Enterprise config
    sudo grep -E '^ *[^#]' /etc/influxdb3/influxdb3-core.conf | while IFS= read -r line; do
      key=$(echo "$line" | sed 's/=.*/=/')
      if sudo grep -qE "^ *${key}" /etc/influxdb3/influxdb3-enterprise.conf; then
        # Update existing uncommented line
        sudo sed -i "s|^ *${key}.*|${line}|" /etc/influxdb3/influxdb3-enterprise.conf
      else
        # Replace commented line with active setting
        sudo sed -i "s|^#${key}.*|${line}|" /etc/influxdb3/influxdb3-enterprise.conf
      fi
    done
  3. Add your license email to the Enterprise configuration:

    sudo sed -i 's|^#license-email.*|license-email = "
    EMAIL_ADDRESS
    "|'
    \
    /etc/influxdb3/influxdb3-enterprise.conf

    Replace EMAIL_ADDRESS with your email address for license activation.

  4. Verify the merged configuration:

    sudo grep -E '^ *[^#]' /etc/influxdb3/influxdb3-enterprise.conf

    The output should include your Core settings plus the license email and cluster ID–for example:

    node-id = "primary-node"
    object-store = "file"
    data-dir = "/var/lib/influxdb3/data"
    plugin-dir = "/var/lib/influxdb3/plugins"
    cluster-id = "primary-cluster"
    license-email = "you@example.com"

    The DEB/RPM packages use primary-node and primary-cluster as defaults, matching the behavior of running influxdb3 serve without --node-id or --cluster-id.

Start InfluxDB 3 Enterprise

sudo systemctl start influxdb3-enterprise

Check the logs to verify the server started successfully:

journalctl --unit influxdb3-enterprise -f

After starting, check your email and click the verification link to activate your license.

Verify the upgrade

After starting Enterprise, verify the upgrade was successful:

# Check the version
influxdb3 --version

# Verify your license
influxdb3 show license --host http://localhost:8181

Query your existing data to confirm it’s accessible.


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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