Upgrade to Unity Catalog without breaking a single job.
Your Databricks workspaces still run on the legacy Hive metastore. Access is set per workspace, lineage is missing and new features need Unity Catalog. We upgrade schema by schema, retire what nobody uses and repoint every job, with tests at each step.
From the old way to the new.
- A Hive metastore per workspace, with access set separately in each
- No lineage from a dashboard back to its source table
- Table ACLs and mount points nobody fully understands
- New Databricks features that need Unity Catalog, out of reach
- One catalog across workspaces, with access set once by role
- Lineage from every report back to the source
- Storage credentials and external locations replacing mounts
- Serverless, AI/BI and other Unity Catalog features available
The upgrade everyone postpones, because jobs might break.
Unity Catalog is where Databricks is heading, but the upgrade touches every table, grant, mount and job. Teams put it off because nobody can say which job reads which table, and a missed dependency breaks a report on Monday morning.

- Grants are scattered across workspaces and table ACLs.
- Jobs read tables through mount points that will not carry over.
- Nobody knows which old tables are still read.
- External tables and managed tables need different handling.
- The upgrade plan keeps growing as hidden dependencies surface.
- You have several workspaces with different access rules.
- Auditors ask who can see what, and the answer takes weeks.
- You want serverless or AI/BI, and they need Unity Catalog.
- The upgrade has been on the roadmap for more than a quarter.
Why it mattered. Every month on the Hive metastore keeps access scattered and keeps newer Databricks features out of reach.
Assess, upgrade schema by schema, then repoint and test.
We start with an assessment of every table, grant, mount and job, using Databricks' own upgrade tooling. Unused tables are retired. The rest move schema by schema, with grants rewritten by role and every job repointed and tested before the old path is removed.
One catalog, every job tested.
- An assessment of every table, view, grant, mount and job, with each marked upgrade, retire or rework.
- Unity Catalog metastore, catalogs and schemas laid out by domain and environment.
- Storage credentials and external locations replacing mount points.
- Grants rewritten by role at catalog, schema, table and column level.
- Every job and notebook repointed to Unity Catalog tables and tested.
- Lineage and audit logs switched on, with a short guide for your team.
- Week 1AuditData profiled, scope and fee fixed
- ThenBuildOne area at a time, tested with your users
- OngoingOperateQuarterly reviews of quality, access and spend