[{"data":1,"prerenderedAt":323},["ShallowReactive",2],{"\u002Fblog\u002Fmigrate-from-uptimerobot-in-60-seconds":3},{"id":4,"title":5,"author":6,"body":8,"category":279,"date":280,"description":281,"extension":282,"faq":283,"howTo":299,"image":315,"lastUpdated":280,"meta":316,"navigation":317,"path":318,"readingTime":319,"seo":320,"stem":321,"__hash__":322},"blog\u002Fblog\u002Fmigrate-from-uptimerobot-in-60-seconds.md","Migrating Your Monitors from UptimeRobot in 60 Seconds",{"name":7},"Theo Cummings",{"type":9,"value":10,"toc":269},"minimark",[11,15,23,26,31,46,49,65,69,83,86,90,93,151,154,194,201,205,208,214,226,230,237,241,248,255],[12,13,14],"p",{},"Switching uptime monitoring providers usually fails at the same hurdle: getting your monitors out. UptimeRobot has no configuration export - the CSV button covers logs and incidents, not your monitor list. So most people facing a migration open two browser tabs and start re-typing URLs.",[12,16,17,18,22],{},"You don't have to. Vantaj imports your entire UptimeRobot account with a single ",[19,20,21],"strong",{},"read-only API key"," - every monitor type, including heartbeats - in about the time it takes to read this paragraph. Here's the whole flow:",[24,25],"import-demo",{},[27,28,30],"h2",{"id":29},"step-1-create-a-read-only-api-key-20-seconds","Step 1: Create a read-only API key (20 seconds)",[12,32,33,34,37,38,41,42,45],{},"In UptimeRobot, open ",[19,35,36],{},"Integrations & API"," from the dashboard sidebar. Under ",[19,39,40],{},"API",", create a ",[19,43,44],{},"Read-Only API Key",".",[12,47,48],{},"Two things worth knowing:",[50,51,52,59],"ul",{},[53,54,55,58],"li",{},[19,56,57],{},"It's available on the free plan."," UptimeRobot includes API access on every tier, so there's no paywall between you and your own data.",[53,60,61,64],{},[19,62,63],{},"Read-only means read-only."," The key can list your monitors but can't modify or delete anything. Your UptimeRobot account is untouched by the migration - you can keep it running in parallel as long as you like.",[27,66,68],{"id":67},"step-2-paste-it-into-vantaj-10-seconds","Step 2: Paste it into Vantaj (10 seconds)",[12,70,71,72,75,76,79,80,45],{},"In Vantaj, go to ",[19,73,74],{},"Settings → Import Monitors"," and choose ",[19,77,78],{},"Quick import from UptimeRobot",". Paste the key and click ",[19,81,82],{},"Fetch monitors",[12,84,85],{},"Vantaj calls the UptimeRobot API on your behalf, pages through your full monitor list, and shows everything it found. The key is used for that one request and never stored.",[27,87,89],{"id":88},"step-3-review-and-import-30-seconds","Step 3: Review and import (30 seconds)",[12,91,92],{},"Every importable monitor is pre-selected. The preview shows what each one becomes:",[94,95,96,109],"table",{},[97,98,99],"thead",{},[100,101,102,106],"tr",{},[103,104,105],"th",{},"UptimeRobot",[103,107,108],{},"Becomes in Vantaj",[110,111,112,120,128,136,144],"tbody",{},[100,113,114,118],{},[115,116,117],"td",{},"HTTP(s) monitor",[115,119,117],{},[100,121,122,125],{},[115,123,124],{},"Keyword monitor",[115,126,127],{},"HTTP(s) monitor with a response assertion",[100,129,130,133],{},[115,131,132],{},"Ping monitor",[115,134,135],{},"Ping (ICMP) monitor",[100,137,138,141],{},[115,139,140],{},"Port monitor",[115,142,143],{},"Port (TCP) monitor",[100,145,146,149],{},[115,147,148],{},"Heartbeat",[115,150,148],{},[12,152,153],{},"The details come over too - and the edge cases are handled the way you'd hope:",[50,155,156,171,177,183,188],{},[53,157,158,161,162,166,167,170],{},[19,159,160],{},"Keyword logic is translated correctly."," UptimeRobot's \"alert when keyword exists\" becomes Vantaj's ",[163,164,165],"em",{},"response must not contain","; \"alert when not exists\" becomes ",[163,168,169],{},"must contain",". Your error-page detection keeps working without you thinking about it.",[53,172,173,176],{},[19,174,175],{},"Check intervals are snapped"," to the nearest Vantaj interval, respecting your plan's minimum.",[53,178,179,182],{},[19,180,181],{},"HTTP basic auth credentials"," carry over.",[53,184,185],{},[19,186,187],{},"Paused monitors stay paused.",[53,189,190,193],{},[19,191,192],{},"Duplicates are caught."," Anything already monitored in Vantaj (matched by URL) is flagged and deselected, so re-running the import never creates copies.",[12,195,196,197,200],{},"Click ",[19,198,199],{},"Import",", and checks start immediately from multiple regions.",[27,202,204],{"id":203},"the-two-things-that-dont-migrate","The two things that don't migrate",[12,206,207],{},"Honesty section. Two things stay behind, for reasons outside anyone's importer:",[12,209,210,213],{},[19,211,212],{},"Historical uptime data."," UptimeRobot's API doesn't expose history in an importable form. Your Vantaj graphs start at import time. If unbroken records matter to you, keep the UptimeRobot account alive (it's free) as a read-only archive, or run both in parallel through the transition.",[12,215,216,219,220,225],{},[19,217,218],{},"Alert contacts."," Notification channels work too differently across providers to map automatically. In Vantaj you set up channels once - Slack, PagerDuty, Telegram, webhooks, email - under ",[221,222,224],"a",{"href":223},"\u002Fdocs\u002Falerts","Alerts & Notifications",", and they apply to every monitor, imported or not. For most teams this is a five-minute job.",[27,227,229],{"id":228},"one-follow-up-for-heartbeat-users","One follow-up for heartbeat users",[12,231,232,233,236],{},"Imported heartbeat monitors get a ",[19,234,235],{},"new Vantaj ping URL",". Your cron jobs are still pinging UptimeRobot until you update them - swap the URL in your crontab or CI config, and consider running both for a day so there's no gap in dead-man's-switch coverage.",[27,238,240],{"id":239},"why-we-built-this","Why we built this",[12,242,243,244,247],{},"Nobody in the uptime monitoring space offers a real self-serve importer. The competition's answer to \"how do I migrate?\" ranges from \"email us your monitor list\" to \"here's our Terraform provider.\" We think switching tools should take a minute, not an afternoon - and that the same courtesy should apply in both directions, which is why the importer asks for a ",[163,245,246],{},"read-only"," key and leaves your old account intact.",[12,249,250,251,254],{},"Migrating from Pingdom, Better Stack, StatusCake, or somewhere else? Tell us via ",[19,252,253],{},"Settings → Share Feedback"," - UptimeRobot is the first source, not the last.",[12,256,257,258,264,265,45],{},"Ready to try it? ",[221,259,263],{"href":260,"rel":261},"https:\u002F\u002Fapp.vantaj.co\u002Fregister",[262],"nofollow","Create a free Vantaj account"," - 20 monitors free, no credit card - and see the ",[221,266,268],{"href":267},"\u002Fdocs\u002Fimport-uptimerobot","full import guide in the docs",{"title":270,"searchDepth":271,"depth":271,"links":272},"",2,[273,274,275,276,277,278],{"id":29,"depth":271,"text":30},{"id":67,"depth":271,"text":68},{"id":88,"depth":271,"text":89},{"id":203,"depth":271,"text":204},{"id":228,"depth":271,"text":229},{"id":239,"depth":271,"text":240},"tutorials","2026-07-05","Vantaj imports your entire UptimeRobot account - HTTP, keyword, ping, port, and heartbeat monitors - with one read-only API key. No CSV exports, no re-typing URLs. Here's exactly how it works and what carries over.","md",[284,287,290,293,296],{"q":285,"a":286},"Does UptimeRobot let me export my monitors?","Not really. UptimeRobot's CSV export covers logs and incidents, not monitor configuration. The practical migration path is their API - which is exactly what Vantaj's importer uses, via a read-only key that can't modify anything in your account.",{"q":288,"a":289},"Is my UptimeRobot API key stored anywhere?","No. Vantaj uses the key once to read your monitor list during the import and never stores it. Using a read-only key also means it can't change or delete anything in your UptimeRobot account.",{"q":291,"a":292},"What UptimeRobot monitor types can be imported?","All five: HTTP(s), keyword, ping, port, and heartbeat monitors. Keyword monitors become HTTP monitors with a response assertion, port monitors become TCP monitors, and heartbeats become Vantaj heartbeats.",{"q":294,"a":295},"Does my uptime history come over?","No - UptimeRobot's API doesn't provide historical data in an importable form, so your Vantaj history starts at import time. Run both providers in parallel for a few days if you want overlapping coverage during the switch.",{"q":297,"a":298},"Do I need a paid UptimeRobot plan to migrate?","No. Read-only API keys are available on every UptimeRobot plan, including the free one.",{"name":300,"description":301,"steps":302},"How to migrate your monitors from UptimeRobot to Vantaj","Import every UptimeRobot monitor into Vantaj with a read-only API key in about a minute.",[303,306,309,312],{"name":304,"text":305},"Create a read-only API key in UptimeRobot","In UptimeRobot, open Integrations & API, then create a Read-Only API Key. It's available on every plan, including free.",{"name":307,"text":308},"Open the importer in Vantaj","In Vantaj, go to Settings → Import Monitors and choose Quick import from UptimeRobot.",{"name":310,"text":311},"Paste the key and fetch your monitors","Paste the read-only key and click Fetch monitors. Vantaj lists everything in your UptimeRobot account with everything importable pre-selected.",{"name":313,"text":314},"Review and import","Deselect anything you don't want, then click Import. Monitors are created and checks start immediately.",null,{},true,"\u002Fblog\u002Fmigrate-from-uptimerobot-in-60-seconds",6,{"title":5,"description":281},"blog\u002Fmigrate-from-uptimerobot-in-60-seconds","ZTuwnJbcSlHEFyV2BKoDiupScXq2C4PHpbEK0U_oW0g",1783160738445]