migrating-dbt-core-to-fusion

To migrate a dbt Core project to Fusion, follow the step-by-step workflow: run dbtf debug and dbtf parse, apply autofixes, manually resolve remaining issues using references, and run dbtf compile to ensure a clean migration.

Migrating to Fusion requires addressing deprecated dbt Core features by aligning your project with Fusion's authoring layer, resolving misspelled keys, custom configurations, and dynamic SQL through resource-driven manual remediation tips.

Yes, the migration workflow recommends using an autofix step to automatically resolve compatibility issues, followed by manual fixes via the references directory for custom configurations and dynamic SQL to achieve zero errors.

The best way to document code changes during a dbt Fusion migration is to generate a Migration Changes Summary template (changes_made.md), providing an audit-ready record of code changes and their rationale.

dbtf compile may fail after migrating to Fusion if deprecated features or misspelled keys remain; use the references directory for manual remediation tips and validate the project using dbtf debug and parse before compiling.

Yes, running dbtf debug and dbtf parse is required to verify connections and identify deprecations early, ensuring a smooth migration path to dbt Fusion with zero compilation errors.