What the Opsgenie shutdown means for your Slack on-call handle

Atlassian is shutting down Opsgenie on April 5, 2027. After that date the product is gone, and any data you haven't moved gets deleted.

Most of the migration guides are about alerts and escalation policies, which makes sense. Those wake people up. But there's a quieter thing that's easy to forget until the morning it breaks. Somebody in #support types @platform-on-call and nobody answers.

Tellspin keeps Slack handles like that one in sync with Opsgenie, so here's what I'd check.

Find everything that reads from Opsgenie

Your alerts aren't the only thing using your schedules. Before you pick a replacement, list what else depends on them.

• Slack user groups kept up to date by an app or a script
• /genie whoisoncall in people's muscle memory
• Scripts and bots that call the Opsgenie API
• Calendar feeds people subscribed to
• Runbooks and channel topics that say who to contact

Atlassian's migration moves your Opsgenie data. It won't fix a script somebody wrote three years ago that calls api.opsgenie.com. That script will just stop working.

Ask whether you need paging at all

This is the question I'd ask first. Some teams use Opsgenie to page people when production breaks. Others mostly use it to keep track of whose turn it is. Those are very different problems, and the second one doesn't need a paging tool.

If an alert wakes someone up at 3 a.m., you need a real replacement. Atlassian points you to Jira Service Management or Compass, and there are plenty of other paging tools to compare.

If nothing pages you, this is a good moment to stop paying for a tool built for something you don't do.

Keep the handle the same

Whatever you move to, keep the handle. People have spent years learning that @platform-on-call is how you reach the right person. That habit is worth more than any feature. If the name stays the same, nobody outside your team has to know you migrated.

So try to avoid a gap. Run the new schedule next to the old one for a few weeks and check that both agree on who is on call before you turn Opsgenie off.

Where Tellspin fits

Tellspin is my product, so keep that in mind. It keeps a Slack user group pointed at the right person. Paging isn't in it yet, so if alerts need to wake someone up, I'd have a paging tool lined up before April.

I'm building Slack-first paging. Email me at dan@tellspin.com if you want to hear when it's ready.

Here's what that means for each path off Opsgenie.

• You only use Opsgenie for the rotation. You can build the rotation in Tellspin and keep your handle.
• You're moving to PagerDuty or Datadog On-Call. Tellspin syncs both, so you point the same handle at the new schedule.
• You're moving to Jira Service Management or Compass. Tellspin can't read those schedules today. If that's you, email me at dan@tellspin.com, because it tells me what to build next.

If you already sync a schedule from Opsgenie, that sync stops when Opsgenie does. Move it before April 5.

You can read more about syncing Opsgenie to Slack, or see how the integration works.