What columns does the CSV need?

name, type, target, and optionally interval. The header row itself is optional. Types are http, ping, port, and smtp; targets are a URL for http, a hostname or IP for ping and smtp, and host:port for port monitors. Intervals look like 30s, 1m, or 1h and default to 5m.

What happens if some rows have errors?

Errors are reported per-row - a bad URL on line 7 doesn't block the other 40 rows. Valid rows import normally; fix the flagged ones and re-upload just those if you want.

Will re-uploading the same CSV create duplicate monitors?

No. Rows matching monitors that already exist in Vantaj are flagged as duplicates and deselected automatically, so re-running an import is safe.

What if the CSV has more monitors than my plan allows?

Plan limits are enforced before anything is created - you'll see the problem up front rather than getting a partial import that stops midway.

My old tool doesn't export CSV. Now what?

Almost everything gets you to a CSV in a few minutes: Uptime Kuma's JSON backup can be converted with a short script, most SaaS dashboards paste cleanly into a spreadsheet, and any tool with an API can be scripted into four columns. The format is deliberately minimal so any source works.

Bulk-Importing Monitors from a CSV (From Any Provider)

The one-click importers cover UptimeRobot, Pingdom, StatusCake, and Better Stack. But maybe you're coming from Site24x7, Uptime.com, Freshping, HetrixTools, or a self-hosted Uptime Kuma. Maybe your "monitoring tool" is a spreadsheet someone in ops maintains, or a Terraform file, or an infrastructure inventory that's never been monitored at all.

For all of those, there's the universal escape hatch: CSV bulk import. Every monitoring tool, spreadsheet, or inventory system can produce a CSV - and Vantaj can turn one into monitors in a single upload. The flow:

Build a CSV with four columns: name,type,target,interval (or download the in-app template)
Upload it under Settings → Import Monitors → Bulk import from CSV
Review the validated rows - errors are flagged per-row, duplicates deselected
Click Import and monitoring starts immediately

The format: four columns, one of them optional

The CSV is deliberately minimal so any source can produce it:

Column	What goes in it
`name`	Whatever you want the monitor called
`type`	`http`, `ping`, `port`, or `smtp`
`target`	A URL for `http`; a hostname or IP for `ping` and `smtp`; `host:port` for `port`
`interval`	Optional - like `30s`, `1m`, or `1h`. Defaults to `5m`

The header row is optional too. A complete, working example:

name,type,target,interval
Marketing site,http,https://acme.com,1m
API health,http,https://api.acme.com/health,30s
Office router,ping,203.0.113.7,5m
Postgres,port,db.acme.com:5432,1m
Mail server,smtp,mail.acme.com,5m

Don't want to start from a blank file? There's a downloadable template in-app: Settings → Import Monitors → Bulk import from CSV → Download template.

Upload, review, import

Upload the file and Vantaj validates every row before creating anything:

Errors are reported per-row. A malformed URL on line 7 doesn't block the other 40 rows - valid rows still import, and each bad row tells you exactly what's wrong with it.
Duplicates are auto-deselected. Rows matching monitors that already exist in Vantaj are flagged and unchecked, so re-uploading a CSV never creates copies.
Plan limits are enforced up front. If the file has more monitors than your plan allows, you find out before anything is created - not halfway through a partial import.

Click Import, and checks start immediately from multiple regions for every monitor created.

What CSV import doesn't carry

Honesty section. A four-column CSV carries monitor identity, not provider-specific configuration:

Keyword assertions, custom headers, expected status codes. These don't fit in the minimal format. Add them after import on the monitors that need them - or use a one-click importer if you're coming from a provider that has one, since those translate assertions automatically.

Heartbeats. Cron monitors need a ping URL generated per-monitor, so they can't come from a CSV. Create them in Heartbeats - it's a name and a schedule.

Alert channels and history. Same as every migration: set up Alerts & Notifications once in Vantaj and they apply to every monitor, and your uptime history starts fresh at import time.

Getting a CSV out of common tools

The export side is usually easier than people expect:

Uptime Kuma has a JSON backup (Settings → Backup). A ten-line script - or one prompt to an LLM with the JSON pasted in - converts it to the four-column format.
Most SaaS dashboards (Site24x7, Uptime.com, Freshping, HetrixTools) render their monitor list as a table you can select and paste straight into a spreadsheet, then rearrange into the four columns and export as CSV.
Anything with an API can be scripted: fetch the monitor list, print name,type,target,interval per line, done. The format is small enough that the script is trivial.
No tool at all? An infrastructure inventory, a DNS zone file, or a list of production URLs in a doc is a fine starting point - this is a chance to get things monitored that never were.

Why we built this

One-click importers are the best experience, but they'll never cover every source - there's a long tail of monitoring tools, and the longest tail of all is "a spreadsheet and good intentions." The CSV importer means no one is stuck re-typing URLs into a form, no matter where they're coming from.

Coming from a supported provider? The one-click importers carry more detail: UptimeRobot, Pingdom, StatusCake, and Better Stack.

Ready to try it? Create a free Vantaj account - 20 monitors free, no credit card - and see the full CSV import guide in the docs.