[{"data":1,"prerenderedAt":637},["ShallowReactive",2],{"\u002Fblog\u002Fstatuspage-io-migration-guide":3},{"id":4,"title":5,"author":6,"body":8,"category":626,"date":627,"description":628,"extension":629,"image":630,"lastUpdated":630,"meta":631,"navigation":74,"path":632,"readingTime":633,"seo":634,"stem":635,"__hash__":636},"blog\u002Fblog\u002Fstatuspage-io-migration-guide.md","How to Migrate from Atlassian Statuspage in 30 Minutes",{"name":7},"Vantaj Team",{"type":9,"value":10,"toc":603},"minimark",[11,15,18,21,26,29,36,42,48,54,58,61,107,110,114,143,146,152,156,159,173,176,180,183,200,203,207,210,215,223,228,236,241,246,249,253,256,270,273,277,280,285,308,311,317,321,329,343,346,352,356,359,367,370,373,377,380,397,400,404,407,421,424,428,519,522,526,531,551,555,575,579,585,591,597],[12,13,14],"p",{},"Atlassian acquired StatusPage.io in 2016. For the first few years, pricing stayed reasonable and the product kept its independent identity. By 2024, that changed: Atlassian folded Statuspage into their broader pricing model, eliminated the free tier, and pushed the entry point up to $29\u002Fmonth for features that competitors offer for free.",[12,16,17],{},"Teams that built their incident communication workflow on Statuspage now face a choice: absorb the price increase and accept the Atlassian dependency, or migrate to a tool that works independently.",[12,19,20],{},"This guide covers what to export, how to recreate your setup, and how to cut over without losing your subscriber list.",[22,23,25],"h2",{"id":24},"why-teams-migrate-from-statuspage","Why Teams Migrate from Statuspage",[12,27,28],{},"The pricing change is the most common trigger, but it's not the only one.",[12,30,31,35],{},[32,33,34],"strong",{},"Statuspage doesn't monitor anything."," It's a communication tool. It shows whatever status you manually set (or push via API). If your site goes down, Statuspage shows \"Operational\" until someone logs in and changes it. You still need a separate monitoring tool to detect outages — and then you need to wire them together.",[12,37,38,41],{},[32,39,40],{},"Two tools mean two subscriptions."," A team paying $29\u002Fmonth for Statuspage plus $X\u002Fmonth for their monitoring tool is paying for two separate products to do what one integrated platform can do.",[12,43,44,47],{},[32,45,46],{},"Atlassian lock-in gets expensive."," Teams that adopted Statuspage as a standalone product now find themselves in Atlassian's ecosystem pricing model, where costs scale with users and seat counts.",[12,49,50,53],{},[32,51,52],{},"Subscribers don't transfer automatically."," If you let your Statuspage subscription lapse without migrating subscribers, you lose the contact list you've built over months or years. The time to migrate is before cancellation, not after.",[22,55,57],{"id":56},"before-you-start-what-to-inventory","Before You Start: What to Inventory",[12,59,60],{},"Run through this checklist before touching any settings:",[62,63,66,77,83,89,95,101],"ul",{"className":64},[65],"contains-task-list",[67,68,71,76],"li",{"className":69},[70],"task-list-item",[72,73],"input",{"disabled":74,"type":75},true,"checkbox"," Export your subscriber list (email + SMS)",[67,78,80,82],{"className":79},[70],[72,81],{"disabled":74,"type":75}," Document all your components (names, descriptions, groupings)",[67,84,86,88],{"className":85},[70],[72,87],{"disabled":74,"type":75}," Screenshot or export your incident history (for internal records)",[67,90,92,94],{"className":91},[70],[72,93],{"disabled":74,"type":75}," Note your custom domain (if configured)",[67,96,98,100],{"className":97},[70],[72,99],{"disabled":74,"type":75}," Note any current API integrations (Datadog, PagerDuty, etc.)",[67,102,104,106],{"className":103},[70],[72,105],{"disabled":74,"type":75}," Identify who is subscribed to which components",[12,108,109],{},"The subscriber list is the most critical export. Everything else can be recreated. Subscribers must be exported before you cancel.",[22,111,113],{"id":112},"step-1-export-your-subscriber-list","Step 1: Export Your Subscriber List",[115,116,117,127,133,140],"ol",{},[67,118,119,120],{},"Log in to Statuspage at ",[121,122,126],"a",{"href":123,"rel":124},"https:\u002F\u002Fmanage.statuspage.io",[125],"nofollow","manage.statuspage.io",[67,128,129,130],{},"Navigate to ",[32,131,132],{},"Subscribers",[67,134,135,136,139],{},"Click ",[32,137,138],{},"Export"," in the top right",[67,141,142],{},"Download the CSV — it contains email addresses, phone numbers (for SMS subscribers), and component subscriptions",[12,144,145],{},"Save this file somewhere accessible. You'll need it during import on your new platform.",[12,147,148,151],{},[32,149,150],{},"Note on SMS subscribers:"," Not all platforms support SMS subscriber import. If SMS notifications are important to your audience, verify your target platform supports them before starting the migration.",[22,153,155],{"id":154},"step-2-document-your-components","Step 2: Document Your Components",[12,157,158],{},"Statuspage organizes services into components and component groups. Before recreating them elsewhere, document:",[62,160,161,164,167,170],{},[67,162,163],{},"Component names and descriptions",[67,165,166],{},"Component groupings (which components appear together)",[67,168,169],{},"Current status of each component",[67,171,172],{},"Any automations that update component status",[12,174,175],{},"A simple spreadsheet works. You're building the blueprint you'll use to recreate the structure on your new platform.",[22,177,179],{"id":178},"step-3-archive-your-incident-history","Step 3: Archive Your Incident History",[12,181,182],{},"Incident history doesn't transfer between platforms. Export it for your own records:",[115,184,185,191,197],{},[67,186,187,188],{},"In Statuspage, go to ",[32,189,190],{},"Incidents",[67,192,193,194,196],{},"Use the ",[32,195,138],{}," function (or manually document recent major incidents)",[67,198,199],{},"Save the export — this becomes your incident history archive",[12,201,202],{},"Your new status page will start with a clean history. Some teams post a brief note explaining the migration to subscribers so the blank history doesn't look alarming.",[22,204,206],{"id":205},"step-4-choose-your-new-platform","Step 4: Choose Your New Platform",[12,208,209],{},"The main categories:",[12,211,212],{},[32,213,214],{},"Standalone status page tools",[62,216,217,220],{},[67,218,219],{},"Statuspage.io (what you're leaving)",[67,221,222],{},"Instatus — starts at $20\u002Fmonth, focused on status pages",[12,224,225],{},[32,226,227],{},"Monitoring + status pages combined",[62,229,230,233],{},[67,231,232],{},"Vantaj — uptime monitoring, SSL, heartbeats, and status pages in one product. Free tier includes a public status page. When a monitor goes down, the status page updates automatically.",[67,234,235],{},"Better Stack — combines monitoring, log management, and status pages",[12,237,238],{},[32,239,240],{},"Self-hosted",[62,242,243],{},[67,244,245],{},"Cachet — open-source, requires a server you maintain",[12,247,248],{},"If the reason you're migrating is cost and Atlassian lock-in, moving to another standalone status page tool replicates the problem. A combined monitoring + status page platform eliminates the \"two tools, two bills\" situation entirely.",[22,250,252],{"id":251},"step-5-recreate-your-components","Step 5: Recreate Your Components",[12,254,255],{},"On your new platform:",[115,257,258,261,264,267],{},[67,259,260],{},"Create the same component structure you documented in Step 2",[67,262,263],{},"Match the names and descriptions your subscribers recognize",[67,265,266],{},"Set up component groups if your platform supports them",[67,268,269],{},"Leave all components at \"Operational\" initially",[12,271,272],{},"Take your time here. Subscribers see component names in notifications. Consistency with what they subscribed to reduces confusion.",[22,274,276],{"id":275},"step-6-import-your-subscribers","Step 6: Import Your Subscribers",[12,278,279],{},"The import process varies by platform.",[12,281,282],{},[32,283,284],{},"On Vantaj:",[115,286,287,290,299,302,305],{},[67,288,289],{},"Go to your Status Page settings",[67,291,292,293,295,296],{},"Select ",[32,294,132],{}," > ",[32,297,298],{},"Import",[67,300,301],{},"Upload the CSV exported from Statuspage",[67,303,304],{},"Map the CSV columns to the correct fields (email, phone, component subscriptions)",[67,306,307],{},"Confirm the import",[12,309,310],{},"Most platforms send a confirmation or re-confirmation email to imported subscribers. This is normal — imported subscribers haven't explicitly opted into the new platform's notification system, so a re-confirmation protects you from deliverability issues.",[12,312,313,316],{},[32,314,315],{},"Expect some subscriber loss."," Some contacts on old lists are no longer active. A re-confirmation flow typically retains 60-80% of the imported list. This is expected and preferable to silently importing stale addresses.",[22,318,320],{"id":319},"step-7-configure-your-custom-domain","Step 7: Configure Your Custom Domain",[12,322,323,324,328],{},"If you were using a custom domain (e.g., ",[325,326,327],"code",{},"status.yourcompany.com","), you need to point it at your new platform.",[115,330,331,334,337,340],{},[67,332,333],{},"Log in to your DNS provider",[67,335,336],{},"Find the CNAME record pointing to Statuspage's infrastructure",[67,338,339],{},"Update it to point to your new platform's CNAME target",[67,341,342],{},"Allow DNS propagation (typically 5-30 minutes with a low TTL)",[12,344,345],{},"Most platforms provide the exact DNS record you need in their domain configuration settings. During the propagation window, visitors may see either the old or the new status page depending on which DNS server they hit — this is normal.",[12,347,348,351],{},[32,349,350],{},"Lower your TTL before migrating."," If you set your TTL to 300 seconds (5 minutes) at least 24 hours before the DNS change, propagation will be much faster when you make the switch.",[22,353,355],{"id":354},"step-8-wire-up-monitoring-automations-if-applicable","Step 8: Wire Up Monitoring Automations (if applicable)",[12,357,358],{},"If you had Statuspage connected to a monitoring tool via API or integration:",[62,360,361,364],{},[67,362,363],{},"On Statuspage + Datadog: you sent webhook updates to change component status when monitors fired",[67,365,366],{},"On Statuspage + PagerDuty: similar webhook setup",[12,368,369],{},"On a combined monitoring + status page platform, this automation is built in. Vantaj, for example, connects the monitor directly to the status page component — when a monitor goes down, the component status changes automatically without any webhook configuration.",[12,371,372],{},"If you're moving to a standalone status page tool, you'll need to rebuild the API integration with your monitoring tool.",[22,374,376],{"id":375},"step-9-test-before-going-live","Step 9: Test Before Going Live",[12,378,379],{},"Before sending any communication to subscribers:",[115,381,382,385,388,391,394],{},[67,383,384],{},"Trigger a test incident manually",[67,386,387],{},"Verify the incident appears on the status page",[67,389,390],{},"Check that notifications send correctly (email + SMS)",[67,392,393],{},"Confirm the incident resolves and recovery notifications send",[67,395,396],{},"View the status page as an unauthenticated visitor",[12,398,399],{},"The test incident confirms your notification pipeline is working. Don't skip this step — finding a broken email template during a real incident is a bad time.",[22,401,403],{"id":402},"step-10-notify-your-subscribers","Step 10: Notify Your Subscribers",[12,405,406],{},"Once everything is live and tested, send a brief subscriber notification:",[408,409,410],"blockquote",{},[12,411,412,413,417,418,420],{},"\"We've moved our status page to ",[414,415,416],"span",{},"new URL",". Your subscription transfers automatically — you'll continue receiving incident notifications without any action required. Update your bookmarks: ",[414,419,416],{},"\"",[12,422,423],{},"If your old Statuspage URL was public and linked from your documentation or website, update those links to the new URL.",[22,425,427],{"id":426},"timeline","Timeline",[429,430,431,444],"table",{},[432,433,434],"thead",{},[435,436,437,441],"tr",{},[438,439,440],"th",{},"Step",[438,442,443],{},"Time required",[445,446,447,456,464,471,478,485,492,500,507],"tbody",{},[435,448,449,453],{},[450,451,452],"td",{},"Export subscriber list",[450,454,455],{},"5 min",[435,457,458,461],{},[450,459,460],{},"Document components",[450,462,463],{},"10 min",[435,465,466,469],{},[450,467,468],{},"Archive incident history",[450,470,455],{},[435,472,473,476],{},[450,474,475],{},"Set up new platform",[450,477,455],{},[435,479,480,483],{},[450,481,482],{},"Recreate components",[450,484,455],{},[435,486,487,490],{},[450,488,489],{},"Import subscribers",[450,491,455],{},[435,493,494,497],{},[450,495,496],{},"Configure custom domain",[450,498,499],{},"5 min (+ propagation)",[435,501,502,505],{},[450,503,504],{},"Test",[450,506,455],{},[435,508,509,514],{},[450,510,511],{},[32,512,513],{},"Total",[450,515,516],{},[32,517,518],{},"~45 min",[12,520,521],{},"The DNS propagation window sits outside your control, but everything else completes in under an hour.",[22,523,525],{"id":524},"what-you-lose-vs-what-you-gain","What You Lose vs. What You Gain",[527,528,530],"h3",{"id":529},"what-you-lose","What you lose",[62,532,533,539,545],{},[67,534,535,538],{},[32,536,537],{},"Incident history"," — new platform starts fresh (archive the old history before cancelling)",[67,540,541,544],{},[32,542,543],{},"Some subscribers"," — re-confirmation flows lose 20-40% of stale addresses (better to lose them than spam them)",[67,546,547,550],{},[32,548,549],{},"Atlassian ecosystem integration"," — if you use Jira or Confluence integrations tied to Statuspage, you'll need to rebuild those",[527,552,554],{"id":553},"what-you-gain","What you gain",[62,556,557,563,569],{},[67,558,559,562],{},[32,560,561],{},"Lower cost"," — most alternatives include status pages at a lower price point or for free",[67,564,565,568],{},[32,566,567],{},"Integrated monitoring"," — on combined platforms, status updates happen automatically instead of manually",[67,570,571,574],{},[32,572,573],{},"Independence from Atlassian pricing"," — no exposure to future price increases",[22,576,578],{"id":577},"common-mistakes","Common Mistakes",[12,580,581,584],{},[32,582,583],{},"Cancelling before exporting subscribers."," Once your subscription ends, the export function may be unavailable. Export first, cancel second.",[12,586,587,590],{},[32,588,589],{},"Importing without testing re-confirmation."," Some platforms send re-confirmation emails during import. Test with a small batch of internal email addresses before importing your full list.",[12,592,593,596],{},[32,594,595],{},"Forgetting to update website links."," Your documentation, help center, incident response runbooks, and email signatures may all link to your Statuspage URL. A broken status page link during an incident looks worse than no status page at all.",[12,598,599,602],{},[32,600,601],{},"Moving to another standalone tool."," If the problem is cost, move to a platform that includes monitoring. Otherwise, you're trading one subscription for two.",{"title":604,"searchDepth":605,"depth":605,"links":606},"",2,[607,608,609,610,611,612,613,614,615,616,617,618,619,620,625],{"id":24,"depth":605,"text":25},{"id":56,"depth":605,"text":57},{"id":112,"depth":605,"text":113},{"id":154,"depth":605,"text":155},{"id":178,"depth":605,"text":179},{"id":205,"depth":605,"text":206},{"id":251,"depth":605,"text":252},{"id":275,"depth":605,"text":276},{"id":319,"depth":605,"text":320},{"id":354,"depth":605,"text":355},{"id":375,"depth":605,"text":376},{"id":402,"depth":605,"text":403},{"id":426,"depth":605,"text":427},{"id":524,"depth":605,"text":525,"children":621},[622,624],{"id":529,"depth":623,"text":530},3,{"id":553,"depth":623,"text":554},{"id":577,"depth":605,"text":578},"tutorials","2026-06-26","Atlassian raised Statuspage prices and killed the free tier. This step-by-step guide walks you through exporting subscribers, recreating components, setting a custom domain, and going live on a new platform — without losing your audience.","md",null,{},"\u002Fblog\u002Fstatuspage-io-migration-guide",10,{"title":5,"description":628},"blog\u002Fstatuspage-io-migration-guide","Ga7o3VGMQCCxQQndWqidert5AxiLN1V_sdmRegz3-ZU",1782496068348]