<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Upgrade HSM to UC using Ucx tool - workspace to workspace migration in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/83559#M36956</link>
    <description>&lt;P&gt;Hello team,&lt;/P&gt;&lt;P&gt;I understand that an automatic upgrade to UC utilizing the UCx tool (Databricks Lab project) is now available to complete this migration from HSM to UC in automate way. But does this tool allow workspace to workspace catalog/artifact migration ? That is, I have an HSM workspace, and if the client wants to upgrade the Catalog to UC with a new or another (fresh) workspace rather than an in-place migration. So, does the UCX tool provide this capability for workspace to workspace migrations ? If not, please let me know of an alternative strategy to automating this procedure using UCx or any other Lab initiatives. Kindly assist me if any limitations around those approaches as well.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Aug 2024 07:37:34 GMT</pubDate>
    <dc:creator>ShivMukesh</dc:creator>
    <dc:date>2024-08-20T07:37:34Z</dc:date>
    <item>
      <title>Upgrade HSM to UC using Ucx tool - workspace to workspace migration</title>
      <link>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/83559#M36956</link>
      <description>&lt;P&gt;Hello team,&lt;/P&gt;&lt;P&gt;I understand that an automatic upgrade to UC utilizing the UCx tool (Databricks Lab project) is now available to complete this migration from HSM to UC in automate way. But does this tool allow workspace to workspace catalog/artifact migration ? That is, I have an HSM workspace, and if the client wants to upgrade the Catalog to UC with a new or another (fresh) workspace rather than an in-place migration. So, does the UCX tool provide this capability for workspace to workspace migrations ? If not, please let me know of an alternative strategy to automating this procedure using UCx or any other Lab initiatives. Kindly assist me if any limitations around those approaches as well.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Aug 2024 07:37:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/83559#M36956</guid>
      <dc:creator>ShivMukesh</dc:creator>
      <dc:date>2024-08-20T07:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade HSM to UC using Ucx tool - workspace to workspace migration</title>
      <link>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/139308#M51144</link>
      <description>&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The UCx (Databricks Labs UCx tool) automates many aspects of migrating from HSM (Hive Metastore) to Unity Catalog (UC), but its default operation focuses on upgrading the catalog within the same workspace (an in-place migration). As of the most recent updates,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;UCx does not natively support automatic migration of catalogs/artifacts across different workspaces&lt;/STRONG&gt;—that is, it does not directly handle a full workspace-to-workspace migration to a fresh workspace with Unity Catalog.&lt;/P&gt;
