← All articles

Freshping Migration Guide: Export, Rebuild, Cut Over

Published · 9 min read

Key takeaways

  • Freshping's full retirement covers uptime checks, alert channels, and hosted status pages, so treat the migration as a parallel-run project rather than a last-minute rebuild.
  • Export incident history and status page subscribers first, because they are the hardest data to reconstruct and subscriber consent does not transfer between tools.
  • Rebuild alert channels before checks, then recreate monitors in criticality order, since 20-30% of typical checks are not worth migrating.
  • Run old and new monitors side by side for seven days, verify parity with a deliberate failure test, and cut over only after alerts reach the on-call person.
  • Hosted replacements start around $5/mo, while UptimeRobot's free tier (50 monitors) and self-hosted Uptime Kuma cover basic needs at zero cost.

Freshping's checks and status pages are being retired, so your migration is a parallel-run project: export your checks, alert channels, status page subscribers, and incident history now, rebuild them on a replacement while Freshping still runs, verify parity, then cut over. This guide gives you the week-by-week timeline and the parity checklist to do it without a monitoring gap.

freshping

Freshping is Freshworks' free uptime monitoring tool, offering URL checks, status pages, and downtime alerts. Freshworks has announced it is retiring the product, and teams are now searching "freshping alternative" because their monitors and status pages will stop working. The retirement covers Freshping's checks, alert channels, and hosted status pages, per Freshworks' product retirement documentation.

If you're paying for Statuspage or Pingdom instead, the same gap exists: protocol-level probes without the $29-199/month bill. StatusPulse covers that with real probe-based checks from $5/mo, free for 5 probes and one status page.

What exactly is being retired in Freshping, and by when?

Confirm what your account still has access to

Freshworks is retiring Freshping, and the shutdown covers the whole product: uptime checks, alert channels, and hosted status pages. Your exact deadline arrives by email and in the in-app banner, so check both rather than relying on a date you read in a forum. Before that date, log in and inventory what you actually have: how many checks, which protocols they use, which Slack or PagerDuty channels receive alerts, and whether you run a public status page with subscribers. Screenshot your incident history too, since export options may be limited.

Set your internal cutover date

Work backwards from the shutdown notice and pick a cutover at least a week earlier, so you can run old and new checks in parallel and tune thresholds without false alarms. If you start rebuilding now, a week is enough to replicate checks, alert routing, and your status page. For threshold tuning during that overlap, see https://blog.statuspulse.ai/post/stop-alert-fatigue-how-to-tune-monitoring-thresholds.

What data can you export from Freshping before shutdown?

Export what you can before your account access ends. Freshping's export options are limited, so plan to recreate some configuration by hand. The Freshping help documentation covers what's available in your dashboard, but here is what to grab and in what form.

Monitors and check configuration

Screenshot or copy every monitor: URL, check interval, method (HTTP, keyword, port), and any custom headers or timeouts. Freshping does not offer a one-click bulk export of monitor configs, so a structured spreadsheet is your safest copy.

Incident history and uptime reports

Download uptime reports and incident logs per monitor as CSV or PDF where the dashboard allows. This is your SLA evidence and your incident postmortem source, and it is the hardest data to reconstruct later.

Status page content and subscribers

Export your status page's subscriber list with emails and notification preferences. Subscriber consent does not transfer automatically to any new tool, so keep the original opt-in record.

What you cannot export and must recreate

Alert routing rules, on-call schedules, and integration webhooks have no export. Rebuild them in the new tool manually; when you do, check protocol-level coverage like TCP and DNS probes, not just URL pings. See how StatusPulse handles probes and status pages for what parity should look like.

How do you rebuild your checks and alert channels on a new monitor without gaps?

Inventory your checks by criticality, not alphabetically

Export your Freshping check list, then sort it into three tiers: the 3-5 checks that page you at 3 AM (your API, your signup flow, your database), the ones that matter during business hours, and the vanity checks you never acted on. Rebuild in that order. Most teams find 20-30% of their Freshping checks were never worth migrating.

Rebuild alert channels first, checks second

Set up your PagerDuty integration, Slack webhook, or SMS routing before creating a single check, and send test alerts through every channel. A check with a broken alert path gives you a false sense of coverage: it fails silently and you find out from a customer tweet.

Match probe types, not just URLs

