: Hope the below helps.
Step1: Prior to migration, i.e. from a local machine personal gateway to server based enterprise gatewway, ensure you do the last refresh for the dataset and archive for backup / recovery purposes AND copy the files and validate the authentication of the new gateway (using Azure preferably on a domain machine and the same access rights as per the first gateway's credentials.
Step 2: You need to add the new gateway for the new source from the admin console for the same dataset. once configured ( we are not yet at the sync stage ....), you will come across something like the below.
Selecting gateway for the same named dataset #PowerBI #Gateway
Step 3 ( Optional ): You can stop the services for sometime of the first gateway to ensure the dataset doesnt sync or show online. Ensure no other reports on running on this gateway ( i.e. Gateway 1)
Step 4: Select the second gateway from the list. You should be able to see it if the authentication is successfull. ( depends whether you are using file/db/live content based source )
Step 5: Once the setup is replicated, now you need to re-run the authentication for the enterprise gateway locally and over the portal and check the connection works. Depending on your data size, monitor the refresh over the new gateway till it's not compelete.
The postings are solely my own and do not represent or constitute my partner organizations views, strategies, comments or opinions.