Skip to content
WelcoYour alerts, by text.

Opsgenie end of life: a step-by-step plan before April 2027

Opsgenie end of life is April 5, 2027. Atlassian stopped new sales on June 4, 2025, and says the product shuts down and unmoved data is deleted on that date. Plan the move now: list each alert source, export what you need, and repoint every source before the cutoff.

Move my alert textsBook a demo

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing

Published:

The problem

Opsgenie goes dark

  • Shutdown on April 5, 2027
  • Data not moved is deleted
  • Alerts stop reaching phones

The fix

A planned move

  • Know which features you use
  • Export schedules and history
  • Repoint each alert source
Illustration: the problem, opsgenie goes dark, next to the fix, a planned move.
  • Atlassian stopped new Opsgenie sales on June 4, 2025 and shuts the product down on April 5, 2027.
  • Data you haven't moved by then is deleted, per Atlassian's migration page.
  • Need escalations and acknowledgements? Pick an incident tool. Only need alert texts? The move is far simpler.
  • Run old and new side by side for two weeks before you switch off.

When does Opsgenie shut down?

Opsgenie shuts down on April 5, 2027, per Atlassian's Opsgenie migration page (read October 6, 2026). Partner Adaptavist's notice of March 5, 2025 gives the same dates and puts the cutoff at 12:00 AM PST.

Dates from Atlassian and Adaptavist, read October 6, 2026.

No new Opsgenie sales

Date
June 4, 2025
What it means for you
New teams can't buy Opsgenie. Existing customers can no longer change their edition.

Opsgenie shuts down

Date
April 5, 2027
What it means for you
Atlassian says the product will no longer be accessible. Alerts routed through it stop.

Data removal

Date
April 5, 2027
What it means for you
Atlassian says any Opsgenie data that has not been moved is deleted.

Sources: Atlassian: Migrate from Opsgenie (read October 6, 2026); Adaptavist: Opsgenie availability changes (Mar 5, 2025) (read October 6, 2026)

Where does Atlassian want Opsgenie customers to go?

Atlassian's own path is Jira Service Management, which now carries Opsgenie's alerting and on-call features. Its migration page says on-call schedules, escalation policies and incident workflows move across with an automated tool.

The move does not start by itself. An Opsgenie owner begins it from Settings > Plan your move, per the same page. Atlassian also offers to carry unused subscription time over, so check its conditions before you plan.

That path suits teams who work in Opsgenie all day. It is not the only path, and our alert texting guides cover the simpler one for teams that mostly read texts.

Why the shutdown needs a plan, not a rush

April 2027 feels far away. But every alert source that points at Opsgenie must be moved by hand, and each one needs a test.

A server monitor, a backup job, a UPS card and a building system may all send to Opsgenie today. Miss one, and that alert quietly stops on shutdown day.

Who should move where after Opsgenie?

Pick the replacement by what your team does when an alert fires, not by everything Opsgenie could do. Many small teams use only a slice of it.

Teams that need escalations, schedules and acknowledgements

If an unanswered alert must climb to a second and third person, you need escalation chains. Welco doesn't run those, take acknowledgements or place voice calls.

Move to Jira Service Management, which takes your Opsgenie setup across, or to another incident tool. Our PagerDuty comparison shows where a full on-call tool earns its per-user price.

Teams that only need texts from email alerts

If your monitoring tools email Opsgenie and people just read the text and act, you need far less. Welco turns those alert emails into texts for the on-call person, routed by time of day.

There is nothing to install and no per-user fee. Our Opsgenie alternative comparison puts the two side by side.

Teams with a bit of both

Split the sources. Keep the few alerts that truly need escalation in an incident tool, and send plain email alerts to the person on duty by text. You pay seats only for the people who use the bigger tool.

Signs you used Opsgenie mostly for texts

  • Most of your integrations are plain email integrations from monitoring tools.
  • Nobody acknowledges alerts in the app. People just read the text and act.
  • Your schedule is a simple weekly on-call rotation, and escalations rarely fire.
  • The per-user bill grew every time someone joined the alert list.

Move off Opsgenie in 7 steps

Start at least a quarter before the shutdown, so there is time to test every source.

  1. Export your integration list

    In Opsgenie, open the integrations list and copy every entry into a shared sheet. Include monitoring tools, backup jobs, email integrations, API integrations and heartbeats.

    • Record how each one sends: by email or through Opsgenie's API.
    • Add the person who owns the source, so someone can change its settings later.

  2. Write down who gets what

    For each source, note which people receive it today, on which days and at which hours. This becomes your routing plan in the new tool.

  3. Mark the features you rely on

    For each source, mark what you really use: a text, a phone call, an escalation to a second person, an acknowledgement, or a schedule. Be strict, because this list picks your replacement.

  4. Export what you need to keep

    Save on-call schedules, contact lists and any alert history you must retain. Do it well before the cutoff, since Atlassian says data not moved will be deleted.

  5. Invite the people on call

    With Welco, each person joins from an invite with their own mobile and replies YES, which is their opt-in. Do this early, so every phone is confirmed before the first real alert.

  6. Repoint each source

    Change each tool's alert email from the Opsgenie address to your Welco address. Try each rule in test mode first, then let night alerts follow after-hours routing to the on-call phone.

  7. Run both, then cut over

    Keep Opsgenie running for two weeks while the same alerts also reach the new service. Compare what arrives each day and fix any gaps.

    • An alert that reached Opsgenie but not a phone means that source still points at the old address.
    • Pick a quiet weekday for cutover, remove the Opsgenie integrations, then tell the team.

