Migrate into InfluxDB
Tested with: InfluxDB 3 3.12 on Databasezy · zb CLI 0.1
Sources: InfluxDB 3 (Core, Enterprise or Cloud) by connection string, another Databasezy instance.
How the copy works
Section titled “How the copy works”Per database and table, SELECT * is streamed as JSON lines from /api/v3/query_sql, converted to line protocol
and written with /api/v3/write_lp at nanosecond precision; tags stay tags and fields stay fields. The token goes
in the URL password slot; name a database in the path to copy only that one.
Run it
Section titled “Run it”# --dry-run prints the preflight checklist and the exact plan without changing anythingFollow it with zb migrate status <mig_id>, or in the portal under the instance’s Migrate in tab.
What is verified
Section titled “What is verified”count(*) per database.table and a hash of each table’s columns. Mismatches are listed in the result; nothing is switched for you.
Not carried over
Section titled “Not carried over”- InfluxDB 1.x and 2.x sources: export to line protocol first (
influx_inspect export/influxd inspect export-lp) and write it to the instance. - Retention periods and last-value / distinct caches are not copied.
- Each table is read with one streaming query; split very large tables with
--include.
How migrations work covers preflight, verification and cutover; engine conversions covers moves between engines.