diff --git a/CHANGELOG.md b/CHANGELOG.md
index db506ec6d6f..8acc3daa2ea 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,7 +1,10 @@
+- Updated product migration in Client Configuration Guide: added SUSE
+  Linux Enterprise Server to SUSE Linux Enterprise Server for SAP
+  Applications and extensions enabled automatically
+- Documented how to replace existing certificates via mgrctl (bsc#1233793)
 - Updated Troubleshooting Autoinstallation in Administration Guide
 - Added external link for creating virtual network peer for Azure in
   Specialized Gudes (bsc#1234441)
-- Documented how to replace existing certificates via mgrtcl (bsc#1233793)
 - Clarified SSH authentication methods during Web UI bootstrap process in
   Client Configuration Guide (bsc#1233497)
 - Changes proxy helm installation to use package from OS channel in
diff --git a/modules/client-configuration/pages/client-upgrades-product-migration.adoc b/modules/client-configuration/pages/client-upgrades-product-migration.adoc
index 42afa8f4868..b337520e2a8 100644
--- a/modules/client-configuration/pages/client-upgrades-product-migration.adoc
+++ b/modules/client-configuration/pages/client-upgrades-product-migration.adoc
@@ -1,7 +1,8 @@
 [[client-upgrades-spmigration]]
 = Product Migration
 
-== Introcustion
+== Introduction
+
 Product migration allows you to upgrade SLE-based client systems from an Service Pack (SP) level to a later one.
 For example, you can migrate {sles}{nbsp}15{nbsp}SP1 to {sles}{nbsp}15{nbsp}SP2.
 You can also upgrade clients such as {almalinux}, {centos}, {oracle}, or {rocky} to {sll}.
@@ -16,6 +17,9 @@ You can also migrate openSUSE Leap to a later minor version or to the correspond
 * openSUSE Leap 15.1 to {sles} 15 SP1
 * openSUSE Leap 15.5 to {sles} 15 SP5
 
+You can also migrate {sles} to the corresponding {slesforsap} SP level, for example:
+
+* {sles} 15 SP5 to {slesforsap} 15 SP5
 
 In {sles}{nbsp}12 and later, {suse} supports service pack skipping if {scclongform} provides it.
 For example, you can upgrade from {sles}{nbsp}15 to SP2, without installing SP1.
@@ -23,6 +27,13 @@ For example, you can upgrade from {sles}{nbsp}15 to SP2, without installing SP1.
 For supported {sles} upgrade paths, see link:https://documentation.suse.com/en-us/sles/15-SP4/html/SLES-all/cha-upgrade-paths.html#sec-upgrade-paths-supported[].
 
 
+[NOTE]
+====
+All recommended extensions are automatically enabled when you migrate.
+====
+
+
+
 [NOTE]
 ====
 During migration, {productname} automatically accepts any required licenses (EULAs) before installation.
@@ -184,7 +195,7 @@ In this case, the system is being upgraded to SLES 15 SP3, and the label is [lit
 To see a list of all base channels currently mirrored, run:
 +
 ----
-spacecmd softwarechannel_listbasechannels.
+spacecmd softwarechannel_listbasechannels
 ----
 +
 Keep in mind you cannot upgrade to a channel unless it is an available target for your current base channel.
diff --git a/parameters.yml b/parameters.yml
index 3f3a653aa75..12e50ad4d81 100644
--- a/parameters.yml
+++ b/parameters.yml
@@ -218,6 +218,8 @@ asciidoc:
       value: "SUSE Manager Proxy"
     - attribute: sles
       value: "SUSE Linux Enterprise Server"
+    - attribute: slesforsap
+      value: "SUSE Linux Enterprise Server for SAP Applications"
     - attribute: sled
       value: "SUSE Linux Enterprise Desktop"
     - attribute: sle
@@ -240,6 +242,8 @@ asciidoc:
       value: MicroOS
     - attribute: slsa
       value: SLES
+    - attribute: sls4sapa
+      value: "SLES for SAP"
     - attribute: suse
       value: SUSE
     - attribute: slea