1. Preparation of the migration

Before you can start with the migration of your PRTG installation, you should prepare the following:

• 1.1 Check your PRTG version and your Windows version
• 1.2 Check your login credentials for the PRTG core server service and the PRTG probe service
• 1.3 Check your cluster setup

1.1 Check your PRTG version and your Windows version

To successfully move a PRTG installation, make sure that you install the same PRTG version on the source system and the target system.
You might need to update the source system to the latest PRTG version before you can proceed.

If you want to migrate PRTG from a 32-bit Windows to a different 32-bit Windows, or from a 64-bit Windows to a different 64-bit Windows, you can proceed without modifying the Windows registry.

If you want to migrate PRTG from a 32-bit Windows to a 64-bit Windows, or the other way around, you must follow these steps.

• Manually modify the following registry key.
  
  Remove the Paessler branch from the Wow6432Node node or move the Paessler branch to the Wow6432Node node.
• Manually transfer the settings of the PRTG Administration Tool from the source system to the target system. See step 7a in article section 2. Step-by-step migration in this case.

1.2 Check your login credentials for the PRTG core server service and the PRTG probe service

On the new system, make sure that you use the same account for the PRTG core server service and the PRTG probe service as on the previous system. If you used custom credentials, you must take the following steps.

1. Go to Services in the Windows Administrative Tools.
2. Open the Properties of the PRTG Core Server Service and/or the PRTG Probe Service.
3. Click the Log On tab and select Local System account or This account to add the account that you want to use.

Note: By default, the PRTG core server service and the PRTG probe service run under the Local System account. This can cause problems with some script sensors because, in some cases, the Local System account does not have access to the network or other computers. We recommend that you use an account with the required permissions.

1.3 Check your cluster setup

If you run PRTG in a cluster, the instructions for migration apply to a PRTG core server system that is the primary master node.

If you plan to move a failover node to a different system, you can follow the migration steps as well. However, if you can afford to lose your failover node's data, we recommend that you install a completely new failover node and join it to the cluster. The new failover node then automatically receives the monitoring configuration from the primary master node.

Take the following steps beforehand:

1. Log in to the PRTG web interface of the primary master node and navigate to Setup | System Administration | Cluster.
2. Delete the entry of the failover node that you want to remove from the cluster.
3. Save your settings.

More

• 2. Step-by-step migration
• 3. After the migration
• 4. Migration of custom files

2. Step-by-step migration

Here you can find a detailed, in-depth migration guide about how to move a PRTG installation from a source system to a new target system.

See the following steps:

• Step 1a: Deactivate your license on the source system
• Step 1b: Install PRTG on the target system
• Step 2: Stop the PRTG core server service and the PRTG probe service on both source and target system
• Step 3: Find the local PRTG data directory
• Step 4: Copy the data files to the PRTG data directory of the target system
• Step 5: Copy your custom files to the PRTG program directory of the target system
• Step 6: Export the settings of the source system and the local probe from the Windows registry to a file
• Step 7: Import the settings of the source system and the local probe to the Windows registry of the target system
• Step 7a: Migrating PRTG from a 32-bit Windows to a 64-bit Windows
• Step 8: Optional: Check the settings of the PRTG core server
• Step 9: Check the path to the PRTG data directory
• Step 10: Optional: Adjust the settings of remote probe installations
• Step 11: Start the PRTG core server service and the PRTG probe service on the target system
• Step 12: Review your monitoring setup and results
• Step 13: Optional: Update to the latest version of PRTG

Step 1a: Deactivate your license on the source system

Before you start to migrate a PRTG installation to a different system, deactivate the PRTG license on the source system. This ensures that you can seamlessly activate your license on the target system.

PRTG still runs as a licensed edition on the source system for a 30-day grace period so that you have enough time to complete the migration. For more information, see PRTG Manual: PRTG Status.

1. Log in to the PRTG web interface on the source system.
2. Select Setup | License Information from the main menu.
3. Click Deactivate this License and confirm the deactivation of the license on this PRTG core server.

If you want to undo the license deactivation, contact our customer service. You cannot manually reactivate your license. Also contact us if you cannot deactivate the license on your source system because it is not reachable anymore. In this case, we must manually deactivate the license for you.

Step 1b: Install PRTG on the target system

During the installation of PRTG on the target system, you must enter the license name and the license key. For more information, see PRTG Manual: Install a PRTG Core Server.

