How to migrate PRTG to another server

Owned by
Eduardo Baldoma Paredes
, created
Last updated: Sept 07, 2023
3 min read

In the case scenario that you need to replace the server where PRTG is installed or you need to move it to another server, here are the instructions to migrate it.

 Instructions

Steps:

  1. On your original server, go to the PRTG web interface and deactivate your PRTG license under Setup | License Information. Otherwise, you cannot activate the license on the new server. Your old server will still run as a licensed version for 30 days.



     

  2. Open the PRTG Administration Tool and stop the PRTG core server service and the PRTG probe service on the old server.

     

  3. Go to the data directory of your old server and copy the contents of %programdata%\Paessler\PRTG Network Monitor to your new server. Make sure that the file paths match.

     

  4. After copying the necessary data, install the same version of PRTG that you run on the old server on the new server using the installer of the old server. By default, this installer is stored in the PRTG program directory: %programfiles(x86)%\PRTG Network Monitor\PRTG Installer Archive. Use the (Currently Installed Version) exe. During the installation you will need your license name and license key that you wrote down in Step 1.

     

  5. After PRTG is installed in the new server, if you use customizations like custom device icons, custom sensors, or certificates, go to the program directory of your old server and copy the respective content to the new server as well.

     

  6. The migration reverts the credentials for the PRTG System Administrator account to the default username and password, prtgadmin. In the PRTG Administration Tool, set the previous password from the old server or take advantage to set a new one.

     

  7. In the PRTG web interface, go to Setup | System Administration | User Interface, section PRTG Web Interface. Enter the DNS Name so that it points to the fully qualified domain name (FQDN) of the new server.

     

  8. Finally, check whether all your sensors behave as expected.