Vantaj

Import from Uptime Kuma

Vantaj can import your Uptime Kuma monitors - HTTP(s), keyword, ping, TCP port, and push - from a JSON backup file. No API keys, no scripts, no re-typing URLs. The backup file is parsed entirely in your browser and is never uploaded to Vantaj's servers.

Before you start

You need an Uptime Kuma JSON backup file:

  1. In Uptime Kuma, open Settings → Backup
  2. Click Export - a .json backup downloads to your machine

Running Uptime Kuma 1.23 or later? The built-in Backup/Export feature was removed in v1.23. If you're on 1.23+, either restore your data on an older version to export from there, or use the CSV import instead.

The backup file never leaves your machine - Vantaj parses it locally in your browser, reads the monitor list, and discards the rest.

Running the import

  1. In Vantaj, go to Settings → Import Monitors and pick Uptime Kuma
  2. Upload (or drag in) your .json backup file
  3. 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
  4. Click Import - monitors are created and checks start immediately

Monitors that were paused in Uptime Kuma are imported as paused in Vantaj. Everything is imported into your currently active project.

What carries over

Uptime KumaVantajNotes
HTTP(s) monitorHTTP(s) monitorName and URL carry over as-is
Keyword monitorHTTP(s) monitor with a response assertionKuma alerts when the keyword is missing, so the keyword becomes must contain; Kuma's invert-keyword option becomes must not contain
Ping monitorPing (ICMP) monitor
TCP Port monitorPort (TCP) monitorThe configured port carries over
Push monitorHeartbeatGets a new Vantaj ping URL - see the note below about updating your cron jobs
Basic auth credentialsHTTP(s) monitor authUsername and password carry over from the backup
Check intervalCheck intervalSnapped to the nearest Vantaj interval, respecting your plan's minimum
Paused statePaused statePaused monitors stay paused

What doesn't carry over

  • DNS, Docker, MQTT, Steam, gRPC, SQL-server, real-browser, and JSON-query monitors - these monitor types aren't imported.
  • Monitor groups - children of a group import as regular monitors; the group structure is flattened.
  • "Upside-down" mode monitors - inverted up/down logic has no Vantaj equivalent, so these are skipped.
  • Notification settings - 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 and maintenance windows - rebuild these in a few clicks under Status Pages and Maintenance Windows.
  • Historical uptime data - your Vantaj history starts at import time.

Push monitors: update your cron jobs

Imported push monitors become Vantaj heartbeats with a new ping URL. Your cron jobs and background workers are still pinging your Uptime Kuma instance until you update them:

  1. Open Heartbeats in Vantaj and copy each monitor's ping URL
  2. Replace the old Kuma push URL in your crontab, CI config, or scheduler
  3. Keep both tools 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 20-second interval becomes 5 minutes on the free plan).

Migrating from another provider?

One-click import is also available for UptimeRobot, Pingdom, StatusCake, and Better Stack. Coming from somewhere else? Use the CSV import, or script it with the REST API.