diff --git a/_topic_maps/_topic_map_osd.yml b/_topic_maps/_topic_map_osd.yml
index 400805ca5453..c0397523af3b 100644
--- a/_topic_maps/_topic_map_osd.yml
+++ b/_topic_maps/_topic_map_osd.yml
@@ -869,6 +869,8 @@ Topics:
     File: about-ovn-kubernetes
   - Name: Migrating from the OpenShift SDN network plugin
     File: migrate-from-openshift-sdn-osd
+  # - Name: Migrating from the OpenShift SDN network plugin
+    # File: migrate-from-openshift-sdn
 - Name: OpenShift SDN network plugin
   Dir: ovn_kubernetes_network_provider
   Topics:
diff --git a/_topic_maps/_topic_map_rosa.yml b/_topic_maps/_topic_map_rosa.yml
index b655671f470f..6a33e8967225 100644
--- a/_topic_maps/_topic_map_rosa.yml
+++ b/_topic_maps/_topic_map_rosa.yml
@@ -1131,6 +1131,8 @@ Topics:
     File: about-ovn-kubernetes
   - Name: Configuring an egress IP address
     File: configuring-egress-ips-ovn
+  - Name: Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin
+    File: migrate-from-openshift-sdn
 - Name: OpenShift SDN network plugin
   Dir: ovn_kubernetes_network_provider
   Topics:
diff --git a/modules/migrate-sdn-ovn.adoc b/modules/migrate-sdn-ovn.adoc
new file mode 100644
index 000000000000..904bfd953b31
--- /dev/null
+++ b/modules/migrate-sdn-ovn.adoc
@@ -0,0 +1,37 @@
+// Module included in the following assemblies:
+//networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="migrate-sdn-ovn-cli_{context}"]
+= Initiate migration using the ROSA CLI
+
+[WARNING]
+====
+You can only initiate migration on clusters that are version 4.16.24 and above.
+====
+
+To initiate the migration, run the following command:
+[source,terminal]
+----
+$ rosa edit cluster -c <cluster_id> <1>
+  --network-type OVNKubernetes
+  --ovn-internal-subnets <configuration> <2>
+----
+<1> Replace `<cluster_id>` with the ID of the cluster you want to migrate to the OVN-Kubernetes network plugin.
+<2> Optional: Users can create key-value pairs to configure internal subnets using any or all of the options `join, masquerade, transit` along with a single CIDR per option. For example, `--ovn-internal-subnets="join=0.0.0.0/24,transit=0.0.0.0/24,masquerade=0.0.0.0/24"`.
+
+[IMPORTANT]
+====
+You cannot include the optional flag `--ovn-internal-subnets` in the command unless you define a value for the flag `--network-type`.
+====
+
+:_mod-docs-content-type: PROCEDURE
+[id="verify-sdn-ovn_{context}"]
+= Verify migration status using the ROSA CLI
+
+To check the status of the migration, run the following command:
+[source,terminal]
+----
+$ rosa describe cluster -c <cluster_id> <1>
+----
+<1> Replace `<cluster_id>` with the ID of the cluster to check the migration status.
\ No newline at end of file
diff --git a/networking/about-managed-networking.adoc b/networking/about-managed-networking.adoc
index ce16248dfd05..059075201f05 100644
--- a/networking/about-managed-networking.adoc
+++ b/networking/about-managed-networking.adoc
@@ -16,19 +16,21 @@ The following are some of the most commonly used {openshift-networking} features
 +
 ** xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[OVN-Kubernetes network plugin], which is the default CNI plugin.
 ** {OCP-short} SDN network plugin, which was deprecated in {OCP-short} 4.16 and removed in {OCP-short} 4.17.
-+
+
+ifdef::openshift-rosa[]
+
 [IMPORTANT]
 ====
-Before upgrading {product-title} clusters that are configured with the OpenShift SDN network plugin to version 4.17, you must migrate to the OVN-Kubernetes network plugin. For more information, see _Migrating from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin_ in the _Additional resources_ section.
+Before upgrading {rosa-classic} clusters that are configured with the OpenShift SDN network plugin to version 4.17, you must migrate to the OVN-Kubernetes network plugin. For more information, see _Migrating from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin_ in the  _Additional resources_ section.
 ====
 
+endif::openshift-rosa[]
 [discrete]
 [role="_additional-resources"]
 [id="additional-resources_{context}"]
 == Additional resources
 
 * link:https://access.redhat.com/articles/7065170[{OCP-short} SDN CNI removal in OCP 4.17]
-
-ifdef::openshift-dedicated[]
-* xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn-osd.adoc#migrate-from-openshift-sdn-osd[Migrating from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin]
-endif::openshift-dedicated[]
\ No newline at end of file
+ifdef::openshift-rosa[]
+* xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin]
+endif::openshift-rosa[]
diff --git a/networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc b/networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc
new file mode 100644
index 000000000000..7a319d49d9e5
--- /dev/null
+++ b/networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc
@@ -0,0 +1,30 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="migrate-from-openshift-sdn"]
+= Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin
+include::_attributes/common-attributes.adoc[]
+include::_attributes/attributes-openshift-dedicated.adoc[]
+:context: migrate-from-openshift-sdn
+
+toc::[]
+
+As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin and verify the migration status using the ROSA CLI.
+
+Some considerations before starting migration initiation are:
+
+* The cluster version must be 4.16.24 and above.
+
+* The migration process cannot be interrupted.
+
+* Migrating back to the SDN network plugin is not possible.
+
+* Cluster nodes will be rebooted during migration.
+
+* There will be no impact to workloads that are resilient to node disruptions.
+
+* Migration time can vary between several minutes and hours, depending on the cluster size and workload configurations.
+
+include::modules/migrate-sdn-ovn.adoc[leveloffset=+1]
+
+
+
+
diff --git a/rosa_release_notes/rosa-release-notes.adoc b/rosa_release_notes/rosa-release-notes.adoc
index 586853dda86a..2cc4ae7ff309 100644
--- a/rosa_release_notes/rosa-release-notes.adoc
+++ b/rosa_release_notes/rosa-release-notes.adoc
@@ -24,6 +24,11 @@ endif::openshift-rosa-hcp[]
 ifdef::openshift-rosa[]
 * **{rosa-classic} cluster node limit update.** {rosa-classic} clusters versions 4.14.14 and greater can now scale to 249 worker nodes. This is an increase from the previous limit of 180 nodes. For more information, see xref:../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[Limits and scalability].
 +
+// * **{product-title} SDN network plugin blocks future major upgrades**
+* **Initiate live migration from OpenShift SDN to OVN-Kubernetes.**
+As part of the {product-title} move to OVN-Kubernetes as the only supported network plugin starting with {product-title} 4.17, users can now initiate live migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin.
+If your cluster uses the OpenShift SDN network plugin, you cannot upgrade to future major versions of {product-title}  without migrating to OVN-Kubernetes. For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
+
 [IMPORTANT]
 ====
 Egress lockdown is a Technology Preview feature.