Used Opsgenie mainly for alert texts?

Point those alert emails at Welco and test them this week.

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing

Move my alert textsBook a demo

Example: a website alert after the move

An uptime monitor that used to email Opsgenie now emails a Welco address. The on-call admin gets one short text, trimmed as our short alert texts guide shows.

Alert email from monitor@uptime.example.net, subject “(F) shop.example.com Ping (Failing)”. Welco trims it to one text of 85 characters: “Welco: [shop.example.com] Not responding to ping at 6:52 AM. Reply STOP to opt out.”

Text received: Welco: [shop.example.com] Not responding to ping at 6:52 AM. Reply STOP to opt out.

Characters234851 credit

Animation: the alert email "(F) shop.example.com Ping (Failing)" is trimmed into one text: "Welco: [shop.example.com] Not responding to ping at 6:52 AM. Reply STOP to opt out."

Any tool that can send an email can do the same. See how email from any system becomes a text.

What changes for the person on call?

They get a plain text on the phone they already carry, with no app to install. Each text starts with Welco: and ends with Reply STOP to opt out., a carrier rule for business texts.

A reply comes back to your team as an email through replies by email. It does not close or acknowledge anything in the monitoring tool, so the person still fixes the fault there.

If one fault sends forty emails, alarm flood control limits the burst so the phone stays usable. Each phone also gets each alert once, not once per copy of the email.

Mistakes to avoid when leaving Opsgenie

Most failed moves come from a source nobody remembered, not from the new tool.

  • Listing sources from memory. Export the integrations list instead. The backup job set up years ago is the one people forget.
  • Forgetting heartbeats. Opsgenie can alert when an expected check-in goes missing. Welco only acts on emails that arrive, so move that check into a monitoring tool that emails on failure.
  • Missing API integrations. Tools that post to Opsgenie through its API need their email alert turned on before they can reach Welco.
  • Assuming phones carry over. Opsgenie contacts don't move to Welco. Each person joins and confirms their own phone.
  • Switching off before the side-by-side run. Two weeks of both shows which sources were missed.
  • Paying for seats nobody uses. If most people only read texts, a per-user tool charges for features they never open.

Opsgenie exit checklist

Tick these off before April 5, 2027.

0 of 9 done

Frequently asked questions

What date should our Opsgenie move be finished by?

Finish before April 5, 2027, the shutdown date on Atlassian's migration page. New sales already stopped on June 4, 2025. Check the notice in your own Atlassian account too, since plan details can differ, and aim to be done a few months early.

What happens to our Opsgenie data after the shutdown?

Atlassian says data that hasn't been moved is deleted when Opsgenie shuts down. Export on-call schedules, contact lists and any alert history you need to keep before then. Don't leave it to the last week, when everyone else is exporting too.

Will Atlassian move our Opsgenie data automatically?

Only after you start the move. Atlassian's migration page says data and settings move to Jira Service Management once an Opsgenie owner starts the process. Owners begin from Settings > Plan your move. If nobody starts it, unmoved data is deleted at shutdown.

Is Welco a full replacement for Opsgenie?

No. Welco turns alert emails into texts for the right on-call phone, with routing by time of day. It has no escalation chains, acknowledgements or voice calls. If your team relied on those, choose a full on-call tool instead.

How long does it take to move alert texts off Opsgenie?

Changing an address in each tool takes minutes. The real time goes into finding every source and testing it. Most small teams can move in a week or two, including the side-by-side run before switching Opsgenie off.

Do our on-call staff need an app after leaving Opsgenie?

Not with Welco. Alerts arrive as normal texts on the phone each person already carries. Each person joins once with their own mobile and replies YES before the first alert. Their text replies come back to your team as email.

Can we test Welco before the Opsgenie cutover?

Yes. Test mode shows what each rule would send without texting anyone or using credits. Then run the free trial alongside Opsgenie with real alerts. A card is needed to verify your business, and nothing is charged until you approve a plan.

Can we keep our monitoring tools when we leave Opsgenie?

Yes. Nagios, PRTG, Zabbix, backup software and building systems all send email alerts already. You change where those emails go, from the Opsgenie address to the new one. The tools, thresholds and checks you tuned over the years stay exactly as they are.

Reviewed by Rakesh Patel, Founder, Welco

Have your alert texts moved long before April 2027

Repoint one source today and test it.

Move my alert textsBook a demo

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing