migrating-dbt-core-to-fusion

Triage dbt Fusion migration errors by running dbt-autofix first, then reproducing failures with dbt compile or a custom command. Analyze the resulting compile output and git diffs to classify errors into Auto-Fixable, Guided Fixes, Needs Your Input, or Blocked categories.

Auto-fixable dbt Fusion migration errors include SQL, Jinja, YAML, and package compatibility issues that dbt-autofix successfully resolves. You must run dbt-autofix and review its git diffs to identify which errors are automatically corrected without manual intervention.

dbt Fusion migration compilation failures stem from SQL, Jinja, YAML, package, static analysis, or Fusion engine gaps. Run dbt debug to surface credential issues, then use a repro command like dbt compile to identify the specific compiler or runtime error blocking your migration.

You must run dbt-autofix before triaging Fusion migration errors to avoid duplicate or conflicting changes. The triage process requires analyzing dbt-autofix output and its git diffs to accurately separate auto-fixed issues from those needing guided fixes or user input.

Handle dbt Fusion engine blockers by searching GitHub issues to identify known gaps and suggest safe workarounds. Blocked errors are classified separately, providing risk descriptions and issue links so you can track engine limitations preventing migration progress.