[{"data":1,"prerenderedAt":462},["ShallowReactive",2],{"\u002Fblog\u002Fopsgenie-end-of-life-migration-guide":3},{"id":4,"title":5,"author":6,"body":8,"category":449,"date":450,"description":451,"extension":452,"image":453,"lastUpdated":454,"meta":455,"navigation":456,"path":457,"readingTime":458,"seo":459,"stem":460,"__hash__":461},"blog\u002Fblog\u002Fopsgenie-end-of-life-migration-guide.md","OpsGenie End of Life - Migration Guide for Monitoring Teams",{"name":7},"Vantaj Team",{"type":9,"value":10,"toc":422},"minimark",[11,16,20,23,26,30,33,65,68,72,77,80,83,87,90,94,97,101,105,108,119,125,129,132,137,141,148,151,155,158,162,165,225,229,232,258,261,265,268,288,291,295,298,324,328,331,335,338,353,357,360,389,393,396,416,419],[12,13,15],"h2",{"id":14},"opsgenie-is-going-away","OpsGenie Is Going Away",[17,18,19],"p",{},"Atlassian announced that OpsGenie - their standalone incident management and alerting platform - is being retired and folded into Jira Service Management (JSM). For teams that relied on OpsGenie for alert routing, on-call schedules, and incident response, this is a forced migration with real consequences.",[17,21,22],{},"If you're using OpsGenie today, you have a decision to make: migrate to JSM and accept Atlassian's bundled pricing and workflow, or use this as an opportunity to rethink your monitoring and alerting stack entirely.",[17,24,25],{},"This guide covers what's changing, what you lose in the transition, and how to migrate your monitoring and alerting to a simpler, more focused setup.",[12,27,29],{"id":28},"whats-happening-to-opsgenie","What's Happening to OpsGenie",[17,31,32],{},"Here's what we know:",[34,35,36,43,48,53,59],"ul",{},[37,38,39],"li",{},[40,41,42],"strong",{},"OpsGenie as a standalone product is being discontinued",[37,44,45],{},[40,46,47],{},"Functionality is being absorbed into Jira Service Management",[37,49,50],{},[40,51,52],{},"Existing OpsGenie customers will be migrated to JSM",[37,54,55,58],{},[40,56,57],{},"Pricing changes"," - JSM uses per-agent pricing, which can be significantly more expensive for teams that only used OpsGenie for alerting",[37,60,61,64],{},[40,62,63],{},"Workflow changes"," - Alert management now lives inside Jira's interface, which is heavier and more complex than OpsGenie's focused UI",[17,66,67],{},"For teams that used OpsGenie purely for alert routing and on-call management - without needing Jira's full service desk capabilities - this migration adds cost and complexity with no added value.",[12,69,71],{"id":70},"what-you-lose-in-the-migration","What You Lose in the Migration",[73,74,76],"h3",{"id":75},"simplicity","Simplicity",[17,78,79],{},"OpsGenie was a focused tool: alerts come in, get routed to the right person, and escalate if not acknowledged. JSM is an enterprise service management platform. The alert routing functionality is still there, but it's now wrapped in Jira's project structure, issue types, workflows, and permission schemes.",[17,81,82],{},"For a 5-person engineering team that just needs reliable alerting, JSM is a sledgehammer where a screwdriver would do.",[73,84,86],{"id":85},"predictable-pricing","Predictable Pricing",[17,88,89],{},"OpsGenie had straightforward per-user pricing for alerting. JSM's pricing model is per-agent, and the cost per agent is higher - especially once you factor in that many team members who only needed OpsGenie alert access now need a full JSM agent seat.",[73,91,93],{"id":92},"independence-from-your-ticketing-system","Independence from Your Ticketing System",[17,95,96],{},"With standalone OpsGenie, your alerting was decoupled from your project management. You could use OpsGenie with any monitoring tool, any ticketing system, and any workflow. With JSM, your alerting is now tightly coupled to Jira. If your team uses Linear, Asana, Notion, or anything else for project management, you're now paying for Jira infrastructure you don't use.",[12,98,100],{"id":99},"your-migration-options","Your Migration Options",[73,102,104],{"id":103},"option-1-move-to-jsm","Option 1: Move to JSM",[17,106,107],{},"If your team is already deep in the Atlassian ecosystem (Jira, Confluence, Bitbucket), migrating to JSM might make sense. You'll get:",[34,109,110,113,116],{},[37,111,112],{},"Alert routing and on-call within JSM",[37,114,115],{},"Tight integration with Jira issues",[37,117,118],{},"Incident timelines linked to Jira tickets",[17,120,121,124],{},[40,122,123],{},"The trade-off:"," Higher per-agent cost, more complex UI, and coupling your alerting to Jira's platform.",[73,126,128],{"id":127},"option-2-replace-opsgenie-with-a-focused-alerting-tool","Option 2: Replace OpsGenie with a Focused Alerting Tool",[17,130,131],{},"Tools like PagerDuty or Rootly can replace OpsGenie's alert routing and on-call scheduling without the Jira dependency. This makes sense if alert routing and escalation are your primary needs.",[17,133,134,136],{},[40,135,123],{}," Another vendor to manage, another bill to pay, and you still need a separate monitoring tool feeding alerts into it.",[73,138,140],{"id":139},"option-3-consolidate-monitoring-and-alerting","Option 3: Consolidate Monitoring and Alerting",[17,142,143,144,147],{},"This is where most teams find the biggest opportunity. OpsGenie was an ",[40,145,146],{},"alert router"," - it didn't monitor anything itself. It received alerts from monitoring tools (Datadog, Pingdom, custom integrations) and routed them to people.",[17,149,150],{},"But if your monitoring tool has built-in alert routing, escalation, and multi-channel notifications, you don't need a separate alert router at all. You can eliminate an entire layer of your stack.",[12,152,154],{"id":153},"how-to-migrate-to-vantaj","How to Migrate to Vantaj",[17,156,157],{},"If you were using OpsGenie to route alerts from an uptime monitoring tool, Vantaj can replace both - the monitoring tool and the alert router.",[73,159,161],{"id":160},"step-1-inventory-your-current-setup","Step 1: Inventory Your Current Setup",[17,163,164],{},"Before migrating anything, document what you have:",[166,167,168,181],"table",{},[169,170,171],"thead",{},[172,173,174,178],"tr",{},[175,176,177],"th",{},"What to document",[175,179,180],{},"Where to find it",[182,183,184,193,201,209,217],"tbody",{},[172,185,186,190],{},[187,188,189],"td",{},"Active integrations sending alerts to OpsGenie",[187,191,192],{},"OpsGenie → Settings → Integrations",[172,194,195,198],{},[187,196,197],{},"Alert routing rules",[187,199,200],{},"OpsGenie → Teams → Routing Rules",[172,202,203,206],{},[187,204,205],{},"On-call schedules",[187,207,208],{},"OpsGenie → On-Call → Schedules",[172,210,211,214],{},[187,212,213],{},"Escalation policies",[187,215,216],{},"OpsGenie → Teams → Escalation Policies",[172,218,219,222],{},[187,220,221],{},"Notification preferences per user",[187,223,224],{},"OpsGenie → Users → Notification Rules",[73,226,228],{"id":227},"step-2-recreate-your-monitors","Step 2: Recreate Your Monitors",[17,230,231],{},"For every integration that was sending alerts to OpsGenie, create the corresponding monitor in Vantaj:",[34,233,234,240,246,252],{},[37,235,236,239],{},[40,237,238],{},"HTTP\u002FHTTPS monitors"," for websites and APIs",[37,241,242,245],{},[40,243,244],{},"Heartbeat monitors"," for cron jobs and background workers",[37,247,248,251],{},[40,249,250],{},"SSL and domain monitors"," for certificate and registration expiry",[37,253,254,257],{},[40,255,256],{},"Vendor monitors"," for third-party dependencies",[17,259,260],{},"This step usually takes 15–30 minutes, depending on how many services you're monitoring.",[73,262,264],{"id":263},"step-3-set-up-alert-policies","Step 3: Set Up Alert Policies",[17,266,267],{},"Recreate your OpsGenie routing rules as Vantaj alert policies:",[34,269,270,276,282],{},[37,271,272,275],{},[40,273,274],{},"Which monitors"," trigger which alert policy",[37,277,278,281],{},[40,279,280],{},"Which channels"," receive notifications (email, Slack, webhook, SMS)",[37,283,284,287],{},[40,285,286],{},"Escalation timing"," - how long before an unacknowledged alert escalates",[17,289,290],{},"Vantaj's alert policies map cleanly to what OpsGenie called \"routing rules\" - they determine who gets notified, how, and when.",[73,292,294],{"id":293},"step-4-configure-notification-channels","Step 4: Configure Notification Channels",[17,296,297],{},"Connect your team's notification channels:",[34,299,300,306,312,318],{},[37,301,302,305],{},[40,303,304],{},"Slack"," - Send alerts to specific channels per project or severity",[37,307,308,311],{},[40,309,310],{},"Email"," - Individual or group notifications",[37,313,314,317],{},[40,315,316],{},"Webhooks"," - Push alerts to any system that accepts HTTP callbacks",[37,319,320,323],{},[40,321,322],{},"SMS"," - For critical alerts that need immediate attention",[73,325,327],{"id":326},"step-5-set-up-status-pages","Step 5: Set Up Status Pages",[17,329,330],{},"If you were using a separate status page tool alongside OpsGenie, Vantaj's built-in status pages can replace that too. Create a status page, add the relevant monitors, and share the URL with your users or clients.",[73,332,334],{"id":333},"step-6-run-in-parallel-then-cut-over","Step 6: Run in Parallel, Then Cut Over",[17,336,337],{},"Don't switch everything at once. Run Vantaj alongside your existing OpsGenie setup for 1–2 weeks:",[339,340,341,344,347,350],"ol",{},[37,342,343],{},"Verify that Vantaj detects the same incidents OpsGenie was routing",[37,345,346],{},"Confirm that alerts are reaching the right people via the right channels",[37,348,349],{},"Check that alert timing and escalation match your expectations",[37,351,352],{},"Once confident, disable the OpsGenie integrations",[12,354,356],{"id":355},"migration-checklist","Migration Checklist",[17,358,359],{},"Use this checklist to track your migration:",[34,361,362,365,368,371,374,377,380,383,386],{},[37,363,364],{},"Documented all OpsGenie integrations and routing rules",[37,366,367],{},"Created monitors in Vantaj for every monitored service",[37,369,370],{},"Set up alert policies matching your routing rules",[37,372,373],{},"Connected all notification channels (Slack, email, webhooks)",[37,375,376],{},"Created status pages for user-facing services",[37,378,379],{},"Ran parallel monitoring for 1–2 weeks",[37,381,382],{},"Verified alert delivery and escalation",[37,384,385],{},"Disabled OpsGenie integrations",[37,387,388],{},"Cancelled OpsGenie \u002F JSM subscription",[12,390,392],{"id":391},"why-this-migration-is-an-opportunity","Why This Migration Is an Opportunity",[17,394,395],{},"Forced migrations are painful, but they're also a chance to simplify. Most teams that audit their OpsGenie setup during migration discover:",[34,397,398,404,410],{},[37,399,400,403],{},[40,401,402],{},"Integrations that are no longer active"," - services that were decommissioned but never removed from monitoring",[37,405,406,409],{},[40,407,408],{},"Routing rules that no longer match the team structure"," - people who left, teams that reorganized",[37,411,412,415],{},[40,413,414],{},"Alert noise they'd been tolerating"," - too many low-priority alerts going to too many people",[17,417,418],{},"Use the migration as a spring cleaning. Start fresh with only the monitors and alert policies you actually need, routed to the people who actually respond to them.",[17,420,421],{},"A simpler stack is a more reliable stack.",{"title":423,"searchDepth":424,"depth":424,"links":425},"",2,[426,427,428,434,439,447,448],{"id":14,"depth":424,"text":15},{"id":28,"depth":424,"text":29},{"id":70,"depth":424,"text":71,"children":429},[430,432,433],{"id":75,"depth":431,"text":76},3,{"id":85,"depth":431,"text":86},{"id":92,"depth":431,"text":93},{"id":99,"depth":424,"text":100,"children":435},[436,437,438],{"id":103,"depth":431,"text":104},{"id":127,"depth":431,"text":128},{"id":139,"depth":431,"text":140},{"id":153,"depth":424,"text":154,"children":440},[441,442,443,444,445,446],{"id":160,"depth":431,"text":161},{"id":227,"depth":431,"text":228},{"id":263,"depth":431,"text":264},{"id":293,"depth":431,"text":294},{"id":326,"depth":431,"text":327},{"id":333,"depth":431,"text":334},{"id":355,"depth":424,"text":356},{"id":391,"depth":424,"text":392},"tutorials","2026-06-02","Atlassian is shutting down OpsGenie and merging it into Jira Service Management. Here's what that means for your monitoring setup and how to migrate without losing coverage.","md",null,"2026-06-04",{},true,"\u002Fblog\u002Fopsgenie-end-of-life-migration-guide",8,{"title":5,"description":451},"blog\u002Fopsgenie-end-of-life-migration-guide","AJDSxZ98Lw_wuCyftRkNTqSGpTh8Hu8Nr8OFm4V23lg",1780583794110]