Migrate data to InfluxDB Cloud Serverless
Migrate data to InfluxDB Cloud Serverless powered by the v3 storage engine from other InfluxDB instances powered by TSM including InfluxDB OSS 1.x, 2.x, InfluxDB Enterprise, and InfluxDB Cloud (TSM).
- Should you migrate?
- Before you migrate
- Data migration guides
Should you migrate?
There are important things to consider with migrating to InfluxDB Cloud Serverless. The following questions will help guide your decision to migrate.
Are you currently limited by series cardinality?
Yes, you should migrate. Series cardinality is a major limiting factor with the InfluxDB TSM storage engine. The more unique series in your data, the less performant your database. The InfluxDB v3 storage engine supports near limitless series cardinality and is, without question, the better solution for high series cardinality workloads.
Do you want to use SQL to query your data?
Yes, you should migrate. InfluxDB Cloud Serverless lets you query your time series data with SQL. For more information about querying your data with SQL, see:
Do you depend on a specific cloud provider or region?
You should maybe migrate. InfluxDB Cloud Serverless instances are available from the following providers:
- Amazon Web Services (AWS)
- US East (Virginia)
- EU Frankfurt
If your deployment requires other cloud providers or regions, you may need to wait until the InfluxDB v3 storage engine is available in a region that meets your requirements. We are currently working to make InfluxDB v3 available on more providers and in more regions around the world.
Are you reliant on Flux queries and Flux tasks?
You should maybe migrate. Flux queries are less performant against the InfluxDB v3 storage engine. Flux is optimized to work with the TSM storage engine, but these optimizations do not apply to the on-disk structure of InfluxDB v3.
Before you migrate
Before you migrate from InfluxDB 1.x or 2.x to InfluxDB Cloud Serverless, there are schema design practices supported by the TSM storage engine that are not supported in the InfluxDB v3 storage engine. Specifically, InfluxDB v3 enforces the following schema restrictions:
- You can’t use duplicate names for tags and fields
- Measurements can contain up to 200 columns where each column represents time, a field, or a tag.
For more information, see Schema restrictions.
If your schema does not adhere to these restrictions, you must update your schema before migrating to InfluxDB Cloud Serverless.
Data migration guides
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.