Migration Series

Databricks Migration with MigrationRoom

Let the agent move it. Prove where it belongs.

A 4-hour hands-on lab: use MigrationRoom's AI-assisted workflow to move a Databricks TPC-H workload, prove Unity Catalog and a second REST catalog can stay zero-copy, and build a measured ClickHouse-native hot path.

4 hoursAdvanced8 modules
DatabricksMigrationRoomUnity CatalogMergeTree

What you will do

8 modules, in order

  1. 00

    Create a new Databricks environment and open the MigrationRoom dashboard.

  2. 01

    Use MigrationRoom's first UI action to discover the live Databricks workload.

  3. 02

    Challenge the agent's ClickHouse schema proposal in chat before approving DDL.

  4. 03

    Drive the copy, parity gate, and SQL rewrites from the MigrationRoom UI.

  5. 04

    Compare equivalent Databricks and ClickHouse queries through MigrationRoom.

  6. 05

    Use MigrationRoom chat to query Unity, another REST catalog, and native ClickHouse together.

  7. 06

    Let MigrationRoom optimize the workload, approve each change, and benchmark again.

  8. 07

    Make keep, federate, or materialize decisions from evidence, then remove participant resources.

EN