Skip to main content

Migrate from Pingdom to SolidPing

You do not have to recreate your checks by hand. SolidPing reads your Pingdom checks through the Pingdom API 3.1 and turns each one into a SolidPing check. It previews first, so nothing is written until you say so.

Not sure you want to move? Read SolidPing vs Pingdom first. It says where Pingdom is the better choice too.

1. Give SolidPing your checks​

Two ways, pick the one you are comfortable with.

With a read-only API token. In My Pingdom open Settings > Pingdom API > Add API token and give it read access only. SolidPing uses the token once to read your checks and their details, and never stores it.

With a JSON export, if you would rather not share a token at all. Fetch your checks yourself and paste the result:

curl -s -H "Authorization: Bearer $PINGDOM_TOKEN" \
'https://api.pingdom.com/api/3.1/checks?include_tags=true' \
> pingdom-checks.json

The list endpoint leaves out some settings. For the most complete import, paste a JSON array of GET /api/3.1/checks/{id} responses instead: the importer accepts both shapes.

2. Preview​

In the SolidPing dashboard open Checks > More actions > Import, pick Pingdom, paste the token or the JSON and run the preview. You get the list of checks that would be created and every item that did not map cleanly.

Or use the API with an organization admin token:

curl -s -X POST \
-H "Authorization: Bearer $TOKEN" \
-H 'Content-Type: application/json' \
--data-binary @pingdom-checks.json \
'https://your-instance/api/v1/orgs/myorg/checks/import/convert?source=pingdom&dryRun=true'

3. Apply​

Confirm in the dashboard, or drop dryRun=true from the API call. Imported checks carry the label solidping-managed=pingdom, so running the import again updates them in place instead of duplicating. You can keep Pingdom running next to SolidPing until you are ready to cut over.

What maps​

PingdomSolidPing
HTTP / HTTPShttp: URL, port, expected and forbidden text, request headers, POST data
HTTP customhttp on the same URL, with a warning
TCP, UDPtcp, udp, with their send and expect strings
Pingicmp
DNSdns, with the expected IP and the nameserver
SMTP, POP3, IMAPsmtp, pop3, imap
Check interval, paused state, tagsperiod, disabled check, labels
"Alert after n failures"a confirmation period of n intervals

What you do by hand​

The preview lists all of this as warnings.

  • Transaction (TMS) checks are skipped. SolidPing has browser checks for scripted journeys; rebuild the important ones there.
  • Basic auth credentials are not imported. The preview names the checks that had them: re-enter them on the check, where they are stored encrypted.
  • Alert contacts and integrations. They do not carry over. Set up SolidPing integrations and on-call.
  • Probe filters and maintenance windows. Recreate them if you need them.
  • Status history. Results are not portable between tools.

Full reference​

The complete guide, kept next to the code, is at solidping.io/docs/features/migrate/from-pingdom. If something does not import the way you expect, open an issue with a sample. That sample is most of the work.