diff --git a/docs/single-to-multi-master.md b/docs/single-to-multi-master.md
index c44db1c7a5..f5ab28ad37 100644
--- a/docs/single-to-multi-master.md
+++ b/docs/single-to-multi-master.md
@@ -1,9 +1,29 @@
 # Migrating from single to multi-master
 
 This document describes how to go from a single-master cluster (created by kops)
-to a multi-master cluster.
+to a multi-master cluster. If you are using etcd-manager you just need to perform some steps of the migration.  
 
-## Warnings
+# etcd-manager 
+
+If you are using etcd-manager, just perform the steps in this section. Etcd-manager is default for kops 1.12. Etcd-manager makes the upgrade to multi-master much smoother. 
+
+The list references steps of the next section. To upgrade from a single master to a cluster with three masters:
+
+- Skip Step 1 since Etcd-manager is doing automatic backups to S3
+- Create Instance Groups (Section 2 below)
+  - create the subnets
+  - create the instance groups (no need to disable the third master, leave minSize and maxSize at 1)
+  - add the masters to your etcd cluster definition (both in section named main and events)
+- Skip Step 3 and 4
+- Now you are ready to update the AWS configuration:
+  - `kops update cluster your-cluster-name` 
+- AWS will launch two new masters, they will be discovered and then configured by etcd-manager
+- check with `kubectl get nodes` to see everything is ready
+- Cleanup (Step 5) to do a rolling restart of all masters (just in case)
+
+# Etcd without etcd-manager 
+
+## 0 - Warnings
 
 This is a risky procedure that **can lead to data-loss** in the etcd cluster.
 Please follow all the backup steps before attempting it. Please read the
@@ -60,10 +80,45 @@ $ scp -r admin@<master-node>:backup-events/ .
 
 ## 2 - Create instance groups
 
-### a - Create new master instance group
+### a - Create new subnets
+
+Add new subnets for your availability zones. Also create subnets of type Utility if they are defined in your configuration. 
+```bash
+kops edit cluster
+```
+
+Change the subnet section. An example might be: (**Adapt to your configuration!**)
+```yaml
+  - cidr: 172.20.32.0/19
+    name: eu-west-1a
+    type: Private
+    zone: eu-west-1a
+  - cidr: 172.20.64.0/19
+    name: eu-west-1b
+    type: Private
+    zone: eu-west-1b
+  - cidr: 172.20.96.0/19
+    name: eu-west-1c
+    type: Private
+    zone: eu-west-1c
+  - cidr: 172.20.0.0/22
+    name: utility-eu-west-1a
+    type: Utility
+    zone: eu-west-1a
+  - cidr: 172.20.4.0/22
+    name: utility-eu-west-1b
+    type: Utility
+    zone: eu-west-1b
+  - cidr: 172.20.8.0/22
+    name: utility-eu-west-1c
+    type: Utility
+    zone: eu-west-1c
+```
+
+### b - Create new master instance group
 
 Create 1 kops instance group for the first one of your new masters, in
-a different AZ from the existing one.
+a different AZ from the existing one. 
 
 ```bash
 $ kops create instancegroup master-<availability-zone2> --subnet <availability-zone2> --role Master
@@ -76,8 +131,10 @@ $ kops create ig master-eu-west-1b --subnet eu-west-1b --role Master
 
  * ``maxSize`` and ``minSize`` should be 1,
  * only one zone should be listed.
+ * adjust the machineType
+ * adjust the image to the OS you are using
 
-### b - Create third master instance group
+### c - Create third master instance group
 
 Instance group for the third master, in a different AZ from the existing one, is
 also required. However, real EC2 instance is not required until the second master launches.
@@ -93,9 +150,12 @@ $ kops create ig master-eu-west-1c --subnet eu-west-1c --role Master
 ```
 
  * ``maxSize`` and ``minSize`` should be **0**,
+ * if you are using etcd-manager, you just can leave the `maxSize` and `minSize` at **1**.
  * only one zone should be listed.
+ * adjust the machineType
+ * adjust the image to the OS you are using
 
-### c - Reference the new masters in your cluster configuration
+### d - Reference the new masters in your cluster configuration
 
 *kops will refuse to have only 2 members in the etcd clusters, so we have to
 reference a third one, even if we have not created it yet.*
@@ -136,7 +196,6 @@ etcdClusters:
     name: events
 ```
 
-
 ## 3 - Add a new master
 
 ### a - Add a new member to the etcd clusters
@@ -325,4 +384,4 @@ Test if your master is reboot-proof:
 
 Go to EC2 and ``Terminate`` the instance and check if your cluster recovers (needed to discard any manual configurations and check that kops handles everything the right way).
 
-Note! Would recommend also to use Amazon Lambda to take daily Snapshots of all your persistent volume so you can have from what to recover in case of failures.
+Note! Would recommend also to use Amazon Lambda to take daily Snapshots of all your persistent volume so you can have from what to recover in case of failures.
\ No newline at end of file