Migrate from Cronhub to CronCraft

Cronhub is shutting down June 30, 2026. This guide is for teams who already have curl pings wired into scripts and want the smallest possible change set.

Read the Cronhub alternative overview first if you want positioning and feature mapping. For Docker self-hosting, the ping path is the same idea — only the base URL changes.

1. Export your monitor list from Cronhub

Grab names, schedules, and grace expectations while Cronhub's UI is still available. You will recreate each logical monitor as a job in CronCraft.

2. Create matching jobs in CronCraft

For each Cronhub monitor:

Register a job with the same cadence (cron expression).
Set a grace period that matches how late a run is allowed before you want an alert — this is how CronCraft avoids false positives on slow runs.
Copy the new ping URL from the job detail page.

3. Replace ping URLs in your codebase

Search your repo and server configs for cronhub.io (or your old domain). Swap the host and path segment for CronCraft's token URL:

curl -fsS --retry 3 https://croncraft.app/ping/YOUR_TOKEN > /dev/null

If you used success/fail endpoints on Cronhub, use /ping/TOKEN for success and /ping/TOKEN/fail for explicit failure — same pattern as CronCraft docs.

4. Run a test window

Leave both systems active briefly if you can: fire a manual run, confirm the CronCraft dashboard shows the ping, then remove the old Cronhub call once you trust the new path.

5. Alert channels

Free tier includes email. If you used Slack or webhooks on Cronhub, connect those under Pro in CronCraft settings after upgrade — see Slack integration.

Free tier, no credit card — create jobs and paste new URLs today.