How to migrate from Freshping to StackEye

Freshping's free tier is generous — until you hit the limits. When you need more monitors, shorter check intervals, or real status pages, the jump to a paid plan can sting. This guide walks you through moving your Freshping checks to StackEye in under 30 minutes.

Why teams switch from Freshping

Freshping's free plan is a great entry point: 50 checks at 1-minute intervals with basic email alerts. But as teams grow, a few friction points appear:

• Paid plans start at $12/mo — for 200 checks at 1-minute intervals. StackEye Starter is $5/mo for 25 monitors at 2-minute intervals, and Pro is $12/mo for 100 monitors at 1-minute intervals — a better ratio for most teams.
• Status pages are limited on the free tier — Freshping free status pages show basic uptime history. StackEye includes full incident management and custom domain support on all paid plans.
• No scoped API keys — Freshping's API uses account-level credentials. StackEye supports per-key permissions (probes:read, probes:write, alerts:read) for safer CI/CD and automation integrations.
• No multi-region consensus — Freshping checks from a single location. StackEye runs from multiple regions and only alerts when a majority confirm the failure, eliminating single-datacenter false positives.

Feature mapping

Step 1: Export your checks from Freshping

Freshping doesn't have a dedicated export button in the UI, but you can export via the Freshping API. You'll need your API key from Settings → API.

# List all checks (replace YOUR_API_KEY)
curl -s "https://api.freshping.io/v1/checks/" \
  -H "Authorization: Token YOUR_API_KEY" \
  | python3 -m json.tool > freshping-checks.json

Either export that way, or open Freshping's Checks page and use the export option if your plan supports it. You need each check's URL and name.

Step 2: Prepare a CSV for import

The StackEye CLI accepts a CSV with the following columns. Create freshping-import.csv:

name,url,interval,regions
My App,https://app.example.com,60,"nyc3,sfo3,chi1"
API,https://api.example.com,60,"nyc3,sfo3,chi1"

• name — display name (used in alerts and status pages)
• url — the URL to monitor
• interval — check frequency in seconds (60 = 1 minute)
• regions — comma-separated region identifiers (run stackeye region list to see available regions)

Step 3: Sign up and create your API key

Create a free StackEye account at app.stackeye.io/signup. No credit card required for the free tier. Then create an API key under Settings → API Keys with probes:write and labels:write permissions:

stackeye configure --api-key se_YOUR_KEY_HERE

Step 4: Import probes

# Dry run first — review what will be created
stackeye probe import freshping-import.csv --dry-run

# Run the actual import
stackeye probe import freshping-import.csv

Known CLI behavior: Labels specified in the CSV are not applied during import. Apply them immediately after with stackeye probe label <id> key=value or use the bulk label command.

Step 5: Migrate alert channels

In StackEye, alert channels are configured under Alerts → Channels. Freshping supports email, Slack, and webhooks — StackEye supports all three plus PagerDuty, SMS, and Microsoft Teams.

Step 6: Migrate your status page

If you have a Freshping status page, recreate it in StackEye under Status Pages → New. Select the probes to display, add branding, and publish. Custom domains require a CNAME pointing to status.stackeye.io.

Step 7: Validate and cut over

Run both tools in parallel for 24–48 hours before cancelling Freshping. Cutover checklist:

• All probes showing UP status in StackEye dashboard
• Alert channels verified — send a test alert from each
• Status page live and displaying correct probe statuses
• Custom domain CNAME updated (if applicable)
• Team members invited to the StackEye organization
• Freshping subscription cancelled

Pricing comparison