# Leaving a managed platform: what moves and what does not

Guide, read 10 Nov 2026

**The short answer.** Moving Spark batch work off Databricks or Snowflake splits into parts that travel as files and code, parts that need edits, and parts that stay behind, such as automatic maintenance and billing commitments. This page lists each part with the vendor documentation that says so.

## What moves as files

Open table formats keep data in Parquet files. Databricks documents that Delta tables can generate Iceberg metadata through UniForm from Databricks Runtime 14.3 LTS, so Iceberg clients read them without rewriting data files. Delta Lake's own docs describe UniForm as generating the metadata asynchronously for Iceberg and Hudi clients.

On Snowflake, Iceberg tables with an external volume sit in customer-managed S3, Google Cloud Storage or Azure storage, so the data files are already yours. Snowflake also documents that you can move Iceberg data from Snowflake storage to your own cloud storage at any time with CTAS at standard rates.

## A published exit incentive

Snowflake states that it will reimburse the eligible Snowflake compute costs of a qualifying one-time migration of Iceberg data to customer-owned storage in the same cloud platform and region as the Snowflake account. The conditions on the page: the data must have been in Snowflake storage for at least 30 days, and the total size must be at least 1 TB. Contact is through Snowflake Support.

No equivalent offer appears in the Databricks pages read on 2026-11-10.

## What moves with edits

Spark code moves in proportion to how much of it is standard Spark. Snowpark Connect runs PySpark DataFrame code on Snowflake warehouses, so that code is already written to the Spark Connect protocol, but Snowflake documents semantic differences: ByteType, ShortType and IntegerType come back as LongType, and several interval and user-defined types are unsupported. Code tested only on Snowflake needs a check against real Spark behavior. Snowflake supports Spark 3.5 only, which is the line Amazon EMR 7.14.0 ships as Spark 3.5.8-amzn-0.

Databricks code that uses platform features does not move unchanged. The serverless compute page lists Databricks Container Services, DBFS mounts with instance profiles and global temp views as unsupported on serverless, which tells you what the other direction would rely on. Photon is a Databricks runtime feature; EMR has its own runtime, and the two are separate products with separate published claims.

## What stays behind

Automatic maintenance does not travel. Databricks predictive optimization runs OPTIMIZE, VACUUM and ANALYZE only on Unity Catalog managed tables. Snowflake runs compaction, manifest compaction and snapshot expiry on Snowflake-managed Iceberg tables, and states it performs no maintenance on tables managed by an external catalog, where you must expire snapshots, remove old metadata and compact files in your own engine.

In an open stack that work becomes jobs you schedule or services you turn on. Iceberg's documentation lists expiring snapshots, removing old metadata files and deleting orphan files as recommended maintenance. AWS offers Glue table optimizers and S3 Tables maintenance for Iceberg. See [compaction on each platform](/maintenance/compaction-on-each-platform/).

Billing arrangements also stay: Databricks offers committed-use discounts on DBUs, so check the contract end date against the migration plan.

## Catalog and permissions

The catalog decides who can find and write a table. Snowflake Open Catalog is a managed service for Apache Polaris, and Snowflake states that customers who had not already created an Open Catalog account cannot sign up for a first one. Unity Catalog has an Apache-2.0 open-source project hosted under LF AI & Data, with Delta Lake and an Iceberg REST Catalog API. The [catalogs guide](/guides/lakehouse-catalogs-for-tables/) lists the options.

Databricks serverless compute needs Unity Catalog to reach external data sources, so the catalog is part of the platform, not an add-on you can leave behind.

## Where the compute can land

Vendors in alphabetical order, only for Spark batch work. Amazon EMR on EC2, EKS or Serverless runs Spark code with AWS describing the runtime as 100% API-compatible. Dremio runs its own Arrow-based engine, and its documentation describes no mode that runs existing Spark jobs. Onehouse says its jobs are fully compatible with Apache Spark and that EMR code can be reused unless it uses AWS-specific features; its Quanton clusters run in your AWS account. Starburst Galaxy runs SQL on Trino, so Spark DataFrame code and UDFs would be rewritten or kept on Spark.

Microsoft Fabric lists Azure regions only, so its Spark compute does not run inside AWS, and its OneLake S3 shortcuts give read-only access to S3 data.

## A short list of checks

- Which tables are Snowflake-managed or Unity Catalog managed, and which sit under an external catalog.
- Which Spark version the code runs on today and which versions the target runtime ships.
- Which notebooks or jobs use serverless-only or warehouse-only behavior.
- Who runs compaction, snapshot expiry and orphan-file cleanup after the move.
- Contract dates for committed spend, and whether the Snowflake 1 TB and 30-day migration conditions apply.

## Sources

- Databricks UniForm: https://docs.databricks.com/aws/en/delta/uniform (read 10 Nov 2026)
- Delta Lake UniForm: https://docs.delta.io/latest/delta-uniform.html (read 10 Nov 2026)
- Snowflake Iceberg storage: https://docs.snowflake.com/en/user-guide/tables-iceberg-storage (read 10 Nov 2026)
- Snowflake Iceberg table management: https://docs.snowflake.com/en/user-guide/tables-iceberg-manage (read 10 Nov 2026)
- Snowpark Connect for Apache Spark: https://docs.snowflake.com/en/developer-guide/snowpark-connect/snowpark-connect-apache-spark (read 10 Nov 2026)
- Snowpark Connect compatibility: https://docs.snowflake.com/en/developer-guide/snowpark-connect/snowpark-connect-compatibility.md (read 10 Nov 2026)
- Snowpark Connect limitations: https://docs.snowflake.com/en/developer-guide/snowpark-connect/snowpark-connect-limitations.md (read 10 Nov 2026)
- Databricks serverless compute limitations: https://docs.databricks.com/aws/en/compute/serverless/limitations (read 10 Nov 2026)
- Databricks predictive optimization: https://docs.databricks.com/aws/en/optimizations/predictive-optimization (read 10 Nov 2026)
- Databricks pricing: https://www.databricks.com/product/pricing (read 10 Nov 2026)
- Amazon EMR 7.x release versions: https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-release-app-versions-7.x.html (read 10 Nov 2026)
- Apache Iceberg maintenance: https://iceberg.apache.org/docs/latest/maintenance/ (read 10 Nov 2026)
- Snowflake Open Catalog overview: https://docs.snowflake.com/en/user-guide/opencatalog/overview (read 10 Nov 2026)
- Unity Catalog open source: https://www.unitycatalog.io/ (read 10 Nov 2026)
- Dremio architecture: https://docs.dremio.com/current/what-is-dremio/architecture (read 10 Nov 2026)
- Onehouse EMR migration: https://docs.onehouse.ai/product/jobs/emr-migration (read 10 Nov 2026)
- Starburst Galaxy documentation: https://docs.starburst.io/starburst-galaxy/index.html (read 10 Nov 2026)
- Fabric OneLake S3 shortcuts: https://learn.microsoft.com/en-us/fabric/onelake/create-s3-shortcut (read 10 Nov 2026)
- AWS Big Data Blog, EMR 7.12 and Iceberg benchmark: https://aws.amazon.com/blogs/big-data/run-apache-spark-and-iceberg-4-5x-faster-than-open-source-spark-with-amazon-emr/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/guides/leaving-a-managed-platform/
