Migrate from Cronhub
step by step
Recreate up to three Cronhub jobs on the Free beta with dashboard alerts and the complete 44-tool site-health catalog.
Use manual migration guideOr follow the step-by-step manual guide below.
Step-by-step migration
Export your Cronhub jobs
Go to your Cronhub dashboard and note down each job name, schedule (cron expression), and grace period.
Create a CheckFast account
Sign up at checkfast.io. Free accounts can recreate up to three combined monitors; use the manual path while bulk import remains closed.
Create matching jobs
For each Cronhub job, create a new monitor in CheckFast with the same schedule and grace period. You'll get a new ping URL.
Replace ping URLs
In your crontab or CI/CD config, replace the Cronhub ping URL with your new CheckFast ping URL. Use the sed commands below for a quick swap.
Verify & set up alerts
Trigger a test ping and confirm it appears in your dashboard. Connect Telegram, or Slack on Pro and Agency, for missed-ping alerts.
Quick URL replacement:
# Each CheckFast job gets a new UUID. Copy its generated URL, # then replace the corresponding Cronhub URL explicitly. OLD_URL='https://cronhub.io/ping/<old-uuid>' NEW_URL='https://checkfast.io/api/ping/<new-uuid>' # Preview the matching crontab entry first crontab -l | grep -F "$OLD_URL" # Replace this job only, then review before installing crontab -l | sed "s|$OLD_URL|$NEW_URL|g" > /tmp/checkfast-crontab cat /tmp/checkfast-crontab crontab /tmp/checkfast-crontab
Cronhub vs CheckFast
Migration FAQ
Both accept simple HTTP pings, but the URLs are not interchangeable. Every new CheckFast job receives a new UUID under /api/ping/<uuid>. Replace each full Cronhub URL with its mapped CheckFast URL and test the mapping before cutover.
No. CheckFast generates a new UUID for every job. Keep an explicit old-to-new URL mapping, update each cron entry, and send a test ping before removing the old endpoint.
If Cronhub shuts down before you migrate, your cron jobs will still run — they just won't be monitored. Any curl calls to Cronhub will fail silently (if you use -f flag) or return errors. Migrate now to avoid a monitoring gap.
CheckFast records ?type=start, ?type=fail, and a base-URL success ping. It does not currently derive run duration, hung-job detection, or p95 alerts from the start marker.
The authenticated importer accepts one name | cron-expression | grace-minutes row per job and creates new CheckFast jobs subject to your paid plan's combined quota. It is not a Cronhub export parser: you must prepare the rows and replace each old ping URL with the newly generated URL.
Restore monitoring after the shutdown.
Recreate each job, replace its old ping URL with the new CheckFast URL, and trigger a test ping before relying on the new monitor.
Use the manual guide