diff --git a/openmetadata-docs/content/deployment/upgrade/index.md b/openmetadata-docs/content/deployment/upgrade/index.md
index 8cf558aef4d..a114fc74f9f 100644
--- a/openmetadata-docs/content/deployment/upgrade/index.md
+++ b/openmetadata-docs/content/deployment/upgrade/index.md
@@ -27,10 +27,17 @@ Explore 0.13.0 by following up [Deployment guides](https://docs.open-metadata.or
 
 If you are upgrading production this is the recommended version to upgrade.
   
- 
- 
- 
 ## Breaking Changes from 0.13.0 Feature Release
+
+OpenMetadata Release 0.13.0 introduces below breaking changes -
+### dbt Workflow
+
+dbt ingestion has been separated from the metadata ingestion. It can now be configured as a separate workflow after completing the metadata ingestion workflow.
+
+We will remove the dbt configuration from your existing metadata ingestion pipelines and they will keep working as expected.
+
+After upgrading you will have to create the dbt workflow for the dbt ingestion to start working again.
+
 ## Breaking Changes from 0.12.x Stable Release
 
 OpenMetadata Release 0.12.x introduces below breaking changes -
diff --git a/openmetadata-docs/content/deployment/upgrade/versions/012-to-013.md b/openmetadata-docs/content/deployment/upgrade/versions/012-to-013.md
index ff7ebf36293..a37e3bb418f 100644
--- a/openmetadata-docs/content/deployment/upgrade/versions/012-to-013.md
+++ b/openmetadata-docs/content/deployment/upgrade/versions/012-to-013.md
@@ -29,7 +29,7 @@ Starting with `0.13.0`, we have deprecated the initial configurations for Author
   - Airbyte connector now support Basic Authentication.
     - Added: `username`, `password`
 
-## Lineage Backend
+### Lineage Backend
 
 In 0.13.1:
 
@@ -37,3 +37,10 @@ In 0.13.1:
 to `airflow_provider_openmetadata.lineage.backend.OpenMetadataLineageBackend`.
 - We removed support from Airflow v1.
 - The failure callback now only updates the pipeline status if the Pipeline already exists in OpenMetadata.
+
+### dbt Workflow
+
+- Starting with `0.13.1` dbt ingestion has been separated from the metadata ingestion. It can now be configured as a separate workflow after completing the metadata ingestion workflow
+- We will remove the dbt configuration from your existing metadata ingestion pipelines and they will keep working as expected.
+- After upgrading you will have to create the dbt workflow for the dbt ingestion to start working again.
+- dbt workflow can be configured via going to `services->selecting your service->ingestion tab->Add DBT Ingestion`