&lt;H2 class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0"&gt;UCx Tool Capabilities and Limitations&lt;/H2&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The UCx tool is designed primarily for upgrading the catalog and artifacts within the original source workspace.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;It automates catalog conversion, permissions, and data lineage mostly for the in-place upgrade scenario.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Artifacts such as tables, managed/external locations, ACLs, and lineage are usually mapped within the same workspace context.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Direct workspace-to-workspace automation—the kind you described—is&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;not provided out of the box&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;by UCx as of late 2025.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2 class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0"&gt;Alternative Migration Strategies&lt;/H2&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;If you need to migrate HSM artifacts to UC in a new or different workspace, you can consider the following approaches:&lt;/P&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Manual Export/Import&lt;/STRONG&gt;: Use Databricks’ export utilities or custom scripts to export tables, views, and permissions from the HSM workspace, then reconstruct them in the new workspace with UC enabled.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Delta Lake Data&lt;/STRONG&gt;: If tables are backed by Delta Lake, you can "register" the underlying Delta tables in a new workspace/catalog after copying physical files.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Workspace API Automation&lt;/STRONG&gt;: Develop automation scripts using Databricks REST API to recreate catalogs, databases, tables, and permissions in the target workspace after upgrading to UC.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Databricks Partner Solutions/Labs Projects&lt;/STRONG&gt;: Watch for new Databricks Labs projects or partner tools, but as of now there’s&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;no officially supported or widely used tool for workspace-to-workspace automated UC migration&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2 class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0"&gt;Limitations to Consider&lt;/H2&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Identity &amp;amp; Permissions&lt;/STRONG&gt;: Mapping and migrating ACLs between workspaces is complex, as identity (users/groups) might differ.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Physical Data Location&lt;/STRONG&gt;: Migrating managed tables might require physically moving files in cloud storage; UCx does not automate this if the storage buckets differ between workspaces.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Lineage/History Loss&lt;/STRONG&gt;: Full lineage and usage history might not transfer automatically between workspaces.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;Manual Effort&lt;/STRONG&gt;: Even script-based automation will require careful validation and may not be fully hands-off.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2 class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0"&gt;Summary Table&lt;/H2&gt;
&lt;DIV class="group relative"&gt;
&lt;DIV class="w-full overflow-x-auto md:max-w-[90vw] border-subtlest ring-subtlest divide-subtlest bg-transparent"&gt;
&lt;TABLE class="border-subtler my-[1em] w-full table-auto border-separate border-spacing-0 border-l border-t"&gt;
&lt;THEAD class="bg-subtler"&gt;
&lt;TR&gt;
&lt;TH class="border-subtler p-sm break-normal border-b border-r text-left align-top"&gt;Approach&lt;/TH&gt;
&lt;TH class="border-subtler p-sm break-normal border-b border-r text-left align-top"&gt;Automation Level&lt;/TH&gt;
&lt;TH class="border-subtler p-sm break-normal border-b border-r text-left align-top"&gt;Supported by UCx&lt;/TH&gt;
&lt;TH class="border-subtler p-sm break-normal border-b border-r text-left align-top"&gt;Limitations&lt;/TH&gt;
&lt;/TR&gt;
&lt;/THEAD&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;In-place UCx migration&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;High&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Yes&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Only same workspace&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Workspace-to-workspace w/ UCx&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Low&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;No&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Manual scripting needed&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Delta Lake register in new WS&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Medium&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;No&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Data path must be accessible&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;REST API/scripted recreation&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Medium&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;No&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Identity/permissions challenges&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Manual export/import&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Low&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;No&lt;/TD&gt;
&lt;TD class="px-sm border-subtler min-w-[48px] break-normal border-b border-r"&gt;Labor-intensive&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;DIV class="bg-base border-subtler shadow-subtle pointer-coarse:opacity-100 right-xs absolute bottom-0 flex rounded-lg border opacity-0 transition-opacity group-hover:opacity-100 [&amp;amp;&amp;gt;*:not(:first-child)]:border-subtle [&amp;amp;&amp;gt;*:not(:first-child)]:border-l"&gt;
&lt;DIV class="flex"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="flex"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;&lt;STRONG&gt;In conclusion, the UCx tool does not currently support fully automated workspace-to-workspace migrations. You will need to employ alternative methods such as API-driven or scripted automation, manual procedures, or leverage Delta Lake features as appropriate, keeping in mind limitations regarding identities, permissions, and lineage transfer in multi-workspace migration scenarios&lt;/STRONG&gt;.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2025 11:37:08 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/139308#M51144</guid>
      <dc:creator>mark_ott</dc:creator>
      <dc:date>2025-11-17T11:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade HSM to UC using Ucx tool - workspace to workspace migration</title>
      <link>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/139383#M51182</link>
      <description>&lt;P&gt;I was involved in the simialr request in past where we did use UCX for the in-place workpsace. However, as we had to split few data assets to a different workspace, it was pretty much done using custom workarounds as mentioned above.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2025 15:31:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/139383#M51182</guid>
      <dc:creator>Raman_Unifeye</dc:creator>
      <dc:date>2025-11-17T15:31:20Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade HSM to UC using Ucx tool - workspace to workspace migration</title>
      <link>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/139391#M51184</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/116680"&gt;@ShivMukesh&lt;/a&gt;&amp;nbsp;I have used UCX to migrate to Unity catalog. It is a great tool. But it also involves lot of workarounds specially in group migration and table migration. In group migration it renames the old workspace group and assigns the same permission to the account group. You have to run some custom scripts to cleanup the old group. Also it didn't suppported view migration while I was working starting this year.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Nov 2025 15:49:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/upgrade-hsm-to-uc-using-ucx-tool-workspace-to-workspace/m-p/139391#M51184</guid>
      <dc:creator>nayan_wylde</dc:creator>
      <dc:date>2025-11-17T15:49:57Z</dc:date>
    </item>
  </channel>
</rss>

