How to Migrate from Opsgenie to Self-Hosted OnCallAlert

Atlassian stopped selling Opsgenie on June 4, 2025, and support ends on April 5, 2027. This guide is a migration plan, not just a click path: phases, a field-by-field mapping, what does not move, time and cost estimates, and a rollback.

Timeline. Per Atlassian, Opsgenie can no longer be bought, and access is shut off on April 5, 2027. Data not migrated by then is deleted. Check Atlassian's announcement for your own dates.

What are my options now that Opsgenie is ending?

You have three: move to Jira Service Management (Atlassian's own path, per-agent pricing), move to another on-call tool, or self-host. Atlassian points customers to Jira Service Management or Compass. Self-hosting keeps alert data on your own server and replaces per-user pricing with a flat yearly price. The right choice depends on team size and who must run the server.

What does the migration plan look like, phase by phase?

Plan for five phases: inventory, import, rewire alert sources, parallel run, cutover. The importer covers phase 2 in minutes. Most of your time goes to rewiring integrations and the parallel run. Every phase before cutover is reversible, because OnCallAlert only reads from Opsgenie.

  1. Inventory (day 1). List users, teams, schedules, escalation policies, integrations, heartbeats, routing rules and maintenance windows in Opsgenie. Note which integrations send what, and who owns each.
  2. Stand up and import (day 1 to 2). Run OnCallAlert, create the read-only key, preview, import (steps below).
  3. Rebuild what does not map (day 2 to 5). Recreate routing logic, heartbeats and maintenance windows by hand or with the Terraform, OpenTofu or Pulumi provider.
  4. Rewire and parallel run (1 to 2 weeks). Point alert sources at OnCallAlert while Opsgenie keeps running. Send a test alert to every service. Compare who gets paged in each.
  5. Cut over and keep a rollback. Switch the senders fully, keep Opsgenie read-only for at least one more week, then turn it off. To roll back, point senders back at the old Opsgenie URL.

How long does it take?

These are our planning estimates, not measurements: about 1 to 2 days of effort for a team of 5, about 1 week for 20, and 2 to 3 weeks for 50 or more, mostly spent on integrations and the parallel run. The import itself takes minutes at any size.

Team sizeHands-on effortCalendar time with parallel run
5 users1 to 2 daysAbout 1 week
20 usersAbout 1 week2 weeks
50+ users2 to 3 weeks3 to 4 weeks

Before you start

  1. Run OnCallAlert. You need the Docker image and a PostgreSQL database. The Docker quickstart covers it.
  2. Sign in as an admin.
  3. Pick a quiet week. You will run both systems side by side for a few days.

Step 1. How do I create a read-only key in Opsgenie?

In Opsgenie go to Settings → Integrations → Add integration → API, with Read and Configuration access. Note the key and your region (US or EU). If Opsgenie has already moved into Jira Service Management, use the Jira Service Management option instead, with an API token from id.atlassian.com. OnCallAlert only reads from your old tool. Nothing changes there.

Step 2. How do I preview and run the import?

Open Admin → Import (/admin/import), choose Opsgenie, enter the key and region and click Preview. Read the counts and warnings, tick the confirmation box and import. The import is one transaction: everything is imported or nothing is.

  1. Check which users match existing accounts and which will be created.
  2. Fix warnings in Opsgenie or note them for phase 3.
  3. Delete the Opsgenie key afterwards. OnCallAlert does not store it.

What comes across, field by field?

Users, contact methods, teams, schedules with rotations, escalation policies and integrations come across. Integrations become one service each. This table is taken from the migration docs; nothing outside it is imported.

OpsgenieOnCallAlertNotes
Users (not blocked)UsersMatched to existing users by email, others created. No password: sign in with GitHub or Google using the same verified email, or OIDC.
Contact methods, notification rulesContact methods and notification rulesEmail, SMS and voice.
TeamsTeams and members
Schedules and rotationsSchedules and rotationsIncluding overnight and multi-day shifts.
Escalation policiesEscalation policiesSame steps, delays and repeats.
IntegrationsOne service per integration, with an integration keyUses the policy from the team's default routing rule.

What does not migrate?

Anything not in the table above does not come across. Expect to recreate these by hand: routing rules beyond a team's default, heartbeats, maintenance windows, alert and incident history, and custom actions or automations. Export history from Opsgenie first if you need it, because Atlassian deletes it after April 5, 2027.

Step 3. How do I point my alerts at OnCallAlert?

The result page lists every old integration with its new URL and what to change. This is the step that takes the most time.

Step 4. How do I cut over safely?

Test every service, run both tools in parallel for one to two weeks, then switch senders fully and keep Opsgenie for a rollback window. Imported users land in their accounts with schedules and contact methods already in place.

How much does it cost compared with Opsgenie and Jira Service Management?

For 5, 20 and 50 users, OnCallAlert Team costs $1,499 a year flat, against $1,197 to $11,970 for Opsgenie Standard and $1,290 to $12,900 for Jira Service Management Standard at list price. Opsgenie is no longer sold, so existing customers pay until April 2027 only.

UsersOpsgenie Essentials / Standard (per year)Jira Service Management Standard (per year)OnCallAlert Team (per year)
5$567 / $1,197$1,290$1,499
20$2,268 / $4,788$5,160$1,499
50$5,670 / $11,970$12,900$1,499

Opsgenie list prices: $9.45 Essentials and $19.95 Standard per user per month billed annually. Jira Service Management: about $21.50 per agent per month. Atlassian offers volume discounts, so your quote may be lower. OnCallAlert Team includes the mobile app and up to 50 users; add roughly $20 a month for your own server if you do not have one. At 5 users a small team may be cheaper on Opsgenie Essentials until it shuts off, and Core ($699 a year, up to 15 users) has no mobile push. Jira Service Management also bundles service desk features OnCallAlert does not have. Try your own numbers in the cost calculator.

Why does OnCallAlert cost less to own than a per-user plan?

One flat license covers your whole team: $1,499 a year (Team) for up to 50 on-call users, with unlimited free viewers. The server is a single small container, it uses the PostgreSQL you probably already run, and SMS and voice go through your own Twilio account at carrier cost.

How much does the flat license save?

The price does not change as you add responders. Team works out at about $12.49 per user a month for 10 users, $6.25 for 20 and $2.50 for 50, so the bill stays predictable while per-user plans keep climbing. Team costs less than each plan below from the number of paid users in the last column.

Compared withList priceTeam ($1,499 a year) costs less from
Opsgenie Essentials$9.45 per user a month, annual14 users
Opsgenie Standard$19.95 per user a month, annual7 users
Opsgenie Enterprise$31.90 per user a month, annual4 users

These figures count license fees at the list prices on our Sources list (checked November 2026) and ignore taxes and add-ons. Very small teams can start on a free plan elsewhere, such as PagerDuty Free for up to 5 users, and move to OnCallAlert as the rotation grows. The Core plan ($699 a year, up to 15 users) suits teams that alert by SMS and voice, and the mobile app comes with Team and above. Past 50 users, extra 10-user packs cost $300 each on yearly plans.

What does it cost to run?

OnCallAlert is one container plus PostgreSQL 16 or newer. In our deployments the server uses roughly half a vCPU and PostgreSQL about the same at typical on-call load, and most teams already have a PostgreSQL instance, so the database often adds no new machine. We have not published a benchmark, so size it for your own alert volume. You control upgrades, backups and placement: run it on infrastructure separate from the systems it watches.

How do you keep SMS and voice bills low?

You use your own Twilio account and pay Twilio directly, with no markup from us. In the US an SMS costs roughly $0.013 per segment with carrier fees and voice about $0.014 a minute, plus a monthly number fee (list prices, so check Twilio). Hosted tools meter SMS and voice too, so this cost exists everywhere; here you see it on your own bill. See our full-screen call versus direct call breakdown for the arithmetic.

The hybrid approach is what cuts it. When the responder's phone is online, the alert arrives as a push notification from the mobile app and rings through Do Not Disturb, so no call or SMS is sent. SMS and voice fire only as a fallback when the phone is offline or the alert is not acknowledged. Every page delivered by push is a call and two SMS segments you do not pay for, about $0.04 at the list prices above, and the saving grows with alert volume. Read how mobile push replaces most SMS and voice for details. Ring-through-Do-Not-Disturb works on Android today; Apple's Critical Alerts approval for iPhone is still pending.

Why does self-hosting matter for data privacy?

Your alert content, schedules and contact details stay on a server you control. The OnCallAlert server sends no telemetry about your alerts. Optional features call out: the license check, the push relay for mobile notifications, and the dead-man's switch heartbeat. The privacy page lists exactly what leaves your server.

What are the weak spots?

You run the server, so you own upgrades, backups and uptime. The importer does not move routing rules, heartbeats, maintenance windows or history, and there is no hosted Managed Cloud yet. Opsgenie has integrations OnCallAlert does not accept natively, and those senders must post JSON to OnCallAlert.

After the move

Install the mobile app and pair it for push alerts (the Team, Business and Unlimited plans include the hosted push relay). If you manage on-call as code, the Terraform, OpenTofu and Pulumi provider can take over from there (see infrastructure as code).

Frequently asked questions

Can I keep using Opsgenie until the end?

Yes. Per Atlassian, access works until April 5, 2027. Run both in parallel until you are confident, then switch off.

Does the importer change anything in Opsgenie?

No. It reads through a read-only key. Delete the key after the import.

What happens to my Opsgenie alert history?

It is not imported. Export what you need before April 5, 2027, when Atlassian deletes un-migrated data.

Can I migrate to Jira Service Management instead?

Yes. Atlassian offers that path. OnCallAlert can also import from Opsgenie data that already moved into Jira Service Management.

Share this post:

See what your team would pay. Put your own numbers into the calculator, then compare the plans.

PagerDuty cost calculator → Pricing & plans

Sources and notes (checked 2026-11)