Switching from Opsgenie to Uptimely
Atlassian stopped selling Opsgenie on Jun 4, 2025, and shuts it down on April 5th, 2027, when any data that has not been moved is deleted. Atlassian's own destination is Jira Service Management, and for a team that routes alerts from many monitoring tools it is the better answer. This page is for the other kind of Opsgenie team: one that pages on its own websites, APIs and scheduled jobs and wants the checks, the pager and the status page in one product. It says what Uptimely imports today (your heartbeats), what you set up by hand (on-call schedules and escalation), and what has no equivalent at all.
What Atlassian's own pages say
Opsgenie's end of sale was Jun 4, 2025. Existing customers can keep using it until April 5th, 2027; after that Atlassian says Opsgenie will be shut down, the product will no longer be accessible, and data that has not been moved will be deleted, though you can still download your data. If you move to Jira Service Management instead, the table on Atlassian's feature-changes page lists heartbeats as available only in Premium and Enterprise there, so a team that relies on heartbeats on a lower plan has a decision to make either way.
Deciding rather than moving?
This page assumes you have already chosen to leave. Uptimely vs Opsgenie is the page that argues the choice itself, with every competitor figure sourced and dated, and all Uptimely comparisons lists the rest.
What maps to what, and what does not
| Opsgenie | Uptimely | Notes |
|---|---|---|
| Heartbeat | Incoming Request (heartbeat) monitor — imported | Imported from your Opsgenie account with an API key that has Read and Configuration Access: name, interval and description. Each also gets a small grace (20% of the interval, between 2 and 60 minutes) so a ping a few seconds late does not page anyone; you can change it. Disabled heartbeats are listed and skipped. Each monitor gets a new heartbeat URL, and your jobs keep pinging Opsgenie until you point them at it. |
| On-call schedule, rotations, overrides | On-call schedule with layers and user overrides — set up by hand | Layers carry a rotation, a handoff time and restriction times, and overrides cover swaps and holidays. Nothing is imported: you rebuild each schedule from what Opsgenie shows you. |
| Escalation policy | On-call policy with escalation rules — set up by hand | Rules run in order, each notifying users or an on-call schedule after a delay, and repeat until someone acknowledges. Opsgenie's per-rule conditions and its notify-next, notify-previous and notify-all options are not imported, and may not have a one-to-one equivalent. |
| Team and its members | Project members — invited by hand | Each person needs their own Uptimely account and verifies their own phone number. Free has 3 members and Pro has 25, so a larger Opsgenie team does not fit on one project. |
| Alert integrations (Datadog, Prometheus, CloudWatch and the rest) | — | No equivalent. Uptimely pages for what its own monitors detect; it is not an alert-routing hub and does not ingest alerts from other tools. |
| Routing rules and alert policies | — | No equivalent. Which policy a monitor pages is chosen on the monitor itself, not by rules over alert payloads. |
| Maintenance window | Scheduled maintenance — set up by hand | Per monitor and per status page, with subscriber notices, rather than rule-based alert suppression. |
| Alert and incident history | — | Not imported. Download it from Opsgenie before April 5th, 2027 if you need it for your records. |
What you gain
- Uptime checks in the same product as the pager: a failing website, API, port or DNS check declares an incident, and that incident runs your on-call policy.
- On-call schedules and escalation included on every plan, Free too, and a flat $29/month Pro plan for 25 members.
- Status pages on the same plan: 1 on Free, unlimited on Pro, each with a custom domain, subscribers and scheduled maintenance.
- Your heartbeats come across in one step instead of being retyped, and every one that cannot is named with the reason.
- A public /v1 REST API with an OpenAPI 3.1 schema, an npm SDK and an MCP server.
What Uptimely does not do
- The Opsgenie importer reads heartbeats only. On-call schedules, escalation policies, teams, routing rules, integrations and alert history are not imported; schedules and escalation are set up by hand and the rest has no equivalent here.
- Uptimely is not an alert-routing hub. It does not receive alerts from Datadog, Prometheus, CloudWatch or other tools, so if most of your pages start there, Jira Service Management or another routing product is the right move.
- Free has 3 members and Pro has 25, and every responder needs their own account. A team larger than that does not fit.
- If you add uptime checks, Uptimely probes from one vantage point, not several regions. A monitor declares an incident only after consecutive failed checks, each re-confirmed, and failures that look like our own network are checked against a live egress health check before anyone is paged. A second vantage is on the roadmap and is not shipped.
- There is no app-store mobile app. Phone alerts arrive as web push, and as SMS and voice calls where the project turns those on.
How to move
- In Opsgenie, create an API key under Settings → App Settings → API Key Management with Read and Configuration Access ticked (heartbeats are configuration, so Read alone is refused; it needs no Create/Update or Delete access), and note whether your account is on the US or the EU site.
- Try Uptimely first if you like: guest mode needs no account, so you can create a monitor, watch it run and publish a status page before you sign up.
- In Uptimely, open Monitors → Import and export, and paste the key into Import heartbeats from Opsgenie with your region. You see a preview of every heartbeat it will create and every one it skips, with the reason. Nothing is written until you confirm, and the key is used for that request only — it is never stored. If you would rather not paste a key, save the JSON that GET /v2/heartbeats returns and drop the file into the Import card instead.
- Point each job at its new monitor: replace the call to Opsgenie's heartbeat ping with a request to the heartbeat URL on the monitor's Documentation page. Keep pinging Opsgenie too until the Uptimely monitor has seen a few pings.
- Invite your responders under the project's members, and have each one add and verify the phone number they want to be paged on.
- Rebuild each on-call schedule under On-Call Duty → On-Call Schedules: one layer per Opsgenie rotation, with its users, rotation length, handoff time and any restriction times, then add overrides for swaps already planned.
- Rebuild each escalation policy under On-Call Duty → On-Call Policies: add escalation rules in the order Opsgenie ran them, each notifying a schedule or users after its delay, and choose the policy in each monitor's criteria so its incidents page it.
- Download any Opsgenie alert history you need before April 5th, 2027, then turn Opsgenie off once Uptimely has paged you for something real.
Opsgenie's end-of-sale date, shutdown date, deletion of data that has not been moved, the option to download your data and the automatic sync into Jira Service Management are quoted from Atlassian's own migration page, read 2026-10-12: https://www.atlassian.com/software/opsgenie/migration . That heartbeats are Premium and Enterprise only in Jira Service Management is quoted from the table on Atlassian's feature-changes page, whose Heartbeats row reads “Only in Premium and Enterprise.” under “Availability in Jira Service Management”, re-read 2026-10-13: https://support.atlassian.com/opsgenie/docs/feature-changes-and-deprecations-in-jira-service-management/ . Opsgenie's heartbeat fields are from its API documentation: https://docs.opsgenie.com/docs/heartbeat-api . No Opsgenie or Jira Service Management price is quoted. Uptimely figures reflect its current plans.
Uptimely's Free plan has 10 monitors, 1 status page and 1-minute checks, with no credit card. Pro comes with a 14-day free trial.
Start free →What does Uptimely import from Opsgenie?
Heartbeats. Paste an Opsgenie API key with Read and Configuration Access under Monitors → Import and export, or drop in the JSON that GET /v2/heartbeats returns, and each enabled heartbeat becomes a heartbeat monitor with the same name and interval. You see the plan first, and nothing is written until you confirm. On-call schedules, escalation policies, teams, routing rules, integrations and alert history are not imported.
Is my Opsgenie API key stored?
No. It is sent once to Opsgenie to read your heartbeats for the preview, once more when you confirm the import, and it is never saved or logged. The key needs Read and Configuration Access, because heartbeats are configuration in Opsgenie, but no Create/Update or Delete access, so it cannot change anything in your Opsgenie account.
Do my jobs need to change?
Yes. Each imported monitor has its own new heartbeat URL, so every job that pings Opsgenie has to be pointed at its Uptimely monitor instead. Until you do, the new monitor hears nothing and goes Offline when its first window ends. The import tells you this for every heartbeat it creates.
Can Uptimely receive alerts from my other monitoring tools like Opsgenie does?
No. Uptimely pages for incidents its own monitors declare and does not ingest alerts from Datadog, Prometheus, CloudWatch or other tools. If routing other tools' alerts is most of what Opsgenie does for you, Atlassian's Jira Service Management, which Atlassian says syncs most Opsgenie data automatically, is the better move.
When does Opsgenie shut down?
Atlassian ended sales on Jun 4, 2025, and existing customers can use Opsgenie until April 5th, 2027. After that Atlassian says it will be shut down and data that has not been moved will be deleted, though you can still download your data.