Migrate Opsgenie alert workflows to Jira Service Management Operations before the April 2027 shutdown
domain: support.atlassian.com/opsgenie · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Audit existing Opsgenie resources: list teams, escalation policies, schedules, and alert routing rules via the Opsgenie REST API (GET /v2/teams, /v2/schedules, /v2/escalations) and export results as JSON
Enable Opsgenie Operations inside your Atlassian Jira Service Management (JSM) project; JSM Operations is the migration target for Opsgenie on-call and alerting functionality
Map Opsgenie teams to JSM Operations teams; on-call schedules and escalation policies can be recreated in JSM Operations under the Schedules and Escalations sections
Update alert integrations (monitoring tools, webhooks, email) to send to JSM Operations API endpoints instead of Opsgenie API endpoints; JSM Operations uses a separate API key per integration
Test the migrated configuration in JSM Operations by triggering test alerts and verifying on-call routing, escalations, and notifications behave as expected
Decommission Opsgenie integrations after a parallel-run period; Atlassian will shut down standalone Opsgenie on April 5, 2027 and delete all unmigrated data
Known gotchas
Opsgenie stopped accepting new signups on June 4, 2025; Atlassian has confirmed the shutdown date of April 5, 2027 with no extensions — data not migrated by that date will be deleted
JSM Operations does not have full feature parity with Opsgenie for all alert policy conditions; test complex routing rules carefully before decommissioning Opsgenie
The Opsgenie API base URL (api.opsgenie.com) continues to work until shutdown, but Atlassian is not adding new features — use the migration period to refactor integrations rather than building new ones against Opsgenie
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?