Documentation

Replicate an organization

The state of an organization consists of metadata (dashboards, buckets, and other resources) and data (time-series). An organization’s state at a point in time can be replicated to another organization by copying both metadata and data. To replicate the state of an organization:

  1. Create a new organization using the InfluxDB Cloud sign up page. Use a different email address for the new organization.

  2. Replicate metadata.
    Use an InfluxDB template to migrate metadata resources. Export all resources, like dashboards and buckets, to a template manifest with influx export all. Then, apply the template to the new organization.

  3. Replicate data.
    Use one of the methods below to copy data to the new organization:

  4. Re-invite users.

Export data to CSV

  1. Perform a query to return all specified data.
  2. Save the results as CSV (to a location outside of InfluxDB Cloud).
  3. Write the CSV data into a bucket in the new organization using the influx write command.

Write data with Flux

Perform a query to return all specified data. Write results directly to a bucket in the new organization with the Flux to() function.

If writes are prevented by rate limiting, use the influx write --rate-limit flag to control the rate of writes. For more information on rate limits in InfluxDB Cloud, see Exceeded rate limits.


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:

InfluxDB Cloud powered by TSM