This article applies as of PRTG 22
Migrate PRTG to PRTG Hosted Monitor
It is possible to migrate an on-premises PRTG installation to a PRTG Hosted Monitor instance. However, not every on-premises PRTG installation qualifies for the migration to PRTG Hosted Monitor.
Before the migration, please see the following resources:
- It is currently not possible to migrate historic data or custom objects such as notifications, reports, maps, lookup files, etc.
- We cannot migrate .oidlib files, device templates, lookups, and device icons for you. You can upload these yourself after the migration.
- The maximum number of sensors that a PRTG Hosted Monitor instance supports is 10,000. This means that it is not possible to migrate more than 10,000 sensors to a PRTG Hosted Monitor instance.
After the migration
The following aspects are not migrated and require your manual effort after the migration.
Existing user accounts from your on-premises PRTG installation will not be available in the PRTG Hosted Monitor instance.
You will also notice that you do not have the same login dialog for the PRTG Hosted Monitor instance as you do for the on-premises installation. This is because we have a third-party provider (Auth0) that manages logins for all our PRTG Hosted Monitor instances.
This means that it is necessary to create all user accounts anew in PRTG Hosted Monitor.
Note: The Active Directory integration and Azure Active Directory logins are not available in PRTG Hosted Monitor.
Credentials for sensors
Credentials for sensors are encrypted within the configuration file. The so-called salt that PRTG uses to encrypt and decrypt the data is generated based on the system that runs the on-premises PRTG installation.
So, when migrating the configuration file to a new system, these credentials cannot be decrypted properly.
This means that sensors that rely on credentials will stop working. You must set the credentials anew in PRTG Hosted Monitor.
Sensors on the local probe
What is known as the local probe in your on-premises PRTG installation is called hosted probe in PRTG Hosted Monitor. Keep in mind that the hosted probe can only monitor devices that are publicly reachable. The hosted PRTG instance does not have a VPN or any similar connection to your network infrastructure.
This means that you will be required to install remote probes inside your network in order to monitor your devices on site.
For more information on how to install a remote probe, see the PRTG Manual: Install a Remote Probe.
If you own an on-premises PRTG Network Monitor installation and if you're interested in migrating it to PRTG Hosted Monitor, please contact us via email to [email protected] mentioning this article so we can guide you at best and clarify commercial questions in first place.