Databricks does not provide a built‑in way to “move” or migrate a Unity Catalog (UC) metastore from one Databricks account to another.

Here is the list of activities that you can try

Inventory & plan:

1.  Enumerate catalogs, schemas, tables (Delta vs. external), views (incl. dynamic views), volumes, models, notebooks to move.
2. Identify tables on DBFS root and migrate them to cloud storage before the move. [stackoverflow.com]

Stand up destination objects with Terraform:

1. Create metastore, storage credentials, external locations, catalogs/schemas.
2. Define grants with databricks_grants resources.

Move data: 

1. Preferred: Delta Sharing from source → destination; then DEEP CLONE or CTAS to materialize.
2. Alternative: Export files (Delta/Parquet/CSV) to shared cloud storage, then register in destination. (Avoid DBFS root.)

Recreate dependent objects: 

1. Views/materialized views: recreate with destination names/paths.
2. Streaming tables: consider deep clone to carry stream metadata, or rebuild pipelines as needed.

Reapply governance: 

1. Use Terraform (or SQL) to apply catalog/schema/table grants; if you used shares, governance on shared assets follows UC rules.