Migrate into TypeDB

Sources: Self-hosted TypeDB or TypeDB Cloud (3.11 or newer), another Databasezy instance.

How the copy works

typedb console runs database export <db> schema.tql data.typedb on the source and database import <db> schema.tql data.typedb on the target, inside the migration Job. Name the database in the URL path (typedb://user:password@host:1729/<database>); typedbs:// (or an https:// host outside the cell) uses TLS.

Run it

shell

# --dry-run prints the preflight checklist and the exact plan without changing anything
zb migrate --from "typedbs://admin:[email protected]:1729/social" --engine typedb --to inst_abc

Follow it with zb migrate status <mig_id>, or in the portal under the instance’s Migrate in tab.

What is verified

The target schema is compared with the source (a schema hash); instance counts are not compared. Mismatches are listed in the result; nothing is switched for you.

Not carried over

• Both sides must run TypeDB 3.11 or newer: the migration uses TypeDB Console 3.13, and TypeDB 3.11 changed the network protocol, so older servers and newer consoles refuse each other. Upgrade an older source to 3.11 or newer first.
• The whole database is exported; --include / --exclude do not apply.
• Copy only; writes during the export are not carried over.

How migrations work covers preflight, verification and cutover; engine conversions covers moves between engines.