Choose Opsgenie if
- You already run Jira Service Management or Compass and want paging inside it.
- You need SMS or voice paging right now, which Transmit does not switch on yet.
Opsgenie is no longer sold, and Atlassian ends support on 5 April 2027. You have to move somewhere. Here is what moving to Transmit looks like next to Atlassian’s own path.
Claims about Opsgenie are from Opsgenie’s own pages, checked on 4 October 2026. Products change; follow the sources for the current picture. Tell us if something here is out of date.
| Topic | Transmit | Opsgenie |
|---|---|---|
| Can you buy it | Yes, in early access. Free for up to 5 responders; Team is $15 per responder a month. | No. Opsgenie stopped being sold on 4 June 2025.[2] |
| After 5 April 2027 | Keeps paging. | End of support: access is shut off, and data that was not migrated is deleted.[1] |
| Where Atlassian suggests you go | Import into Transmit; it only ever reads from Opsgenie. | Jira Service Management or Compass.[2] |
| Moving your setup | Import members, schedules, policies, services and heartbeats, with a check of who is on call against Opsgenie, and warnings for anything that does not map exactly. | An in-product migration tool that syncs most Opsgenie data and configuration, with 120 days of Opsgenie alongside.[3] |
| Alert API | Answers on Opsgenie’s /v2/alerts paths. Change the URL and key. | The Opsgenie Alert API, at api.opsgenie.com/v2/alerts.[4] |
| Heartbeats | Opsgenie’s ping path, plus a ping URL with the key in it. | The Heartbeat API, pinged at /v2/heartbeats/{name}/ping.[5] |
| Prometheus Alertmanager | Point the opsgenie_config api_url at Transmit, or use its webhook receiver. | Alertmanager has a built-in Opsgenie receiver, with an api_url that defaults to Opsgenie.[6] |
| Paging channels | Email today. SMS and voice calls are coming soon. | Ends with the product on 5 April 2027.[1] |
Transmit is in early access. Tell us about your on-call setup, and we will help you import it and check it against Opsgenie before you switch.