diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx
index 121a1e89..6351d54d 100644
--- a/dbt-guides/dbt-fusion-migration.mdx
+++ b/dbt-guides/dbt-fusion-migration.mdx
@@ -12,6 +12,16 @@ Unlike dbt 1.10 which is an incremental update, Fusion represents a fundamental
     Important: dbt Fusion is still in beta, which means some dbt functionality is not supported at present. Please review the [dbt Fusion supported features and current limitations documentation](https://docs.getdbt.com/docs/fusion/supported-features) before proceeding with this migration.
 </Warning>
 
+## Using dbt Fusion with Lightdash
+
+dbt Fusion is compatible with Lightdash for both local development and cloud-based compilation, but a few behaviors differ from dbt Core.
+
+**Local development with Lightdash CLI**  
+You can use the dbt Fusion CLI (`dbtf`) together with the Lightdash CLI. The Lightdash CLI does not run dbt itself; it simply reads the manifest (`manifest.json`) generated by your dbt tool. Because dbt Fusion produces a Core-compatible manifest, the Lightdash CLI works the same whether you use `dbt` or `dbtf` locally.
+
+**Connecting a Fusion project to Lightdash**  
+When you connect your dbt project in the Lightdash UI, you will be asked which dbt version your project uses. Since Lightdash compiles your project using **dbt Core 1.10+** on its servers, you should select **dbt Core 1.10+**, even if you use dbt Fusion locally. dbt Fusion follows the same project configuration model as dbt 1.10+ and produces a manifest that Lightdash can compile using Core.
+
 ## Recommended Migration Process
 ### Step 1: Upgrade to dbt 1.10 and Fix Warnings
 
@@ -19,12 +29,14 @@ Unlike dbt 1.10 which is an incremental update, Fusion represents a fundamental
 2. Use Lightdash's [MetaMove CLI](https://docs.lightdash.com/dbt-guides/dbt-1.10-migration#automated-migration-with-metamove) to automatically migrate `meta` and `tags` from top-level properties to `config` blocks.
 3. Run your dbt project and address any other deprecation warnings before proceeding. Note you can also use [dbt-autofix](https://github.com/dbt-labs/dbt-autofix) to automatically resolve many deprecation warnings.
 
+<Note>
+    We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon.
+</Note>
+
 ### Step 2: Migrate to Fusion (only required for dbt Core users)
 Once all deprecation warnings are resolved, dbt Core users will need to follow the steps below to migrate to the dbt Fusion engine. dbt Cloud users, however, can wait for automatic rollout - dbt Labs will handle the dbt Fusion migration automatically. 
 
 #### For dbt Core Users: 
 1. Check that you meet the [dbt Fusion migration prerequisites](https://docs.getdbt.com/docs/fusion/install-fusion#prerequisites)
 2. Install the dbt Fusion engine following the [installation guide](https://docs.getdbt.com/docs/fusion/install-fusion#install-fusion)
-3. Run your project with dbt Fusion to identify any compatibility issues.
-
-
+3. Run your project with dbt Fusion to identify any compatibility issues.
\ No newline at end of file