descirbe semi-automated procedure

Author: akarasavov

modules/ROOT/pages/clustering/setup/discovery.adoc

@@ -558,6 +558,27 @@ As such, ensure that `dbms.cluster.discovery.version=V2_ONLY`, and that `dbms.cl
 are set as required, so that the servers start with v2 running on the next restart.
 ====
 
+[[discovery-v1-to-v2-semi-automated-procedure]]
+=== Semi-automated procedure
+
+Another way to migrate from Discovery Service `V1` to `V2` is to use a semi-automated procedure, which simplifies the migration process
+It automates the approach described in the xref:clustering/setup/discovery.adoc#_using_procedures[previous section].
+
+. Make sure that server side routing is enabled as detailed in xref:https://neo4j.com/docs/operations-manual/current/clustering/setup/routing/#clustering-routing[Server-side routing] section
+. For all the servers, ensure that new settings are updated to the configuration as detailed the xref:clustering/setup/discovery.adoc#_preparation[Preparation] section.
+. Connect to any server using server-side routing
++
+[source,cypher]
+----
+./cypher-shell -a neo4j://localhost:7691 -d system
+----
+. Run the following procedure three times to move all members from `V1_ONLY` to `V2_ONLY`. If the procedure fails, read the error message and resolve the issue manually.
+One possible reason for failure is that some members might have had inconsistent `dbms.cluster.discovery.version` settings initially.
+Refer to the previous section for guidance on debugging and fixing issues.
+[source,cypher]
+----
+CALL internal.dbms.cluster.moveToNextDiscoveryVersion();
+----
 
 
 == Monitoring the progress and metrics