Import from Better Stack
Vantaj can import your Better Stack Uptime monitors - HTTP, status-code, keyword, ping, TCP, and SMTP - plus your heartbeats, with a single API token. No CSV exports, no re-typing URLs, no downtime in your coverage.
Import from Better Stack
HTTP, keyword, ping, TCP, SMTP monitors and heartbeats are all supported.
- In Better Stack, open Uptime → API tokens
- Create a Uptime API token
- Paste it below - it's used once to read your monitor list, and never stored
Before you start
You need a Better Stack Uptime API token. Tokens are scoped to a team, so pick the team whose monitors you want to import:
- Log in to Better Stack and open Uptime → API tokens
- Copy the API token for the team you're migrating (or create one)
Vantaj uses the token once to read your monitor and heartbeat lists and never stores it.
Running the import
- In Vantaj, go to Settings → Import Monitors and pick Quick import from Better Stack
- Paste your API token and click Fetch monitors
- Review the list - everything importable is selected by default. Monitors that already exist in Vantaj (matched by URL) are flagged and deselected so you don't create duplicates
- Click Import - monitors are created and checks start immediately
Monitors that were paused in Better Stack are imported as paused in Vantaj. Everything is imported into your currently active project.
What carries over
| Better Stack | Vantaj | Notes |
|---|---|---|
| HTTP / status monitor | HTTP(s) monitor | Name and URL carry over as-is |
| Expected status code | HTTP(s) monitor | The expected status code carries over |
| Keyword monitor | HTTP(s) monitor with a response assertion | Keyword becomes must contain; keyword-absence becomes must not contain |
| Ping monitor | Ping (ICMP) monitor | |
| TCP monitor | Port (TCP) monitor | The configured port carries over |
| SMTP monitor | SMTP monitor | |
| Heartbeat | Heartbeat | Period and grace carry over - see the note below about ping URLs |
| Check frequency | Check interval | Snapped to the nearest Vantaj interval, respecting your plan's minimum |
| Paused state | Paused state | Paused monitors stay paused |
What doesn't carry over
- UDP, DNS, POP, and IMAP monitors - these monitor types aren't imported.
- Playwright / transaction monitors - browser scripts have no Vantaj equivalent; consider an HTTP monitor against the same endpoint instead.
- Historical uptime data - your Vantaj history starts at import time.
- Alert integrations and escalation policies - notification setups work differently across providers. Set up your integrations once under Alerts & Notifications and they apply to all monitors, imported or not.
- Status pages - rebuild these in a few clicks under Status Pages.
Heartbeats: update your cron jobs
Imported heartbeat monitors get a new Vantaj ping URL. Your cron jobs and background workers are still pinging Better Stack until you update them:
- Open Heartbeats in Vantaj and copy each monitor's ping URL
- Replace the old Better Stack URL in your crontab, CI config, or scheduler
- Keep both providers running in parallel for a day if you want zero gaps
Plan limits
Imports count toward your plan's monitor limit, shared across uptime monitors, heartbeats, and domains. If your selection exceeds the remaining allowance, the importer tells you before anything is created - deselect a few monitors or upgrade your plan first.
Check intervals below your plan's minimum are raised to the closest allowed value (e.g. a 30-second frequency becomes 5 minutes on the free plan).
Migrating from another provider?
One-click import is also available for UptimeRobot, Pingdom, and StatusCake. Coming from somewhere else? Use the CSV import, or script it with the REST API.