# Migration to a sovereign lakehouse

> Migrating to DataNature lands source data in an immutable Bronze layer, reprocesses it through open engines (Spark, Trino, Kafka and dbt) and validates every output against the old system using Atlas lineage before cutover. Because DataNature is containerized and uses open Delta and Iceberg tables, the result stays portable across clouds and on-premises.

Source: https://datanature.ai/solutions/migration-to-sovereign-lakehouse
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

Move from legacy warehouses, Hadoop or cloud platforms without a big bang

## Components

- **Connect**: Land legacy sources in Bronze
- **Data Engineering workbench**: Rebuild pipelines in dbt and Spark
- **Atlas**: Lineage-based reconciliation
- **Lakehouse**: Delta and Iceberg tables, both native

## Steps

1. **Assess**: Inventory sources, pipelines, reports and users.
2. **Land**: Copy sources into immutable Bronze.
3. **Rebuild**: Port SQL, Spark and dbt; re-create jobs and permissions.
4. **Reconcile**: Run in parallel and compare outputs with Atlas lineage.
5. **Cut over**: Switch consumers, then retire the old platform.

## Documentation

- [Migration](https://docs.datanature.ai/docs/developers/resources/migration)

## Which platforms can we migrate from?

Legacy warehouses, Hadoop, and cloud platforms including Databricks and Snowflake. Spark, SQL and dbt code carries over with modest changes.

## How do we avoid a risky big-bang cutover?

Run old and new in parallel, reconcile outputs with lineage, and switch consumers in waves.

## Who does the work?

Dlytica Consulting and NeuralShore engineers, with knowledge transfer to your team.

## Common questions

### How do we avoid lock-in on the new platform?

Use open table formats, an open catalog protocol and dbt or Spark pipelines. See [lock-in moved to the catalog](/blog/avoid-data-platform-lock-in-catalog-layer).

### Why do data platform bills surprise teams?

Idle compute, premium rates and unbounded usage. See [keeping lakehouse costs predictable](/blog/lakehouse-cost-surprises-and-how-to-avoid-them).

### Does a Canadian cloud region make us sovereign?

Not on its own. See [the US CLOUD Act and Canadian data](/blog/us-cloud-act-and-canadian-data).

## Implementation details

1. **Inventory** tables, jobs, notebooks, permissions and dashboards; tag what must move and what can stay.
2. **Land data** in Bronze with Connect (or as files for platform exports); keep Bronze immutable for reprocessing.
3. **Port transformations**: SQL to Trino or Spark, dbt projects with a target change, Spark code to Spark 4.
4. **Move hot paths** to StreamHouse where the source platform ran streaming jobs.
5. **Recreate governance** as Atlas grants, row filters and masks scoped to schemas; test with non-admin accounts.
6. **Run in parallel** and reconcile Gold metrics per period; cut over one domain at a time.
