Which fits your PRTG renewal: PRTG vs Zabbix
PRTG fits teams that want a packaged, quick-start tool with vendor-supported updates, while Zabbix fits teams with in-house or partner capacity that want no license fee, no device limits and scale they run themselves. Zabbix's open source software carries no license fee, no device limits and no feature gates, so the cost question shifts from licensing to the people, servers and database that operate it. The decision turns on four things: how many sensors or devices you will monitor in three years, whether you have staff who can own a Zabbix server, database and proxies, how your organization feels about the AGPL-3.0 license that applies from Zabbix 7.0 onward, and who will be on call when the platform needs changes.
Start with the sensor count, because it sets the price gap. A PRTG renewal is priced by sensor tier, so the tier you are moving to is the number to compare against Zabbix's hardware and staffing needs, not the license line alone. Ask your PRTG reseller or Paessler contact to confirm the current tier and any sensor overage terms in writing. On the Zabbix side, use the high availability and proxy documentation to size an architecture: Zabbix server nodes share one database, and proxy groups redistribute hosts when a proxy goes offline. Confirm your database choice against the Zabbix requirements page before you commit to a design, since the supported MySQL, MariaDB, PostgreSQL and TimescaleDB versions change by release.
Which scenarios favor PRTG and which favor Zabbix
This table maps common monitoring situations to the platform that usually fits better, with the condition that drives the choice. Read it as a starting point: the deciding factor is often staff skills and how much support the buyer needs, not feature lists alone.
| Scenario | Better fit | Condition that drives the choice |
|---|---|---|
| Small team, a few hundred sensors, no dedicated monitoring staff | PRTG | PRTG's guided setup, auto-discovery and single vendor support suit a team with no one to maintain a database and templates |
| Large SNMP and agent estate with sensor counts growing each year | Zabbix | Templates, low-level discovery and PostgreSQL or TimescaleDB storage keep growth under the team's control, and no per-sensor license is required |
| Multi-site network needing collection close to remote devices | Zabbix | Proxies and proxy groups collect locally and redistribute hosts when a proxy goes offline, provided someone maintains the proxy fleet |
| Team with Linux and database skills that wants full control of the stack | Zabbix | Configuration lives in templates, the database and version-controlled scripts, which suits engineers who already run Linux and SQL services |
| Windows-centric shop that wants a GUI for every sensor type | PRTG | Sensor creation through the PRTG web interface is faster for administrators who do not write templates or scripts |
| Regulated buyer that must have a contract with a named support vendor | Either, with a support decision | Zabbix sells paid technical support tiers, but the buyer must confirm response times and coverage in writing before choosing |
| Team that needs a vendor to own upgrades and fixes end to end | PRTG | Paessler supports its own product, while Zabbix self-hosted upgrades and fixes depend on internal staff or a contracted partner |
Where monitoring data lives and who controls the platform
Both platforms can run on premises or in a cloud account the customer controls, so the first decision is where the monitoring server, its database and the proxies that poll remote sites will physically sit. PRTG is also sold as PRTG Hosted Monitor, which moves that control to the vendor. Confirm with Paessler which deployment model your subscription covers, who holds administrative access to a hosted instance, and where its data is stored and backed up. For Zabbix, the hosting choice is yours alone, so write down the host, network zone and database location in your own environment before anyone asks.
Monitoring data is more sensitive than it looks. A Zabbix or PRTG instance holds hostnames, IP addresses and network topology, sensor credentials for SNMP communities, WMI accounts and database logins, and years of traffic and performance history that reveals when systems are busy or down. Inventory every credential the current PRTG device tree uses before migration, store them in a secrets manager rather than in host macros, and limit who can read them. In Zabbix, check how the web interface authenticates users (internal accounts, LDAP or SAML) and which user group permissions apply to host groups, so that a network team sees only its own devices. The Zabbix authentication documentation describes these settings.
If your organization is subject to a compliance assessment, the monitoring platform becomes evidence. DeployOpen can prepare the access control configuration, logging, backup and change records that an assessor will ask for, but it does not issue audit reports or certifications, and an independent auditor must assess the result. Ask your compliance team which control areas the monitoring system falls under, whether PRTG Hosted Monitor changes the shared responsibility split for those areas, and what evidence they need from a self-hosted Zabbix deployment. Settle these questions before cutover, since changing the hosting model later means repeating the assessment work.
What Zabbix licensing means after AGPL-3.0
Zabbix 7.0 and later are released under the GNU Affero General Public License version 3, which replaced GPL-2.0 used for all versions up to 6.4. For most organizations that install Zabbix on their own servers and monitor their own network, servers and applications, the change in license does not stop them from running it, and the open-source software itself carries no license fee and no device limits. The licensing question is therefore mostly about what you may change or distribute, not about whether you may use the product.
- Version boundary: Versions up to 6.4 remain under GPL-2.0, and 7.0 onward are under AGPL-3.0.
- No license fee: Zabbix states its open-source software has no license fee, no device limits and no feature gates.
- Internal monitoring: Running Zabbix for your own staff and infrastructure is the usual case covered by the license without extra obligations.
- Paid support is separate: Support subscriptions are an optional purchase, not a condition of using the software.
- Version choice: Confirm which version line you will deploy, since it determines which license text applies.
Confirm the exact license terms for your version on the Zabbix license page before you deploy.
AGPL-3.0 is a copyleft license whose distinguishing feature is its network clause: if you modify Zabbix and let users interact with the modified version over a network, you may have to offer them the corresponding source code of your changes. This matters most for teams that build custom modules, change the web interface, or provide Zabbix-based monitoring as a service to customers or affiliates. Simply configuring templates, items and dashboards is generally a different situation from changing the program code, so the scope of your changes drives the analysis.
- Network clause: Modifications offered to users over a network can trigger source disclosure duties under AGPL-3.0.
- Redistribution: Packaging and distributing modified binaries carries its own obligations under the license.
- Managed service offerings: Hosting Zabbix for third parties is the scenario where the network clause is most likely to apply.
- Custom integrations: Separate scripts, external tools or API clients that talk to Zabbix are generally assessed differently from changes to Zabbix itself.
- Documentation: Keep a record of which code you changed, since that record is what a reviewer will ask for.
Before you modify, redistribute or offer Zabbix to others, get a written legal review of your specific plan.
Zabbix sells technical support subscriptions in five tiers: Silver, Gold, Platinum, Enterprise and Global. Support is an operational service, bought to shorten response times and give access to vendor engineers, and it does not change the software license. The tiers differ mainly in coverage hours and response targets, which run from 8x5 support with a 1 day response for Silver, through 4 hour response for Gold, to 24x7 support with a 2 hour response for Platinum, 1.5 hour for Enterprise and 1 hour for Global.
- Silver: 8x5 coverage with a 1 day response target.
- Gold: Response target of 4 hours, per the support page.
- Platinum: 24x7 coverage with a 2 hour response target.
- Enterprise and Global: 24x7 coverage with 1.5 hour and 1 hour response targets respectively.
- Cost driver: Higher tiers cost more, and the tier you need depends on how many hours your operations team covers alone.
Ask Zabbix for a written quote showing the tier, term, included services and whether the price scales with your environment.
PRTG is licensed by sensor count in subscription tiers, so the cost of PRTG grows as you add monitored items, while Zabbix software has no license fee and its cost is mostly infrastructure, staff time and any support you choose to buy. A fair comparison puts PRTG's renewal quote next to the Zabbix support tier and hosting cost you would actually need, not the headline price of either product. The Zabbix side should also include who maintains the platform after go-live.
- PRTG side: Confirm the sensor tier, term and any add-ons on your own quote, since the sensor-based terms are specific to the purchase.
- Zabbix side: Count servers, database, storage, proxies and staff time as separate line items.
- Recurring versus one-time: Hardware and migration effort are often one-time, while support and staff time recur.
- Support is optional: Many teams run Zabbix without a paid tier and buy support only for critical systems.
- Ask for: The license terms, support tier and renewal conditions in writing from each vendor.
Lay both quotes side by side before the renewal date, and have your procurement or legal team confirm the terms.
What drives the cost of PRTG versus self-hosted Zabbix
The two sides of this comparison bill for different things. PRTG charges through sensor-based subscriptions, while Zabbix has no license fee and moves the cost into infrastructure, support and the people who run it. The cards below separate one-time from recurring items and name the inputs that move each total.
PRTG subscription by sensor tier
PRTG licensing is tied to the number of sensors you run, so the subscription grows as you add checks, devices or interfaces. Ask the vendor for the sensor count the quote assumes, the renewal terms, and the price of the tier that comes after yours, since moving up a tier is often the largest single jump. Confirm whether the quote includes support and upgrades for the full term.
Zabbix software has no license fee
Zabbix states its open source software has no license fee, no device limits and no feature gates, so the software line on a Zabbix quote is zero. The cost you still carry is the work to deploy, template and maintain it. Confirm with your legal or procurement team how the AGPL-3.0 terms apply if you modify Zabbix and offer it to users over a network.
Server and database infrastructure
Zabbix server, its web frontend and its database run on machines you provision, either on-premises or in your cloud account. Sizing depends on the number of monitored items, the polling interval and how much history you keep. Ask your platform team to size the database for your retention target and to confirm the supported database versions before buying hardware.
Proxies for distributed sites
Remote branches, data centers or segmented networks often need Zabbix proxies to collect data locally and forward it to the server. Each proxy is another system to host, patch and back up, and the number of sites drives this cost directly. Proxy groups can rebalance hosts when a proxy goes offline, which affects how much spare capacity you should plan for.
Support subscription, if chosen
Zabbix sells technical support subscriptions in tiers that differ by hours of coverage and response time, so the support line is optional and recurring. Compare the response times against your own on-call commitments before deciding. Ask the vendor for the tier, the term, the included upgrade assistance and whether the subscription covers your database and proxies.
Staff time for build, upgrades and backups
Most of the Zabbix cost is people. Building templates, tuning triggers, configuring notifications, testing backups and planning upgrades are recurring duties, and each Zabbix major release has its own support window. Plan named owners and the hours they can give, and ask any implementation partner for a fixed-scope written estimate covering build, migration and handover.
How a move from PRTG to Zabbix usually runs
The sequence turns a PRTG sensor inventory into a Zabbix design that is tested, run alongside PRTG, and cut over only after alerts match. The result is a monitoring setup you own and can verify before the subscription ends.
Inventory devices and sensors through the API
The team exports the device tree, sensor list, sensor types, thresholds and notification settings from PRTG through its HTTP API, and records which sensors are actually alerting. Someone from network or systems operations usually owns this, with the monitoring lead reviewing it. The step is done when every device has a source record and every sensor type is either mapped to a planned check or marked for retirement.
Design templates, proxies and the database
Group the inventory by device class and site, then decide which Zabbix templates cover each class, which devices need SNMP and which need agents, and where Zabbix proxies sit for remote networks. Zabbix 7.0 and later support proxy groups for load balancing and failover, which affects how many proxies you plan. Confirm the database choice against the supported versions for your Zabbix release. The step closes with a written design document that the platform and security teams have signed off.
Build a test instance on supported versions
Stand up a non-production Zabbix server, web frontend, database and one proxy in your own infrastructure, using a PostgreSQL, TimescaleDB or MySQL version listed for the release you chose. Check the server and frontend against the requirements page before installation, and set up authentication and user roles as your access policy requires. The step is done when the test instance accepts a sample host, collects data for it and sends a test notification.
Map sensors to templates and items
Using the inventory, build or import templates and assign them to host groups, then create items, triggers and discovery rules for the checks PRTG ran. Sensors with no direct equivalent, such as some vendor-specific or custom PRTG sensors, are either rebuilt with scripts or agent items or documented as gaps for a decision. The step is done when a sign-off list shows each PRTG sensor mapped to a Zabbix item, a trigger, or a recorded exception.
Rebuild maps, dashboards and notifications
Recreate network maps, dashboards and the alert routing that operations relies on, including escalation paths, maintenance windows and recipient groups. PRTG notification templates do not carry over automatically, so each one is rebuilt as a Zabbix action with its own conditions. Test each route with a controlled trigger and confirm that the right people receive it. The step is done when every notification route used in production has a tested Zabbix equivalent.
Run both systems in parallel
Keep PRTG running and collecting while Zabbix monitors the same devices, and compare the alerts each system raises over a period agreed in advance. Investigate every difference, whether a missing alert, an extra alert or a threshold mismatch, and fix the template or trigger that caused it. The step is done when the two systems raise matching alerts for the agreed set of test events and the open differences are closed or accepted in writing.
Cut over and retire PRTG
Move production alerting to Zabbix, switch on-call and ticketing integrations, and set PRTG to read-only or stop its sensors once the parallel run is accepted. Keep PRTG data exports and configuration records in your archive for audit and reference. Confirm the PRTG subscription end date with Paessler before deciding when to let it lapse, since the export timing guidance is covered in the export page. The step is done when Zabbix is the only source of production alerts and the archived records are verified.
Questions buyers ask before moving from PRTG to Zabbix
What drives the total cost of moving from PRTG to Zabbix?
The software itself has no license fee, so the cost is almost entirely people, infrastructure and optional support. Zabbix states that its open source software has no license fee, no device limits and no feature gates. Your costs fall into four groups: the staff time to design templates, discovery rules and notifications; servers and a database for the Zabbix server, web frontend and any proxies; the migration effort itself; and the ongoing operation of monitoring. Costs rise with the number of hosts, the depth of custom templates and the number of sites that need proxies. Ask any vendor or partner for a quote that separates one-time build work from recurring operations and support.
How long does a PRTG to Zabbix migration take?
No fixed duration applies, because the timeline depends on your estate and how much of PRTG's configuration you rebuild. The main drivers are the number of devices and sensors, how many sensors can be mapped to existing Zabbix templates and how many custom sensors, maps and notification rules must be recreated by hand. Running PRTG and Zabbix side by side until alerts match adds time but reduces cutover risk. Your PRTG subscription end date sets a hard deadline, so start with an inventory and an export plan. Ask for a written scope with phases and acceptance criteria before work begins.
Can our team run Zabbix without a partner?
Yes, many teams run Zabbix in-house, provided someone owns the design and can troubleshoot the platform. The work includes installing the server, database and web frontend, choosing a supported database such as PostgreSQL or MySQL, deploying proxies for remote sites and writing or adapting templates. Zabbix sells technical support subscriptions, so you can keep an in-house team and still buy vendor help for specific incidents. Teams without prior Zabbix experience usually benefit from an external review of the design before go-live. Check your staffing honestly against the scope before deciding.
What skills does a team need to operate Zabbix?
Operators need working knowledge of Linux server administration, SQL databases, SNMP and network basics, and the Zabbix data model of hosts, items, triggers and actions. Someone should also understand templates and low-level discovery, since most of the value of Zabbix comes from well-built templates rather than sensor-by-sensor setup. High availability and proxy design require familiarity with clustering and distributed monitoring concepts. Plan training for the staff who will maintain monitoring, and document the build so knowledge does not sit with one person. Confirm the supported database and version matrix in the Zabbix requirements before you choose hardware.
Do we need a Zabbix support contract?
No, a support contract is optional, because the software is open source and carries no license fee. Zabbix sells paid technical support subscriptions in Silver, Gold, Platinum, Enterprise and Global tiers. The tiers differ in hours of coverage and response time, from 8x5 support with a 1 day response in Silver to 24x7 support with a 1 hour response in Global. Decide whether the business needs guaranteed response times for production monitoring, and compare that cost with the cost of an internal on-call rota. Community resources and in-house expertise can cover non-critical issues.
Does the AGPL-3.0 license affect internal use of Zabbix?
For internal monitoring inside your organization, the AGPL-3.0 license does not require you to publish your own configurations or scripts. Zabbix moved from GPL-2.0 to AGPL-3.0 starting with Zabbix 7.0, and versions up to 6.4 remain GPL-2.0. The key difference is that AGPL-3.0 includes a network-use clause, so if you modify Zabbix and offer the modified version to users over a network, you may have obligations to provide the source of those modifications. Internal use with unmodified code is the common case, but have your legal team review your intended use, especially if you plan to build a customer-facing portal on top of modified Zabbix.
When should we keep PRTG for specific checks?
Keep PRTG for a specific check only when no Zabbix template, item or custom script can cover it reliably within your operational limits. Typical candidates are niche sensors that a vendor supports only in PRTG, or checks owned by a team that will not change tools during the migration. Confirm each candidate against the Zabbix template library and your own custom needs before deciding. Keeping two tools adds licensing cost, alert duplication and operational overhead, so set an end date for any remaining PRTG sensors. Document which tool is the system of record for each service.
How do Zabbix proxies and high availability affect the design?
Proxies collect data from remote sites and reduce the load on the central server, while high availability protects the server itself. Zabbix 7.0 and later support proxy groups, which redistribute monitored hosts between proxies when one goes offline. The Zabbix server also supports a native high availability cluster with several nodes sharing one database, and failover occurs when the active node exceeds a configurable failover delay of 10 seconds to 15 minutes. Design these parts early, because they set the database sizing, network paths and maintenance windows. Confirm the chosen design against the Zabbix high availability and proxy documentation before procurement.
What to confirm with Paessler and Zabbix before deciding
Most of the cost and risk in a PRTG to Zabbix move sits in decisions you can make before any migration starts. Each question below narrows scope, timing or staffing, and the answers feed directly into a written migration plan.
What is our current sensor count and tier?
Pull the sensor total and the subscription tier from your PRTG license and map it to the sensors you actually poll. Many estates carry sensors that nobody reads, and retiring them shrinks the Zabbix item count before you size any hardware. Ask Paessler how the tier and any renewal terms apply if you run both products during a parallel period.
Which Zabbix version and support window fit us?
Zabbix 7.0 LTS has full support until 30 June 2027 and limited support until 30 June 2029, so a deployment started now has a clear support runway. Zabbix 8.0 LTS is planned for Q4 2026. Decide whether you will build on 7.0 LTS or wait for 8.0, and confirm which paid support tier, if any, your team needs for the response times you require.
Which database will the Zabbix server use?
Zabbix stores configuration and history in a database, and the choice affects backup, growth and staffing. Confirm which engine your DBAs already run, whether that engine and version are on the Zabbix requirements list, and whether TimescaleDB is needed for large history volumes. Also ask who owns partitioning and retention settings.
Which application checks must we keep?
PRTG sensors cover many application checks such as HTTP content, database queries and service status. List every check that matters to a business owner and find out whether a Zabbix template or custom item already covers it. Gaps usually mean scripts, external checks or a plan to retire the check, and those choices should be signed off before cutover.
Which notification integrations must keep working?
Alerts reach people through email, SMS, chat, ticketing and on-call tools, and each route is often wired into PRTG by hand. Inventory every notification path, confirm which ones Zabbix supports natively and which need a webhook or script, and agree who tests them. Alert parity is the test that should close the parallel run.
Who will run Zabbix after go-live?
Ask which engineers will own templates, proxies, upgrades, backups and on-call response once PRTG is switched off. Zabbix support subscriptions are optional, so the staffing decision is a recurring cost of its own. Confirm the skills gap, the training time and whether an external partner will cover upgrades and tuning under a written scope.
How DeployOpen helps evaluate and implement Zabbix
DeployOpen plans, implements, customizes, hardens, backs up, documents and supports self-hosted Zabbix inside your own infrastructure, whether that is your cloud accounts, data centers or an air-gapped network. Most engagements are fixed-scope, so the sensor-to-template mapping, the proxy layout, the database choice, the high availability design and the handover documents are agreed in writing before work starts. Ongoing support, upgrades and continuous testing are available as a retainer, which matters because Zabbix standard releases arrive every 6 months and LTS releases every 1.5 years, so someone has to own the upgrade path.
Evaluation usually starts before any commitment. The useful outputs are an inventory of PRTG sensors grouped by what they actually measure, a list of which checks have a Zabbix template or need a custom item, a test of SNMP and agent coverage against a representative set of devices, and a sizing view of proxies and the database. Parallel running is the step most teams underestimate: both systems watch the same hosts until alert volume, notification routing and dashboards agree with what operators expect. Confirm with your own engineers which PRTG alerts are trusted today, because those define the acceptance criteria.
DeployOpen does not publish prices. A quote follows from the written scope, which should state the number of hosts and sensors in scope, the systems that need custom templates, the high availability and backup targets, the parallel running period and who will operate Zabbix afterwards. Ask for those items to be itemized so you can compare the implementation fee, the recurring support retainer and any Zabbix technical support subscription you decide to buy separately. DeployOpen is not a Zabbix or Paessler partner, reseller or certified provider.
