Documentation

Migrate data from InfluxDB OSS to other InfluxDB instances

To migrate data from an InfluxDB OSS bucket to another InfluxDB OSS or InfluxDB Cloud bucket, export your data as line protocol and write it to your other InfluxDB bucket.

InfluxDB Cloud write limits

If migrating data from InfluxDB OSS to InfluxDB Cloud, you are subject to your InfluxDB Cloud organization’s rate limits and adjustable quotas. Consider exporting your data in time-based batches to limit the file size of exported line protocol to match your InfluxDB Cloud organization’s limits.

  1. Find the InfluxDB OSS bucket ID that contains data you want to migrate.

  2. Use the influxd inspect export-lp command to export data in your bucket as line protocol. Provide the following:

    • bucket ID: (Required) ID of the bucket to migrate.
    • engine path: (Required) Path to the TSM storage files on disk. The default engine path depends on your operating system, If using a custom engine-path provide your custom path.
    • output path: (Required) File path to output line protocol to.
    • start time: Earliest time to export.
    • end time: Latest time to export.
    • measurement: Export a specific measurement. By default, the command exports all measurements.
    • compression: (Recommended) Use Gzip compression to compress the output line protocol file.
    influxd inspect export-lp \
      --bucket-id 12ab34cd56ef \
      --engine-path ~/.influxdbv2/engine \
      --output-path path/to/export.lp
      --start 2022-01-01T00:00:00Z \
      --end 2022-01-31T23:59:59Z \
      --compress
    
  3. Write the exported line protocol to your InfluxDB OSS or InfluxDB Cloud instance.

    Do any of the following:


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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: