diff --git a/migrating_from_ocp_3_to_4/installing-3-4.adoc b/migrating_from_ocp_3_to_4/installing-3-4.adoc
index b2adc82c1684..80def1bf21a4 100644
--- a/migrating_from_ocp_3_to_4/installing-3-4.adoc
+++ b/migrating_from_ocp_3_to_4/installing-3-4.adoc
@@ -17,6 +17,7 @@ By default, the {mtc-short} web console and the `Migration Controller` pod run o
 
 After you have installed {mtc-short}, you must configure an object storage to use as a replication repository.
 
+include::modules/migration-compatibility-guidelines.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-3.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+1]
diff --git a/migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc b/migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
index 79566fcd9847..e17d394d53eb 100644
--- a/migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
+++ b/migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
@@ -19,6 +19,7 @@ You can configure the `Migration Controller` custom resource manifest to run the
 
 After you have installed {mtc-short}, you must configure an object storage to use as a replication repository.
 
+include::modules/migration-compatibility-guidelines.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-3.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+1]
diff --git a/migration_toolkit_for_containers/installing-mtc-restricted.adoc b/migration_toolkit_for_containers/installing-mtc-restricted.adoc
index df8f6ce97f59..9030da0f21df 100644
--- a/migration_toolkit_for_containers/installing-mtc-restricted.adoc
+++ b/migration_toolkit_for_containers/installing-mtc-restricted.adoc
@@ -19,6 +19,7 @@ You can configure the `Migration Controller` custom resource manifest to run the
 
 After you have installed {mtc-short}, you must configure an object storage to use as a replication repository.
 
+include::modules/migration-compatibility-guidelines.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+1]
 
diff --git a/migration_toolkit_for_containers/installing-mtc.adoc b/migration_toolkit_for_containers/installing-mtc.adoc
index c8e670d03d19..5f7cfc9af3e3 100644
--- a/migration_toolkit_for_containers/installing-mtc.adoc
+++ b/migration_toolkit_for_containers/installing-mtc.adoc
@@ -17,6 +17,7 @@ By default, the {mtc-short} web console and the `Migration Controller` pod run o
 
 After you have installed {mtc-short}, you must configure an object storage to use as a replication repository.
 
+include::modules/migration-compatibility-guidelines.adoc[leveloffset=+1]
 include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+1]
 
diff --git a/modules/migration-compatibility-guidelines.adoc b/modules/migration-compatibility-guidelines.adoc
new file mode 100644
index 000000000000..cbe052b94c4b
--- /dev/null
+++ b/modules/migration-compatibility-guidelines.adoc
@@ -0,0 +1,24 @@
+// Module included in the following assemblies:
+//
+// * migrating_from_ocp_3_to_4/installing-3-4.adoc
+// * migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc
+// * migration_toolkit_for_containers/installing-mtc.adoc
+// * migration_toolkit_for_containers/installing-mtc-restricted.adoc
+
+[id="migration-compatibility-guidelines_{context}"]
+= Compatibility guidelines
+
+You must install the {mtc-full} ({mtc-short}) version that is compatible with your {product-title} version.
+
+[cols="1,1", options="header"]
+.{product-title} and {mtc-short} compatibility
+|===
+|{product-title} version |{mtc-short} version^[1]^
+|3.7 to 4.5 |1.5.x
+|4.6 or later |1.6.x
+|===
+1. Install the latest z-stream version.
+
+You can migrate workloads from a source cluster with {mtc-short} 1.5.x installed to a target cluster with {mtc-short} 1.6.x installed as long as the `MigrationController` custom resource and the {mtc-short} web console are running on the target cluster.
+
+You cannot install {mtc-short} 1.6.x on a cluster with {product-title} 3.7 to 4.5 installed because the custom resource definition API versions are incompatible.