Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Data Engineering & Analytics

Data Warehouse to Lakehouse Migration

Warehouse migrations are usually estimated from a table count and then run late on the stored procedures, ETL jobs and reports nobody listed. We inventory what is really used, convert with tooling plus engineering review, run old and new side by side and cut over only when the numbers match.

Sound familiar?

  • A Teradata, Netezza or Exadata renewal or hardware refresh is coming and finance wants the move to the cloud costed.
  • Hadoop or Cloudera clusters still run Hive, Impala, Oozie and Sqoop jobs that the people who wrote them no longer maintain.
  • Azure Synapse or Power BI Premium capacity needs a plan now that Microsoft points customers to Fabric.
  • A previous migration stalled on BTEQ scripts, stored procedures or reports whose numbers never matched.

What you receive

  • Inventory with every object in scope, retired or owned
  • Target architecture and wave plan
  • Converted code in your repository
  • Reconciliation report per wave
  • Cut-over runbooks and decommission plan

Book a free 30-minute review

What we deliver

Scope is confirmed in writing in the assessment, with anything out of scope listed too.

  1. 01

    Estate inventory

    Objects, code, jobs, schedules, consumers and query history profiled, with unused objects marked for retirement.

  2. 02

    Target and wave plan

    A Snowflake, Databricks or Fabric target and subject-area waves that respect dependencies.

  3. 03

    Code conversion

    SQL, stored procedures and ETL converted with tools such as Databricks Lakebridge or Snowflake SnowConvert where they help, every object reviewed by an engineer.

  4. 04

    Data movement

    Bulk history loads plus incremental or change-data-capture feeds, so the new platform stays current while the old one still runs.

  5. 05

    Reconciliation

    Row counts, sums and key hashes compared table by table, and the reports business users rely on compared side by side.

  6. 06

    Cut-over and decommission

    BI and downstream feeds repointed, the old system kept read-only for an agreed rollback window, then switched off.

Fixed scope and a fixed fee, agreed in writing.

Every engagement is scoped after a free 30-minute review. The scope and fee are confirmed in writing before work starts, and the assessment fee is credited toward the project.

Step 01

Migration readiness sprint

Fixed fee, scoped after the free review

Inventory, wave plan, a pilot on the hardest object and a fixed migration quote. Credited toward the migration.

Step 02

Migration waves

Fixed fee, scoped after the free review

Scoped per subject area from the sprint, agreed in writing before work starts.

From first call to delivery

You can stop after any step and keep everything we have written.

  1. 01

    Free

    Free 30-minute review

    We look at what you run, what is urgent and whether a fixed-fee engagement fits. You get a short written summary.

  2. 02

    2–4 weeks · credited

    Migration readiness sprint

    Inventory, wave plan, pilot on the hardest object and a fixed quote.

  3. 03

    Per subject area

    Migration waves

    Converted, run side by side, reconciled and cut over with a way back.

Technologies

  • Teradata
  • Apache Hadoop
  • Apache Hive
  • Oracle
  • SQL Server
  • Amazon Redshift
  • Azure Synapse Analytics
  • Google BigQuery
  • Snowflake
  • Databricks
  • Microsoft Fabric
  • Apache Spark
  • dbt

Names are trademarks of their owners. Listing does not imply partnership.

Questions about this service

Straight answers on scope, fees and how we work. Anything else, ask us.

Ask a question

Do automated converters do the whole job?

No. Tools such as Lakebridge and SnowConvert speed up routine SQL, but procedural code, macros and edge cases need an engineer to confirm the behaviour. We plan for both and report what was converted by tool and what by hand.

How do you prove the numbers match?

Each wave runs old and new side by side. Row counts, aggregates and key hashes are compared automatically, and business owners sign off the reports they rely on before cut-over.

Can Snowflake and Databricks share the same data?

Yes, through open table formats such as Apache Iceberg. The readiness sprint shows whether running both is worth the extra complexity for you.

What about Power BI Premium capacity?

Microsoft is retiring Power BI Premium P SKUs at the end of each agreement term and points customers to Fabric F SKUs. We include the capacity move in the plan when it applies.

Start with a free 30-minute review.

Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.