Freshping checks are mostly HTTP and ping. Before rebuilding, map each check to the protocol that actually detects the failure. A homepage returning 200 tells you nothing if your Postgres connection pool is exhausted. We break down the options, including TCP, DNS, and keyword checks, in our guide to monitoring probe types beyond HTTP and ping (https://blog.statuspulse.ai/post/11-monitoring-probe-types-beyond-http-and-ping). The honest caveat on our own product: StatusPulse covers HTTP, keyword, TCP, ping, and DNS probes, so if your Freshping setup leaned on exotic protocols, verify support before committing.

Tune thresholds to avoid false alarms on day one

Imported checks at default intervals and thresholds will page you for transient blips. Set consecutive failures to 2-3, confirmations from a second region where the tool supports it, and run the first 48 hours in a muted state before enabling on-call alerts.

How do you migrate status page subscribers and incident history?

Exporting and re-importing subscribers

Freshping lets you export your status page subscriber list (emails and notification preferences) as a CSV. Import it into your new tool's subscriber list, then send a one-off email telling subscribers the page has moved and asking them to confirm. Some tools re-verify automatically on import; check whether yours does before you delete the old page.

Rebuilding incident history

Most status page tools don't import past incidents directly. Export your incident timeline from Freshping, then post the notable ones as backdated incidents or a linked "historical incidents" archive page. For SLA reporting, keep the CSV yourself; a public history of the last 6-12 months is usually enough for customers.

Custom domain and DNS cutover

Point your status subdomain (status.yourapp.com) at the new tool only after the page content matches. Lower the TTL to 300 seconds a day ahead, then swap the CNAME. Verify the old page is dead before announcing the new URL. For the pricing math behind the switch, see https://blog.statuspulse.ai/post/save-60-70-on-statuspageio-and-pingdom-monitoring.

What Freshping features have no direct equivalent elsewhere?

Three Freshping capabilities will not carry over cleanly, so plan workarounds before your deadline.

Freshping featureWhat you loseWorkaround
Free unlimited checksZero-cost coverage for many URLsUptimeRobot's free tier (50 monitors) or StatusPulse's 5 free probes
Freshworks suite hooksAuto-incident sync to Freshdesk/FreshserviceRebuild via generic webhooks or PagerDuty integration
Status page subscriber listEmail list of people expecting outage updatesExport it yourself; Freshping's help docs cover status page subscriber export

The Freshworks integration is the hardest to replace: most standalone monitors talk to PagerDuty or Slack, not Freshdesk, so expect to wire a webhook manually. Subscriber export matters most because those emails are your incident audience; re-collecting them after cutover is slow and lossy.

How do you verify parity before cutting over?

The parallel-run week

Run both Freshping and your new monitor side by side for at least seven days. Keep Freshping as the source of truth for alerting during this window so a misconfigured new check cannot create a coverage gap. Compare uptime percentages, response times, and alert timestamps daily. Any check that disagrees between the two tools points to a wrong interval, endpoint, or timeout you need to fix before canceling.

Parity checklist: checks, alerts, status page

Confirm three things match, not just exist:

  • Checks: same URLs, same intervals, same expected status codes and keywords. A homepage check that passes on a 302 redirect in one tool and fails in the other is a false alarm waiting for 3 AM.
  • Alert channels: send one test alert through every channel — email, SMS, Slack, and PagerDuty if you use it — and confirm it reaches the on-call person, not a dead inbox.
  • Status page: verify your public page renders, subscribers receive a test incident notification, and your custom domain resolves with the right SSL cert.

Deliberate failure test

Take down a staging endpoint on purpose and time how long detection takes on each tool. If your new monitor alerts slower than Freshping did, tighten the interval or timeout now. This one test tells you more than a week of green dashboards, and it proves your downtime alerts actually fire before paying customers find the outage first.

What should you do if you miss the export deadline?

First, check whether your Freshping account still resolves: Freshworks has kept retired-product logins accessible for a grace period in past sunsets, so try exporting checks via the API before assuming the data is gone. If the account is locked, contact Freshworks support directly and request a manual export of your checks and subscriber list.

Second, reconstruct from what you already own: your DNS records, deployment configs, and on-call history tell you which endpoints you were monitoring. Rebuilding 10-20 checks manually takes under an hour on any tool. UptimeRobot's free tier covers 50 monitors (pricing), so coverage gaps close faster than subscriber migration.

Which replacement fits a small SaaS team's budget?

For most Freshping refugees, the honest answer is: free or near-free covers it. UptimeRobot's free tier handles basic URL checks, and self-hosted Uptime Kuma costs nothing but your maintenance time. If you want a hosted status page plus monitoring without thinking about servers, budget $5-19/mo.

StatusPulse starts at $5/mo (Starter) with a free tier of 5 probes and 1 status page, and Pro at $19/mo. Unlike most tools at that price, checks run as protocol-level probes rather than homepage pings, so you can watch an actual API endpoint instead of a vanity URL. It includes PagerDuty-style alerting and subscriber-ready status pages, which is what most Freshping migrants actually lose.

Where it falls short: no log management, no synthetic browser checks, and fewer integrations than Better Stack or Hyperping. If you need those, expect to pay $25+/mo elsewhere. For a solo founder replacing Freshping's core job, $5/mo buys parity.

FAQ

Is Freshping shutting down completely, or just the free plan?

The entire product is being retired: uptime checks, alert channels, and hosted status pages all stop working, regardless of which plan you were on. Your exact deadline arrives by email and in the in-app banner, so check both rather than trusting a date from a forum post. Log in now and inventory what you have before access ends.

Can I export my Freshping uptime history as CSV?

Partly. The dashboard lets you download uptime reports and incident logs per monitor as CSV or PDF where available, but there is no one-click bulk export of monitor configurations. Grab the incident history first, since it is your SLA evidence and the hardest data to reconstruct. Alert routing rules and integration webhooks have no export at all.

What is the cheapest Freshping alternative with a status page included?

Self-hosted Uptime Kuma costs nothing but maintenance time. Among hosted options, StatusPulse starts at $5/mo with a free tier of 5 probes and one status page, running protocol-level checks rather than homepage pings. UptimeRobot's free tier covers 50 monitors but its status page sits on paid plans, so budget accordingly if subscribers matter.

Will my status page subscribers get notified when I switch tools?

Not automatically. Subscriber consent does not transfer between tools, so export the email list with notification preferences before your account closes, and keep the original opt-in records. After cutover, import the list and send a test incident notification to confirm delivery. Re-collecting subscribers after the switch is slow and lossy, so do this first.

How long does a Freshping migration take for a 20-monitor account?

A focused week is enough. Rebuild alert channels first and test them, then recreate checks in criticality order, since 20-30% of typical checks turn out not to be worth migrating. Run both tools in parallel for seven days with Freshping still alerting, verify parity, and cut over. Manual reconstruction alone takes under an hour.

Monitor it, then tell your customers

10 probes, 3 status pages, forever. No credit card.