How to migrate from Opsgenie before it shuts down
Atlassian stopped selling Opsgenie on June 4, 2025, and ends support on April 5, 2027. This guide walks through moving your on-call setup — schedules, escalation, integrations and people — to a new tool with a parallel run, using EvoHub as the example.
The Opsgenie timeline
| Date | What happens |
|---|---|
| June 4, 2025 | Opsgenie end of sale — no new Opsgenie standalone purchases. |
| April 5, 2027 | Opsgenie end of support — standalone Opsgenie stops working; Atlassian's path is Jira Service Management or Compass. |
Opsgenie concepts, mapped to EvoHub
| Opsgenie | EvoHub | Notes |
|---|---|---|
| Teams | Teams | Invite everyone — EvoHub has no per-seat fee. |
| On-call schedules & rotations | Schedules & rotations | Recreate each rotation with the same participants, handoff time and time zone. |
| Schedule overrides | Overrides & takeover | Responders can also take over an incident from the mobile app. |
| Escalation policies | Escalation policies | Multi-step, with a delay and notification method per step. |
| Integrations (Prometheus, Datadog, CloudWatch, email…) | 20 alert integrations | Each integration gets its own URL or inbound email address and escalation policy. |
| Alert API | EvoHub alert API | A JSON POST where only summary is required; supports trigger, acknowledge and resolve. |
| Heartbeats | Uptime heartbeat monitors | Dead-man's-switch monitors for cron jobs and workers — free. |
| Notification channels (SMS, voice, push, email) | Voice call, mobile push, email | SMS is not offered yet — move SMS-only responders to push or voice. |
| Mobile app | iOS and Android apps | Acknowledge, resolve and take over incidents. |
| Statuspage (separate Atlassian product) | Status pages | Included in the same platform, on your own domain. |
Step-by-step migration
Inventory what you run in Opsgenie
List every team, schedule (with rotations and overrides), escalation policy, integration and heartbeat. The Opsgenie UI or its REST API can list them. Note which alert sources page which team — that mapping is what you will rebuild.
Create your EvoHub organization and invite the team
Sign up, create teams that mirror your Opsgenie teams, and invite responders, managers and stakeholders. Seats are free, so there is no reason to leave anyone out. Ask responders to install the iOS or Android app and allow notifications.
Recreate schedules and rotations
For each Opsgenie schedule, create an EvoHub schedule with the same rotation length, handoff time, time zone and participant order. Add any upcoming overrides so the first weeks match exactly.
Rebuild escalation policies
Recreate each escalation policy step by step: who (a schedule or a person), how long to wait, and how to notify (voice call, push or email). Responders who relied on SMS in Opsgenie should switch to push or voice.
Connect alert sources — and run both tools in parallel
Add an EvoHub integration for each alert source and attach its escalation policy. Where the source allows several destinations (Alertmanager receivers, Datadog webhooks, CloudWatch SNS subscriptions, email recipients), keep Opsgenie and add EvoHub, so both receive the same alerts for a week or two.
Test paging end to end
Fire a test alert through each integration and confirm the right person is paged, can acknowledge from the app, and that recovery auto-resolves the alert where the source supports it. Compare what EvoHub paged against Opsgenie during the parallel run.
Cut over and decommission Opsgenie
Once the parallel run is clean, remove the Opsgenie destinations from your alert sources, and replace heartbeats and API calls. Finish well before April 5, 2027 — leave time for a quiet week with EvoHub as the only pager.
Setup steps for each alert source: EvoHub integrations. Product comparison: EvoHub vs Opsgenie.
Opsgenie migration FAQ
When does Opsgenie shut down?
Atlassian ended new Opsgenie sales on June 4, 2025. Opsgenie reaches end of support on April 5, 2027, after which standalone Opsgenie stops working and Atlassian directs customers to Jira Service Management or Compass.
Can I import my Opsgenie configuration into EvoHub automatically?
Not yet — there is no automated importer. Schedules, escalation policies and integrations are recreated by hand, which for most teams takes an afternoon. The EvoHub team can help plan the move: info@evosync.io.
Do I have to move to Jira Service Management?
No. Jira Service Management is Atlassian's suggested path, but any on-call tool works. EvoHub keeps on-call as a focused product, priced on usage instead of per seat, with uptime monitoring and status pages in the same platform.
How much does EvoHub cost compared to Opsgenie?
EvoHub has no per-user fee. You pay per usage — an ingested alert is 1 EvoHub token (about $0.015), a voice call 10 tokens (about $0.15), push and webhook notifications are free — and every account gets 200 free tokens each month.
Does EvoHub support SMS alerts like Opsgenie?
Not yet. EvoHub pages by voice call, mobile push and email today; SMS is coming soon.
Start free — 200 EvoHub tokens every month. See pricing.
Last updated: · EvoHub is built and operated by EvoSync LLC.