You can always check the license status of your PRTG installation under Setup | License Information in the PRTG web interface.

Step 2: Stop the PRTG core server service and the PRTG probe service on both source and target system

1. Open the PRTG Administration Tool on both the source system and the target system.
2. Select the Service Start/Stop tab.
3. In sections PRTG Core Server Service and PRTG Probe Service, click Stop Service.

Step 3: Find the local PRTG data directory

To find the PRTG data directory, take the following steps:

1. Open the PRTG Administration Tool on both the source system and the target system.
2. Select the PRTG Core Server tab.
3. See section Local Storage of Data Files and Monitoring Database to find where the PRTG data files are stored.

Step 4: Copy the data files to the PRTG data directory of the target system

Overwrite the data files in the PRTG data directory on the target system.

Note: Consider copying the \Monitoring Database folder before you start the entire migration process because depending on the number of sensors, this folder can be quite large and so the copy process can take some time. Make sure to also copy the PRTG Configuration.dat file to the new server.

The following folders are not necessarily required for the migration:

• \Configuration Auto-Backups
• \Logs
• \Logs\debug
• \Logs\webserver
• \Report PDFs

Step 5: Copy custom files to the PRTG program directory of the target system

If you use custom files, you must also copy these files to the PRTG program directory of the target system. For more information on where you can find the folders that you must move, see 4. Migration of custom files.

Step 6: Export the settings of the source system and the local probe from the Windows registry to a file

Note: If you migrate PRTG from a 32-bit Windows to a 64-bit Windows, the following instructions do not work. See step 7a in this case.

1. On the source system, open the Windows registry editor and navigate to the PRTG registry key. The exact location varies, depending on the Windows operating system.
   • 32-bit Windows:
     HKEY_LOCAL_MACHINE\SOFTWARE\Paessler\PRTG Network Monitor
   • 64-bit Windows:
     HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Paessler\PRTG Network Monitor
2. Right-click PRTG Network Monitor and Export the selected branch to a .reg file.
3. Save the file to a USB stick or a network share.

Note: The target system uses the same IP address as the source system. Make sure that the target system actually owns the old IP addresses, and shut down the source system. If you need to change the IP address during migration so that the target system has a different IP address, see 3. After the migration.

Step 7: Import the settings of the source system and the local probe to the Windows registry of the target system

Note: If you migrate PRTG from a 32-bit to a 64-bit Windows, the following instructions do not work. See step 7a in this case.

• Make sure that the Windows version installed on the target system matches the Windows version on the source system. This means that if the source system ran a 32-bit Windows, the target system must also run a 32-bit Windows.
  Note: If you want to import settings from a 32-bit Windows to a 64-bit Windows or the other way around, you must manually change the branch of the registry settings. We do not officially support this approach, however.
• Import the PRTG settings to the Windows registry of the target system, for example, by double-clicking the .reg file you exported on the source system.
  Note: If you do not import the PRTG settings to the registry, settings like user name and password, for example, revert to the default values. This means that user name and password are prtgadmin again.

Step 7a: Migrating PRTG from a 32-bit Windows to a 64-bit Windows

If you move your PRTG installation from a 32-bit Windows to a 64-bit Windows, the registry export and import as described in step 6 and step 7 do not work. You must manually copy the PRTG settings:

1. Open the PRTG Administration Tool on both the source system and the target system.
2. Manually transfer the PRTG settings from the source system to the target system. Make sure that you copy all settings.
3. Go on with step 8.

Step 8: Optional: Check the settings of the PRTG core server

The following steps are only necessary if you use remote probes.

1. Open the PRTG Administration Tool on the target system.
2. Select the PRTG Core Server tab.
3. Make sure that the settings in section Probe Connection Management are correct. If you use remote probes, this setting must either be Accept connections from remote probes on all IP addresses or Accept connections from remote probes on selected IP addresses only.

Note: This step is necessary because the import of registry settings does not always work flawlessly, depending on the used Windows version.

Step 9: Check the path to the PRTG data directory

1. Open the PRTG Administration Tool on the target system.
2. Select the PRTG Core Server tab.
3. Make sure that the path to the PRTG data directory specified in section Local Storage of Data Files and Monitoring Database matches the path to which you copied your data files in step 4.
4. Adapt the path, if necessary.

Step 10: Optional: Adjust the settings of remote probe installations

