How to Migrate from Uptime Kuma to Pingzo

Uptime Kuma is a widely used open-source, self-hosted monitoring tool. But as your services grow, managing your own monitoring servers introduces significant operational overhead: dealing with server maintenance, configuring reverse proxies, managing Docker containers, and handling false alerts caused by single-node network drops. Upgrading to Pingzo provides a fully managed, globally distributed check network with native WhatsApp alerts.

This guide details how to migrate your services and settings from self-hosted Uptime Kuma to Pingzo.

Why Teams Migrate to Pingzo Managed Cloud

• Multi-Region Consensus Checking: Pingzo checks your endpoints from multiple global locations, preventing false alarms caused by localized network routing issues.
• Zero Server Maintenance: Eliminate the need to maintain Linux servers, update Docker images, manage Let's Encrypt certificates, or secure databases.
• Official WhatsApp Notifications: Get native WhatsApp Business API alerts directly, bypassing complex community script configurations.

Step 1: Export Your Settings from Uptime Kuma

Export your current settings to prevent manually re-entering your monitoring rules:

1. Log in to your self-hosted Uptime Kuma dashboard.
2. Go to Settings -> Backup.
3. Click the Export button to download your configuration file as a JSON backup.
4. This file contains your active monitor list, check types, retry settings, and interval metrics.

Step 2: Import Monitors to Pingzo Cloud

Import your endpoints into Pingzo's cloud-hosted infrastructure:

1. Access your Pingzo Dashboard.
2. Navigate to Monitors and choose Create Monitor.
3. Use the target URLs and intervals from your Kuma backup. Configure checks down to 30 seconds for critical database APIs.
4. Create alert destinations for your team, including Slack webhooks, Discord bots, and official WhatsApp numbers.

Step 3: Recreate Your Status Boards

Rebuild your public status dashboards on Pingzo:

1. Navigate to Status Pages -> Create Status Page.
2. Link your new cloud checkers to their respective status cards.
3. Map your custom domain (e.g. status.yourcompany.com). Pingzo handles DNS configurations and issues free SSL certificates automatically.
4. Upload your company brand logo, add custom header text, and configure your brand colors.

Step 4: Decommission Your Self-Hosted Instance

Once your new monitoring pipeline is fully verified, you can wind down your old setup:

1. Add Pingzo's status CNAME record to your active domain registrar.
2. Log in to your self-hosted server, stop your active Uptime Kuma Docker containers, and disable background services.
3. Shut down the virtual server instance to save on hosting costs.
4. Run verification checks to confirm that your public status pages load correctly and alert channels are fully functional.