Migrate from UptimeRobot to DomainCare
Move your UptimeRobot monitors, contacts, and alert integrations to DomainCare with this step-by-step migration guide.
UptimeRobot's free tier has made it a go-to choice for developers getting started with uptime monitoring. But as your infrastructure matures — and especially as your domain portfolio grows — you'll notice the gaps: no SSL expiry tracking, no DNS change detection, no email deliverability health, and no per-domain grouping. DomainCare was built to fill exactly those gaps.
This guide takes you from a running UptimeRobot account to a fully configured DomainCare setup.
What you'll move
- HTTP/HTTPS monitors (uptime checks)
- Keyword checks
- Alert contacts (email, SMS, Slack, webhook)
- Maintenance windows
Step 1: List your UptimeRobot monitors
UptimeRobot provides an API to list all monitors. Run:
curl -X POST "https://api.uptimerobot.com/v2/getMonitors" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "api_key=YOUR_API_KEY&format=json&logs=0" | jq '.monitors[] | {friendly_name, url, type, interval}'Or use the UptimeRobot dashboard: go to My Monitors, export the list, and note:
- The full URL for each monitor (e.g.
https://example.com/health) - Monitor type (HTTP, keyword, ping)
- Check interval in seconds
- Which alert contacts are assigned
Step 2: Add your domains to DomainCare
DomainCare is domain-centric rather than URL-centric. Instead of adding individual monitor URLs, you add a domain and DomainCare enables the appropriate checks automatically.
Domain-first monitoring
A single domain entry in DomainCare replaces multiple UptimeRobot monitors. example.com becomes one entry that tracks uptime, SSL, DNS changes, and email deliverability health together.
For each unique domain in your UptimeRobot list:
- Sign into DomainCare (or start a free trial).
- Click Add domain.
- Enter the domain name (without
https://— justexample.com). - DomainCare reads your DNS and pre-fills suggested checks. Review and enable the ones you want.
If you have monitors pointing to multiple paths on the same domain (e.g. https://example.com/, https://example.com/api/ping), add the domain once and then add a separate HTTP check for each path under Checks > Add check.
See Add your first domain for a full walkthrough.
Step 3: Map UptimeRobot monitor types to DomainCare checks
| UptimeRobot type | DomainCare equivalent |
|---|---|
| HTTP(S) | Uptime check |
| Keyword | Uptime check with expected-content option |
| Ping | Uptime check (ICMP ping) |
| Port | Port check |
| DNS | DNS record monitor |
| Heartbeat | Not yet available in DomainCare |
Most UptimeRobot monitors map cleanly to DomainCare uptime checks. The key difference: DomainCare also runs SSL, DNS, and email deliverability checks continuously — checks you'd need separate UptimeRobot monitors (or external tools) to replicate.
Keyword monitors
UptimeRobot keyword monitors check that a specific string appears in the response body. DomainCare's uptime check validates HTTP status codes. If you rely on keyword matching, configure an expected-status check and use your application's health endpoint instead.
Step 4: Set up notification channels
DomainCare supports email, Slack, webhooks, PagerDuty, and others. UptimeRobot contacts map as follows:
| UptimeRobot alert contact | DomainCare channel |
|---|---|
| Email channel | |
| Slack | Slack OAuth integration |
| Webhook | Webhook channel (POST with JSON payload) |
| PagerDuty | Webhook channel (PagerDuty Events API v2) |
| SMS | Not yet available in DomainCare |
To add channels:
- Go to Settings > Notifications.
- Click Add channel and complete the setup for each type.
- Test each channel with Send test notification.
Then open each domain's settings and assign the notification policy — which events trigger alerts, on which channels, after how many consecutive failures.
See Notification channels for setup details.
Step 5: Replicate maintenance windows
UptimeRobot maintenance windows suppress alerts during scheduled downtime. In DomainCare, you pause individual checks or mute notifications for a domain during maintenance:
- Open the domain.
- Click the ... menu next to any check.
- Select Pause check with a duration.
DomainCare supports per-domain maintenance windows with start/end datetimes. Named, reusable schedules are planned for a future release.
Step 6: Validate and cut over
Before cancelling UptimeRobot:
- Let DomainCare run for at least 24 hours and confirm check results look correct.
- Trigger a test alert by temporarily taking down a staging endpoint (or using DomainCare's test notification feature).
- Confirm you receive the alert via each configured channel.
Once you're confident, cancel UptimeRobot at My Account > Subscription. UptimeRobot retains account data for 30 days after cancellation if you need to reference old incident history.
Common questions
Does DomainCare have a free trial? Yes — a 30-day free trial covers 1 domain with full feature access, no credit card required. See pricing for paid plan details.
Can I import UptimeRobot monitors automatically? Not currently. Adding domains manually takes roughly 2 minutes per domain for a typical setup.
What about teams and user management? DomainCare accounts are currently single-user. Team and multi-user support is on the roadmap.
Will check history transfer? No — DomainCare starts fresh from the day you add a domain. UptimeRobot history stays in your UptimeRobot account until it's deleted.
Switch to domain-centric monitoring
Get uptime, SSL, DNS, and email auth health in one place. Add your first domain in two minutes.
Start free trial