What it does
kynetra migrate plans, runs, resumes and rolls back a project move built on the portable backup bundle. It checks compatibility, transfers the bundle in checksummed chunks with a durable checkpoint, restores into a target engine, validates, and then records a cutover watermark. The transport that ships today is local directories; no cloud transport is implemented.
How it works
A migration is create a bundle at the source, transfer it, verify it, then restore it at the target. plan, also called dry-run, produces the full plan and a compatibility report without writing anything: a source inventory, a compatibility assessment against the target's capabilities, such as region constraints and missing feature flags, and a transfer estimate. run stages the bundle in a working directory, splits it into chunks with per-chunk checksums, transfers them with a durable checkpoint after each verified chunk, restores into the target project, validates, and records the cutover watermark.
An interrupted run resumes without re-transferring chunks that were verified, and re-running a finished migration is a no-op. A corrupted chunk is detected and fetched again. Credentials are referenced by id, kept separate by side, and a source credential is refused on the target seam.
Validation gates cutover on shape equivalence (record count, kinds, vector count, embedding dimensions) and on a sampled content comparison. A pass therefore means no record was lost or added and every sampled record matches; it is not a byte-exhaustive proof, because an in-place change to an unsampled record would not be detected. On failure, authority stays with the source. The cutover watermark moves authority exactly once, and rollback discards or quarantines the target scope and is refused once cutover has been confirmed.
The source of a CLI migration is the project in the local engine, and the target is another engine at --target-dir. Any step that would provision a real cloud resource is gated behind an explicit approval in the library, and the CLI does not expose it.
Where you reach it
- CLI
kynetra migrate plan --source-project <id> --target-project <id> (alias: dry-run) - CLI
kynetra migrate run | resume --source-project --target-dir --target-project --work-dir [--allow-nonempty-target] - CLI
kynetra migrate rollback --target-dir --source-project --target-project [--quarantine]
Limits
- No cloud transport is implemented. The shipped transport moves data between local directories. To move a project between hosts today, use the portable bundle push and pull.
- Validation compares shape and a sample of content, not every record.
- Like the other backup commands, it opens the local data directory directly. Run it against a stopped server or a copy.
- It moves one KynetraDB project to another. Moving data from an external database is covered on the migration page.
Evidence
- On this siteMigration sources and limits
- TestsCovered in the engine repository by 20 migration tests (inventory, compatibility, dry run, end-to-end move, restart survival, resume without re-transfer, corrupted chunk, single cutover, failed validation keeps the source authoritative, rollback, credential separation, no cloud by default, single-project isolation)
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to talk through the limits above against your own workload.