[{"data":1,"prerenderedAt":347},["ShallowReactive",2],{"\u002Fblog\u002Fswitching-uptime-monitoring-providers":3},{"id":4,"title":5,"author":6,"body":8,"category":303,"date":304,"description":305,"extension":306,"faq":307,"howTo":323,"image":339,"lastUpdated":304,"meta":340,"navigation":341,"path":342,"readingTime":343,"seo":344,"stem":345,"__hash__":346},"blog\u002Fblog\u002Fswitching-uptime-monitoring-providers.md","Switching Uptime Monitoring Providers Without Losing Coverage",{"name":7},"Theo Cummings",{"type":9,"value":10,"toc":290},"minimark",[11,15,18,85,88,93,96,126,129,133,136,143,155,163,177,181,184,187,212,217,224,231,235,243,247,250,270,273,277,280],[12,13,14],"p",{},"The riskiest moment in uptime monitoring isn't an outage - it's the week you switch providers. Cancel the old tool too early and you're flying blind; forget one cron job and your dead-man's switch is pinging a dead account. This is the vendor-neutral playbook for doing it without a coverage gap.",[12,16,17],{},"If you already know where you're coming from, here are the one-click paths into Vantaj:",[19,20,21,40,51,62,73],"ul",{},[22,23,24,28,29,34,35,39],"li",{},[25,26,27],"strong",{},"UptimeRobot"," → ",[30,31,33],"a",{"href":32},"\u002Fblog\u002Fmigrate-from-uptimerobot-in-60-seconds","migrate in 60 seconds"," (",[30,36,38],{"href":37},"\u002Fdocs\u002Fimport-uptimerobot","docs",")",[22,41,42,28,45,34,48,39],{},[25,43,44],{},"Pingdom",[30,46,33],{"href":47},"\u002Fblog\u002Fmigrate-from-pingdom-in-60-seconds",[30,49,38],{"href":50},"\u002Fdocs\u002Fimport-pingdom",[22,52,53,28,56,34,59,39],{},[25,54,55],{},"StatusCake",[30,57,33],{"href":58},"\u002Fblog\u002Fmigrate-from-statuscake-in-60-seconds",[30,60,38],{"href":61},"\u002Fdocs\u002Fimport-statuscake",[22,63,64,28,67,34,70,39],{},[25,65,66],{},"Better Stack",[30,68,33],{"href":69},"\u002Fblog\u002Fmigrate-from-better-stack-in-60-seconds",[30,71,38],{"href":72},"\u002Fdocs\u002Fimport-betterstack",[22,74,75,28,78,34,82,39],{},[25,76,77],{},"Anything else",[30,79,81],{"href":80},"\u002Fblog\u002Fbulk-import-monitors-csv","bulk import from CSV",[30,83,38],{"href":84},"\u002Fdocs\u002Fimport-csv",[12,86,87],{},"The rest of this post is the process around the import - because the import is the easy part.",[89,90,92],"h2",{"id":91},"step-1-inventory-what-you-actually-have","Step 1: Inventory what you actually have",[12,94,95],{},"Before touching the new tool, list what the old one is doing. Not what you think it's doing - what it's configured to do:",[19,97,98,104,114,120],{},[22,99,100,103],{},[25,101,102],{},"Every monitor",", including the paused ones. Paused monitors are usually paused for a reason someone has forgotten; carry them over paused rather than deciding mid-migration.",[22,105,106,109,110,113],{},[25,107,108],{},"Every heartbeat",", and - critically - ",[25,111,112],{},"every cron job, CI pipeline, and backup script that pings one",". The monitors are in the dashboard; the pingers are scattered across crontabs and CI configs. Find them now, not after the cutover.",[22,115,116,119],{},[25,117,118],{},"Every alert channel"," and who's behind it: Slack channels, PagerDuty services, email lists, webhooks feeding other systems.",[22,121,122,125],{},[25,123,124],{},"Status pages"," and anything embedding them - custom domains, badges in READMEs, iframes in internal dashboards.",[12,127,128],{},"A spreadsheet is fine. The point is that step 4 has a checklist to verify against.",[89,130,132],{"id":131},"step-2-import-into-the-new-tool","Step 2: Import into the new tool",[12,134,135],{},"With a one-click importer this is the sixty-second part: a read-only API key or token, a fetch, a review screen, an import. Monitor types, intervals, keyword assertions, and paused states translate automatically; the provider posts linked above document exactly what carries over from each source, and the honest list of what doesn't.",[12,137,138,139,142],{},"Coming from a tool without an importer, the ",[30,140,141],{"href":80},"CSV route"," gets you there with four columns.",[12,144,145,146,149,150,154],{},"Then do the one piece of setup no importer can do: ",[25,147,148],{},"alert channels",". They don't transfer between providers - the integrations are structurally different - but in Vantaj you configure them once under ",[30,151,153],{"href":152},"\u002Fdocs\u002Falerts","Alerts & Notifications"," and they apply to every monitor, imported or not. Budget five minutes, not an afternoon.",[12,156,157,158,162],{},"Two things you should expect ",[159,160,161],"em",{},"not"," to migrate, from any provider to any provider:",[19,164,165,171],{},[22,166,167,170],{},[25,168,169],{},"Uptime history."," No tool exposes it in an importable form. Your new graphs start at import time - which is exactly why the next step exists.",[22,172,173,176],{},[25,174,175],{},"Alert integrations",", as above. Set up once, verify once.",[89,178,180],{"id":179},"step-3-run-both-in-parallel-the-step-everyone-skips","Step 3: Run both in parallel (the step everyone skips)",[12,182,183],{},"Keep the old provider alive for a few days after the import. This is the cheapest insurance in the entire migration, and it's what makes the \"do I lose history?\" answer tolerable - there's no moment where nothing is watching.",[12,185,186],{},"During the parallel window, verify three things:",[188,189,190,196,206],"ol",{},[22,191,192,195],{},[25,193,194],{},"Both tools agree on reality."," Same monitors up, same monitors down. Disagreements usually mean an import edge case - a wrong port, a keyword assertion inverted - and they're trivial to fix while you still have the old tool as a reference.",[22,197,198,201,202,205],{},[25,199,200],{},"Alerts reach humans."," Trip a test alert (pause a monitor's target, or use a deliberately-failing check) and confirm it lands in the right Slack channel or pager rotation from the ",[159,203,204],{},"new"," tool.",[22,207,208,211],{},[25,209,210],{},"Heartbeats are checking in on their new URLs."," This is gotcha number one, and it deserves its own section.",[213,214,216],"h3",{"id":215},"the-heartbeat-url-cutover","The heartbeat URL cutover",[12,218,219,220,223],{},"Imported heartbeat monitors get ",[25,221,222],{},"new ping URLs"," in the new tool. Nothing updates your cron jobs for you - until you edit them, they keep pinging the old provider, the old tool reports health, and the new tool reports silence.",[12,225,226,227,230],{},"The safe sequence: update every pinger from your step-1 inventory, then run both providers through ",[25,228,229],{},"at least one full cycle of your longest schedule",". A daily backup heartbeat needs a day; a weekly report job needs a week. Only when every heartbeat has checked in on the new URL is the dead-man's-switch coverage actually transferred.",[213,232,234],{"id":233},"the-status-page-cutover","The status page cutover",[12,236,237,238,242],{},"Set up the new ",[30,239,241],{"href":240},"\u002Fdocs\u002Fstatus-pages","status page"," while both tools run, confirm it reflects the imported monitors, then move the URL your users know - repoint the custom domain, update the badge embeds - before the old page goes away. Done in this order, subscribers never see a dead page.",[89,244,246],{"id":245},"step-4-cut-over-alerts-then-decommission","Step 4: Cut over alerts, then decommission",[12,248,249],{},"Once the parallel window has been quiet - or, better, has caught one real incident that both tools saw identically - flip the order of authority:",[188,251,252,258,264],{},[22,253,254,257],{},[25,255,256],{},"Silence the old tool's alerts"," (don't delete anything yet). The new tool is now the one that pages you.",[22,259,260,263],{},[25,261,262],{},"Run one more alert cycle"," with the old tool muted. If nothing surprises you, the migration is functionally done.",[22,265,266,269],{},[25,267,268],{},"Decommission",": cancel the old subscription, revoke the API token you used for the import, and delete the old pingers' credentials from anywhere they lived. If the old tool has a free tier, keeping the account as a read-only archive of your historical uptime costs nothing.",[12,271,272],{},"Work through your step-1 inventory line by line - every monitor accounted for, every pinger updated, every channel firing, every embed repointed. That checklist is the difference between \"we switched\" and \"we think we switched.\"",[89,274,276],{"id":275},"the-short-version","The short version",[12,278,279],{},"Inventory → import → parallel → cut over → decommission. The import takes a minute; the discipline around it takes a few days of mostly waiting. The two places migrations actually fail are the parallel window people skip and the heartbeat URLs people forget - give those two their due and the switch is boring, which is the goal.",[12,281,282,283,289],{},"Ready to run one? ",[30,284,288],{"href":285,"rel":286},"https:\u002F\u002Fapp.vantaj.co\u002Fregister",[287],"nofollow","Create a free Vantaj account"," - 20 monitors free, no credit card - pick your import path above, and keep the old tool running until the new one has proven itself.",{"title":291,"searchDepth":292,"depth":292,"links":293},"",2,[294,295,296,301,302],{"id":91,"depth":292,"text":92},{"id":131,"depth":292,"text":132},{"id":179,"depth":292,"text":180,"children":297},[298,300],{"id":215,"depth":299,"text":216},3,{"id":233,"depth":299,"text":234},{"id":245,"depth":292,"text":246},{"id":275,"depth":292,"text":276},"tutorials","2026-07-05","A vendor-neutral playbook for migrating uptime monitoring safely: inventory, import, run in parallel, cut over alerts, decommission - plus one-click migration paths from UptimeRobot, Pingdom, StatusCake, Better Stack, and CSV.","md",[308,311,314,317,320],{"q":309,"a":310},"How long does a monitoring migration actually take?","The import itself takes about a minute with a one-click importer or a CSV. The full migration - including a parallel-running window and alert cutover - is realistically two to five days, most of which is waiting to confirm the new tool behaves before you cancel the old one.",{"q":312,"a":313},"Do I lose my uptime history when I switch?","Yes. No provider exposes history in a form another tool can import, so your history in the new tool starts at import time. If unbroken records matter, keep the old account alive as a read-only archive and run both in parallel through the transition.",{"q":315,"a":316},"Will my status page break during the migration?","Not if you sequence it: set up the new status page first, confirm it reflects the imported monitors, then update the URL your users know - or point your custom domain at the new page - before shutting the old one down.",{"q":318,"a":319},"Do alert integrations transfer between providers?","No - notification channels work too differently across tools to map automatically. The good news: in Vantaj you set up channels once (Slack, PagerDuty, Telegram, webhooks, email) and they apply to every monitor, so this is a five-minute job, not a per-monitor one.",{"q":321,"a":322},"What's the biggest thing that goes wrong in monitoring migrations?","Heartbeat URLs. Imported heartbeat monitors get new ping URLs, but your cron jobs keep pinging the old provider until you update them - so the new tool sees silence and the old tool sees health. Update every job and run both in parallel for at least one full schedule cycle.",{"name":324,"description":325,"steps":326},"How to switch uptime monitoring providers without losing coverage","Migrate your monitors to a new provider safely by inventorying, importing, running both tools in parallel, and cutting over alerts deliberately.",[327,330,333,336],{"name":328,"text":329},"Inventory what you have","List every monitor, heartbeat, alert channel, and status page in the old tool - including the paused ones and the cron jobs pinging heartbeat URLs.",{"name":331,"text":332},"Import into the new tool","Use a one-click importer (UptimeRobot, Pingdom, StatusCake, Better Stack) or a CSV upload to recreate your monitors in Vantaj, then set up alert channels once.",{"name":334,"text":335},"Run both providers in parallel","Keep the old tool alive for a few days. Confirm the new tool sees the same reality - same up\u002Fdown states, alerts firing to the right channels, heartbeats checking in on their new URLs.",{"name":337,"text":338},"Cut over and decommission","Point status pages and dashboards at the new tool, silence the old tool's alerts, and cancel it once you've gone a full alert cycle without surprises.",null,{},true,"\u002Fblog\u002Fswitching-uptime-monitoring-providers",7,{"title":5,"description":305},"blog\u002Fswitching-uptime-monitoring-providers","jUYq-uxRkGaKjrAopA6mZZLjUoOShXNTgNhdK1l01-c",1783178927710]