This step is only necessary if you use remote probes and if the IP address of the PRTG core server changes during the migration.

• Connect to each remote probe system and open the PRTG Administration Tool. Enter the new IP address of the target system.
• You might also need to change some settings under Setup | System Administration | Core & Probes in the PRTG web interface so that your new PRTG installation accepts incoming remote probe connections (on all IP addresses, if applicable). For more information, see PRTG Manual: Core & Probes.

Step 11: Start the PRTG core server service and the PRTG probe service on the target system

1. Open the PRTG Administration Tool on the target system.
2. Select the Service Start/Stop tab.
3. In sections PRTG Core Server Service and PRTG Probe Service, click Start Service.

Step 12: Review the monitoring setup and results

Log in to the PRTG web interface of the new PRTG installation and check if the migration was successful.

Step 13: Optional: Update to the latest version of PRTG

We recommend that you always keep your systems up to date.

More

• 1. Preparation of the migration
• 3. After the migration
• 4. Migration of custom files

3. After the migration

After the migration, you might need to check and troubleshoot the following aspects, depending on your configuration:

• 3.1 You get the error message License too old
• 3.2 The IP address of the PRTG web server changed
• 3.3 The hostname of the target system changed

3.1 You get the error message License too old

If you get the error message that your license is too old, contact the Paessler support team for a new activation attempt and tell us the reason why you want to migrate PRTG. This way, we can immediately see if your activation request is valid and help you accordingly.

3.2 The IP address of the PRTG web server changed

• The target system automatically switched the address of the PRTG web server to localhost. To make the PRTG web interface available again under the IP address of the PRTG core server system, open the PRTG Administration Tool, select the PRTG Web Server tab, and change the settings in section IP Address for PRTG Web Server accordingly.
• If the IP address of the target system changed, you might need to adapt firewall settings and/or NAT settings that apply to the old IP address.
• If you use an SMTP relay server for email delivery out of PRTG, you might need to allow relaying for the new IP address.
• If you run PRTG in a cluster and the IP address of the target system changed, open the PRTG web interface of the primary master node and navigate to Setup | System Administration | Cluster.
  • If you moved a primary master node: Change the IP address entry of the primary master node so that failover nodes can reconnect to the new primary master node.
  • If you moved a failover node: Change the IP address entry of the failover node so that the primary master node can reconnect to the new failover node.

3.3 The hostname of the target system changed

• In the PRTG web interface, navigate to Setup | System Administration | User Interface and check the DNS Name option. Make sure that the DNS name points to the correct PRTG core server. This DNS name is included in links and in emails sent by PRTG. If it still points to the source system, links in emails might not work.
• Confirm that your clients and remote probes point to the correct hostname or IP address.
• If it is relevant for your network, click the Notification Delivery tab and check the HELO Ident option. Make sure that your email server accepts the entered value.

More

• 1. Preparation of the migration
• 2. Step-by-step migration
• 4. Migration of custom files

4. Migration of custom files

The following folders in the PRTG program directory may contain your custom files that you must also move to the target system. The paths apply to a PRTG installation on a 64-bit Windows:

• Custom sensor files:
  %programfiles(x86)%\PRTG Network Monitor\Custom Sensors
• SSL certificate for the PRTG web server:
  %programfiles(x86)%\PRTG Network Monitor\cert
• Device templates:
  %programfiles(x86)%\PRTG Network Monitor\devicetemplates
• .oidlib files:
  %programfiles(x86)%\PRTG Network Monitor\snmplibs
• MIB files:
  %programfiles(x86)%\PRTG Network Monitor\MIB
• Custom notifications:
  %programfiles(x86)%\PRTG Network Monitor\Notifications
• Custom map objects:
  %programfiles(x86)%\PRTG Network Monitor\webroot\mapobjects
• Custom map background images:
  %programfiles(x86)%\PRTG Network Monitor\webroot\mapbackground
• Custom lookup files:
  %programfiles(x86)%\PRTG Network Monitor\lookups\custom
• Custom device icons:
  %programfiles(x86)%\PRTG Network Monitor\webroot\icons\devices

More

• 1. Preparation of the migration
• 2. Step-by-step migration
• 3. After the migration

We use custom flow rules so also do not forget to copy them at step 4. Procedure: https://kb.paessler.com/en/topic/60203-how-can-i-change-the-default-groups-and-channels-for-flow-and-packet-sniffer-sensors