How do you migrate an existing Zabbix or Prometheus setup to HertzBeat?

A migration goes smoothest as a staged, parallel-run process rather than a single cutover.

1. Inventory existing targets — list every host, service, and exporter currently monitored, along with its check type.
2. Map targets to HertzBeat templates — for Prometheus exporters, this can be nearly a no-op since HertzBeat can scrape them directly via its Prometheus-compatible monitor type; for Zabbix items, find or write the equivalent YML template.
3. Recreate alerting logic — translate Zabbix triggers or Prometheus alert rules into HertzBeat threshold rules, using multi-expression alarms for anything combining multiple conditions.
4. Configure notification channels — set up receivers for the same destinations (Slack, email, etc.) the old system used.
5. Run both systems in parallel for a period, comparing alert firing behavior before fully trusting HertzBeat.
6. Decommission the legacy system once dashboards, thresholds, and notifications are validated, retiring old agents last.