Does Pingdom have a monitor export feature?

Not in the UI. The only way to get your check configuration out of Pingdom is through its REST API, which returns JSON. That's exactly what Vantaj's importer uses - it calls the API for you with a read-only token, so you never have to script anything.

Is my Pingdom API token stored anywhere?

No. Vantaj uses the token once to read your check list during the import and never stores it. Using a read-only token also means it can't change or delete anything in your Pingdom account.

Do Pingdom transaction (browser) checks import?

No. Transaction checks are scripted browser journeys, which don't map to uptime monitors in any tool. HTTP, ping, TCP, and SMTP checks all import; transaction checks need to be rebuilt as targeted HTTP checks against the endpoints they exercise.

Can I keep Pingdom running during the migration?

Yes. The import uses a read-only token and changes nothing in your Pingdom account. Run both providers in parallel for a few days, confirm Vantaj's alerts fire the way you expect, then cancel Pingdom on your own schedule.

Does my uptime history come over?

No - historical data isn't importable in a meaningful form from any provider. Your Vantaj history starts at import time, which is another reason to run both tools in parallel through the transition.

Migrating Your Monitors from Pingdom in 60 Seconds

Pingdom has been the enterprise-name in uptime monitoring for two decades, and since the SolarWinds acquisition it's priced like one. If you're paying enterprise rates for what is, for most teams, a list of HTTP checks and a ping or two, the only thing standing between you and a cheaper tool is getting those checks out.

That's the hurdle. Pingdom has no export button - your check configuration lives behind its REST API, as JSON, and the usual migration advice is "write a script." You don't have to. Vantaj imports your Pingdom account directly with a single read-only API token, in about a minute. The flow:

Create a read-only API token in Pingdom (Settings → Pingdom API)
Paste it into Vantaj under Settings → Import Monitors → Quick import from Pingdom
Review the fetched checks - everything importable is pre-selected
Click Import and monitoring starts immediately

Step 1: Create a read-only API token (20 seconds)

In my.pingdom.com, open Settings → Pingdom API and click Add API token. Give it a name and select Read access.

Read access is all the importer needs - the token can list your checks but can't modify or delete anything. Your Pingdom account is untouched by the migration, so you can keep it running in parallel as long as you like.

Step 2: Paste it into Vantaj (10 seconds)

In Vantaj, go to Settings → Import Monitors and choose Quick import from Pingdom. Paste the token and click Fetch monitors.

Vantaj calls the Pingdom API on your behalf and shows every check it found. The token is used for that one request and never stored.

Step 3: Review and import (30 seconds)

Every importable check is pre-selected. The preview shows what each one becomes:

Pingdom	Becomes in Vantaj
HTTP check	HTTP(s) monitor (URL including path, HTTP or HTTPS)
Ping check	Ping (ICMP) monitor
TCP check	Port (TCP) monitor, with the port
SMTP check	SMTP monitor

The details come over too:

Keyword assertions are translated. Pingdom's should contain becomes Vantaj's response must contain; should not contain becomes must not contain. Your error-page detection keeps working.
Check intervals are snapped to the nearest Vantaj interval, respecting your plan's minimum.
Paused checks stay paused.
Duplicates are caught. Anything already monitored in Vantaj is flagged and deselected, so re-running the import never creates copies.

Click Import, and checks start immediately from multiple regions.

What doesn't migrate

Honesty section - four things stay behind:

DNS, POP3, and IMAP checks. Vantaj doesn't have direct equivalents for these Pingdom check types, so they're skipped. DNS coverage in Vantaj comes through domain monitoring instead.

Transaction (browser) checks. Scripted multi-step browser journeys don't map to uptime monitors. Rebuild the ones that matter as targeted HTTP checks against the endpoints they exercise - in practice that covers most of what teams actually alert on.

Alert integrations. Notification channels work too differently across providers to map automatically. In Vantaj you set them up once - Slack, PagerDuty, Telegram, webhooks, email - under Alerts & Notifications, and they apply to every monitor.

HTTP basic auth credentials. This one is on Pingdom: its API doesn't expose stored credentials, so there's nothing for an importer to read. If any checks use basic auth, re-enter the credentials on the imported monitors in Vantaj - it takes seconds per monitor.

And as with every provider, historical uptime data doesn't come over. Your Vantaj graphs start at import time; run both tools in parallel if you want overlapping coverage during the switch.

Why we built this

Nobody in the uptime monitoring space offers a real self-serve importer. Pingdom's own answer to "how do I get my checks out?" is a REST API reference. We think switching tools should take a minute, not an afternoon of scripting - and that the same courtesy should apply in both directions, which is why the importer asks for a read-only token and leaves your Pingdom account exactly as it found it.

Coming from somewhere else? We also import from UptimeRobot, StatusCake, and Better Stack - and anything that can produce a spreadsheet via CSV bulk import.

Ready to try it? Create a free Vantaj account - 20 monitors free, no credit card - and see the full import guide in the docs.