update the migration steps

Author: renetapopova

modules/ROOT/pages/kubernetes/operations/backup-restore.adoc

@@ -1080,31 +1080,11 @@ To restore the `system` database, follow the steps described in xref:kubernetes/
 
 To migrate from persistent volume-based backups to cloud-native backups, you need to follow these steps:
 
-. Perform final traditional backup.
-. Upload existing backups to cloud storage (if needed).
-. Update configuration to use cloud provider.
-. Remove persistent volume configuration.
-. Enable `preferDiffAsParent` for future differential backups.
+. Perform a final traditional backup to ensure you have the latest data.
+For more information, see <<kubernetes-neo4j-backup-on-prem, Prepare to back up a database(s) to on-premises storage>> and <<kubernetes-neo4j-backup, Back up your databases>>.
+. Upload existing backups to the cloud storage bucket if needed.
+. Update the _backup-values.yaml_ file to configure the cloud provider, bucket name, and credentials.
+See <<kubernetes-neo4j-backup-cloud, Prepare to back up a database(s) to a cloud provider (AWS, GCP, and Azure) bucket>> for details.
+. Install the _neo4j-admin_ Helm chart with the updated _backup-values.yaml_ file to back up your databases to the cloud provider bucket.
+See <<_back_up_your_databases, Back up your databases>> for details.
 
-.Example migration
-[source, yaml]
-----
-# Before (Traditional)
-backup:
-  database: "neo4j"
-  databaseAdminServiceName: "neo4j-admin"
-tempVolume:
-  persistentVolumeClaim:
-    claimName: "backup-pvc"
-
-# After (Cloud-Native)
-backup:
-  cloudProvider: "aws"
-  bucketName: "neo4j-backups"
-  database: "neo4j"
-  databaseAdminServiceName: "neo4j-admin"
-  secretName: "aws-credentials"
-  secretKeyName: "credentials"
-  preferDiffAsParent: true
-# tempVolume configuration removed
-----