migrating-dbt-project-across-platforms

Migrates a dbt project between Snowflake and Databricks using dbt Fusion's real-time compilation to fix SQL dialect differences.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/randoneering/nix-flake-mirror --skill migrating-dbt-project-across-platforms-randoneering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-dbt-project-across-platforms
Source: https://github.com/randoneering/nix-flake-mirror/tree/main/home/programs/opencode/skills/dbt/dbt-migration/skills/migrating-dbt-project-across-platforms
Command: npx skills add https://github.com/randoneering/nix-flake-mirror --skill migrating-dbt-project-across-platforms-randoneering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating a dbt project between data platforms (e.g., Snowflake to Databricks, or Databricks to Snowflake) is notoriously complex due to dialect gaps, configuration drift, and validation challenges. This skill guides the end-to-end migration using dbt Fusion's real-time compilation to identify and fix SQL dialect differences.

Core Features & Use Cases

  • Guided, end-to-end migration workflow across platforms
  • Real-time compilation error reporting to surface dialect differences
  • Step-by-step validation: compile on target, generate unit tests, switch targets, and run final validation on the destination platform

Quick Start

Start the migration by following the Migration Workflow to assess the source, switch to the destination target, and validate the results on the target platform.

Frequently Asked Questions about migrating-dbt-project-across-platforms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a dbt project from Snowflake to Databricks?

To migrate a dbt project from Snowflake to Databricks, use dbt Fusion's real-time compilation to identify and fix SQL dialect differences, generate unit tests, and validate the final build on the target platform.

How does dbt Fusion handle SQL dialect differences during cross-platform migration?

dbt Fusion handles SQL dialect differences during cross-platform migration by utilizing real-time compilation error reporting to surface gaps and configuration drift between data platforms like Snowflake and Databricks.

What is the best way to validate dbt models after switching data platforms?

The best way to validate dbt models after switching data platforms is to compile with zero errors, generate source tests, run target compilation, and validate results before executing a final build on the destination platform.

Can I use this guided workflow to migrate dbt projects between any data platforms?

You can use this workflow to migrate dbt projects between similar engines like Snowflake and Databricks, applying compilation, unit tests, and final validation to ensure zero errors on the destination target.

Why does my dbt project fail to compile when migrating to a new data platform?

A dbt project fails to compile during migration due to SQL dialect gaps and configuration drift between platforms, which dbt Fusion identifies through real-time compilation error reporting for step-by-step resolution.

Do I need to generate unit tests before switching dbt targets?

You need to generate source tests and compile with zero errors on the source platform before switching dbt targets, ensuring that the migration validation process successfully identifies any SQL dialect differences.