Migrate from Pingdom
One-click import of your Pingdom checks into HowlOps — plus a manual checklist for channels and status pages.
Overview
HowlOps imports your Pingdom checks directly over the Pingdom API. Notification channels and status pages are still a short manual step (they don't map one-to-one). Nothing in Pingdom is ever modified — the import only reads.
Time: a few minutes for checks, plus a little for channels/status pages Prerequisites: a Pingdom API token; a HowlOps account
One-click check import (recommended)
- In HowlOps, go to Settings → Import (or start it from the onboarding wizard).
- Choose Pingdom and paste your API token (Pingdom: My Pingdom → Account → The Pingdom API). A read-only token is enough — the import only reads, and HowlOps never stores your token.
- Click Load items to see a preview table of every check and what it maps to. Rows that can't be imported are shown in yellow with the reason.
- Tick the checks you want and click Import. A progress bar shows
Importing 34/120…; a problem with one check never stops the rest. - You get a summary —
117 imported, 3 skipped— and a Download report CSV.
What gets imported
| Pingdom check type | HowlOps equivalent | Notes |
|---|---|---|
| HTTP / HTTP Custom | HTTP / HTTPS monitor | Direct equivalent |
| Ping | Ping (ICMP) monitor | Host taken from the check's hostname |
| TCP, DNS, UDP, SMTP, POP3, IMAP | not imported | HowlOps has no equivalent check type for these — see below |
- TCP / DNS / UDP / SMTP / POP3 / IMAP checks are skipped with a reason in the report. For most "is the service up" cases, recreate them as an HTTP monitor against the service's health endpoint.
- Check intervals are clamped up to your plan's minimum and a note is added to the report (Pingdom's resolution is 1/5/15/30/60 minutes depending on plan; HowlOps Uptime Free = 120 s, and paid plans go faster). Nothing fails just because an interval was too fast for your plan.
Re-running is safe
Every import is idempotent — HowlOps remembers which Pingdom check created which HowlOps monitor, so a second run updates or skips rather than duplicating. If an import is interrupted (e.g. a deploy restarts the service mid-run), just run it again.
Manual steps (channels & status pages)
The rest of the migration is a short manual checklist. The concepts map closely between the two platforms.
Concept mapping
| Pingdom | HowlOps equivalent | Notes |
|---|---|---|
| HTTP / HTTP Custom check | HTTP / HTTPS monitor | Direct equivalent |
| Ping check | Ping (ICMP) monitor | Direct equivalent |
| TCP / DNS / UDP / SMTP / POP3 / IMAP check | none | HowlOps does not have these check types. For most "is the service up" cases, use an HTTP monitor against the service's health endpoint instead. |
| Contact / Integration | Notification channel | HowlOps calls them "channels" |
| Public Status Page | Status page | More customisation options available |
| Maintenance window | Maintenance window | Same concept |
Checks themselves are handled by the one-click import above — you don't need to recreate them by hand. The steps below cover the parts the importer doesn't touch: notification channels and status pages.
Step 1: Recreate notification channels
In Integrations → + Add Channel, recreate each Pingdom contact/integration:
| Pingdom contact/integration | HowlOps channel type |
|---|---|
| Slack | Slack (Incoming Webhook) |
| Webhook | Custom Webhook |
| PagerDuty | PagerDuty |
| SMS | SMS |
After adding each channel, click Send Test Alert to verify it works before assigning it to monitors.
Step 2: Assign channels to monitors
For each monitor:
- Open the monitor and click Edit.
- In the Notifications section, add the appropriate channels.
- Click Save.
Step 3: Recreate your status page
- Go to Status Pages → + New Status Page.
- Give it the same name and select the same monitors.
- If you had a custom domain on Pingdom, follow the custom domain setup in Tutorials: Public status page.
Step 4: Validate and cut over
Before disabling Pingdom:
- Let HowlOps run in parallel for at least 24 hours to confirm checks are running correctly.
- Trigger a deliberate test failure (take down a test endpoint briefly) to confirm alert delivery.
- Verify the status page looks correct.
Once you are confident everything is working:
- Disable or delete checks in Pingdom.
- Update your DNS or subscriber links to point to the new HowlOps status page URL.
Differences to be aware of
- Check intervals: HowlOps Uptime Free has a 120-second minimum. Paid Uptime plans get faster intervals: 60 s on S, 30 s on M, down to 15 s on L.
- Probing regions: HowlOps probes from four global regions — Nuremberg (EU), Helsinki (EU), N. California (US), and Singapore (Asia) — so you keep worldwide coverage when cutting over from Pingdom's checkpoints.
- Heartbeats: Pingdom does not have a heartbeat feature for cron/job monitoring. If you were monitoring a scheduled job via an HTTP check, consider switching to native heartbeats for more reliable detection.
- On-call and escalation: Set up escalation policies in HowlOps to ensure alerts are not missed.
What's next
- Concepts: Monitors: understand all monitor options
- Concepts: Escalation: set up escalation policies
- Tutorials: Public status page: configure your new status page
Was this page helpful?