Historically, customers have used mount points to connect their Databricks workspaces to their chosen cloud object storage, and many chose to utilize file paths as opposed to tables for accessing their data. For these long-time customers, the migration process is extremely manual, slow, and disruptive. This drastically decreases the chances of legacy customers upgrading their environment to Unity Catalog, which over time will lead to increased customer churn in favor of other platforms which do not require such a manual refactoring. Until now, we have not been able to provide an easier path forward for these customers.
Historically, customers have used mount points to connect their Databricks workspaces to their chosen cloud object storage, and many chose to utilize file paths as opposed to tables for accessing their data. For these long-time customers, the migration process is extremely manual, slow, and disruptive. This drastically decreases the chances of legacy customers upgrading their environment to Unity Catalog, which over time will lead to increased customer churn in favor of other platforms which do not require such a manual refactoring. Until now, we have not been able to provide an easier path forward for these customers.