diff --git a/site/content/docs/main/migration-case.md b/site/content/docs/main/migration-case.md
index c547ebbb4..9ad7b809a 100644
--- a/site/content/docs/main/migration-case.md
+++ b/site/content/docs/main/migration-case.md
@@ -53,6 +53,7 @@ If you encounter issues, make sure that Velero is running in the same namespace
 ## Migrating Workloads Across Different Kubernetes Versions
 
 Migration across clusters that are not running the same version of Kubernetes might be possible, but some factors need to be considered: compatibility of API groups between clusters for each custom resource, and if a Kubernetes version upgrade breaks the compatibility of core/native API groups. For more information about API group versions, please see [EnableAPIGroupVersions](enable-api-group-versions-feature.md).
+**Note:** Velero doesn't support restoring into a cluster with a lower Kubernetes version than where the backup was taken.
 
 [1]: how-velero-works.md#set-a-backup-to-expire
 [2]: restic.md
diff --git a/site/content/docs/v1.6/migration-case.md b/site/content/docs/v1.6/migration-case.md
index c547ebbb4..9ad7b809a 100644
--- a/site/content/docs/v1.6/migration-case.md
+++ b/site/content/docs/v1.6/migration-case.md
@@ -53,6 +53,7 @@ If you encounter issues, make sure that Velero is running in the same namespace
 ## Migrating Workloads Across Different Kubernetes Versions
 
 Migration across clusters that are not running the same version of Kubernetes might be possible, but some factors need to be considered: compatibility of API groups between clusters for each custom resource, and if a Kubernetes version upgrade breaks the compatibility of core/native API groups. For more information about API group versions, please see [EnableAPIGroupVersions](enable-api-group-versions-feature.md).
+**Note:** Velero doesn't support restoring into a cluster with a lower Kubernetes version than where the backup was taken.
 
 [1]: how-velero-works.md#set-a-backup-to-expire
 [2]: restic.md
diff --git a/site/content/docs/v1.7/migration-case.md b/site/content/docs/v1.7/migration-case.md
index c547ebbb4..9ad7b809a 100644
--- a/site/content/docs/v1.7/migration-case.md
+++ b/site/content/docs/v1.7/migration-case.md
@@ -53,6 +53,7 @@ If you encounter issues, make sure that Velero is running in the same namespace
 ## Migrating Workloads Across Different Kubernetes Versions
 
 Migration across clusters that are not running the same version of Kubernetes might be possible, but some factors need to be considered: compatibility of API groups between clusters for each custom resource, and if a Kubernetes version upgrade breaks the compatibility of core/native API groups. For more information about API group versions, please see [EnableAPIGroupVersions](enable-api-group-versions-feature.md).
+**Note:** Velero doesn't support restoring into a cluster with a lower Kubernetes version than where the backup was taken.
 
 [1]: how-velero-works.md#set-a-backup-to-expire
 [2]: restic.md