diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml
index 06c0b6683e..0c5489f36b 100644
--- a/deploy-manage/toc.yml
+++ b/deploy-manage/toc.yml
@@ -784,11 +784,9 @@ toc:
                   - file: upgrade/deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md
               - file: upgrade/deployment-or-cluster/kibana.md
                 children:
+                  - file: upgrade/deployment-or-cluster/saved-object-migrations.md
                   - file: upgrade/deployment-or-cluster/kibana-roll-back.md    
-      - file: upgrade/ingest-components.md
-      - file: upgrade/internal-upgrade-processes.md
-        children:
-          - file: upgrade/internal-upgrade-processes/saved-object-migrations.md
+      - file: upgrade/ingest-components.md        
   - file: uninstall.md
     children:
       - file: uninstall/uninstall-elastic-cloud-enterprise.md
diff --git a/deploy-manage/upgrade/deployment-or-cluster/kibana.md b/deploy-manage/upgrade/deployment-or-cluster/kibana.md
index 5093132f9b..97d581f6a2 100644
--- a/deploy-manage/upgrade/deployment-or-cluster/kibana.md
+++ b/deploy-manage/upgrade/deployment-or-cluster/kibana.md
@@ -11,7 +11,7 @@ When you upgrade {{kib}}, you also upgrade the {{observability}} and {{elastic-s
 ::::{warning}
 {{kib}} automatically runs saved object migrations when required. To roll back to an earlier version in case of an upgrade failure, you **must** have a [backup snapshot](../../tools/snapshot-and-restore.md) that includes the `kibana` feature state. Snapshots include this feature state by default.
 
-For more information, refer to [Migrate saved objects](../internal-upgrade-processes/saved-object-migrations.md).
+For more information, refer to [Migrate saved objects](saved-object-migrations.md).
 
 ::::
 
diff --git a/deploy-manage/upgrade/internal-upgrade-processes/saved-object-migrations.md b/deploy-manage/upgrade/deployment-or-cluster/saved-object-migrations.md
similarity index 100%
rename from deploy-manage/upgrade/internal-upgrade-processes/saved-object-migrations.md
rename to deploy-manage/upgrade/deployment-or-cluster/saved-object-migrations.md
diff --git a/deploy-manage/upgrade/internal-upgrade-processes.md b/deploy-manage/upgrade/internal-upgrade-processes.md
deleted file mode 100644
index a8ce64547d..0000000000
--- a/deploy-manage/upgrade/internal-upgrade-processes.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Internal upgrade processes
-
-% What needs to be done: Write from scratch
-
-⚠️ **This page is a work in progress.** ⚠️
\ No newline at end of file
diff --git a/explore-analyze/find-and-organize/saved-objects.md b/explore-analyze/find-and-organize/saved-objects.md
index 475462edd2..afdd3b100c 100644
--- a/explore-analyze/find-and-organize/saved-objects.md
+++ b/explore-analyze/find-and-organize/saved-objects.md
@@ -127,7 +127,7 @@ We have made several enhancements to minimize the impact, and this document desc
 
 ### Impact upon upgrading to version 8.x or later [saved-object-ids-impact-upon-upgrading]
 
-Every time you upgrade {{kib}}, [saved objects are migrated to a new format](/deploy-manage/upgrade/internal-upgrade-processes/saved-object-migrations.md). When you first upgrade to version 8.x or later, this migration process will start enforcing globally unique saved object IDs.
+Every time you upgrade {{kib}}, [saved objects are migrated to a new format](/deploy-manage/upgrade/deployment-or-cluster/saved-object-migrations.md). When you first upgrade to version 8.x or later, this migration process will start enforcing globally unique saved object IDs.
 
 In practical terms, **any old saved objects that exist in a custom space will have their IDs changed to a new UUID**, while saved objects in the Default space will be unchanged. This is how we can ensure that every saved object ID is unique. For example: if you had dashboard "123" in the Default space and dashboard "123" in Another space, after the upgrade you would have dashboard "123" in the Default space and dashboard "456" in Another space.