Moving off Opsgenie? We’ll help you migrate to Moneat.
Opsgenie support ends on April 5, 2027. If you’re looking for a replacement, we can help you move your on-call setup to Moneat.
We’ll go through your schedules, escalation policies, and alert integrations with you, work out what needs manual setup, and help you test everything before you switch. You can keep using your existing monitoring tools.

What needs to move
Start with the people and rules you rely on today: who’s on call, when their shifts change, who covers an override, and who gets notified if the first person doesn’t respond. Moneat can read your users, teams, schedules, rotations, overrides, escalation policies, priorities, and the next two weeks of coverage directly from Opsgenie.
On Settings › On-call Migration, choose Opsgenie, paste an API key with Read and Configuration Access, and pick your region. The read runs in the background, and Moneat emails you when it’s ready to review.
The review shows what Moneat will create, matches people to your members by email, and lists anything it couldn’t carry over. Importing creates the schedules, layers, overrides, escalation policies, and teams your plan supports. The policies stay as drafts until you enable mirroring or switch paging over. We’ll help you check for missing settings and gaps in on-call coverage.
Each responder still needs to set their contact methods and notification rules under Paging. Historical alerts and incidents aren’t imported, so export any history you want to keep before your Opsgenie site closes.
Moneat keeps your API key encrypted only until the read finishes, for at most 7 days, and you can remove it sooner. Revoke the key in Opsgenie once the migration is done.
Check when your Opsgenie site will close
Opsgenie’s REST APIs remain available until April 5, 2027, but your own site may close earlier. After a migration to Jira Service Management, the site shuts down automatically after 120 days, and an administrator can close it sooner. Check your site’s shutdown date before planning exports or a fallback to Opsgenie.
Set up your alerts and try them
Each monitoring tool that sends alerts to Opsgenie needs a connection and routing rule in Moneat. Keep the same deduplication key on an alert’s trigger and recovery events so they can be matched.
Once the schedules and alert sources are set up, agree on a test window with your team. Choose Mirror before switching to let the imported policies page for alerts sent through your Moneat routes while Opsgenie keeps paging too. Do this only if duplicate notifications are safe and everyone knows which ones to acknowledge.
For each alert route, send a test event and check:
- The alert arrives with the details you expect and reaches the person currently on call.
- The schedule hands over to the right person at the next shift, including any overrides.
- Every notification channel your team uses works: SMS, voice, push, email, or Slack.
- If nobody responds, the alert escalates to the right people after the right delay.
- You can acknowledge, resolve, reassign, and manually escalate the alert.
- Repeated events stay grouped, recovery events match the alert, and retries don’t send duplicate pages.
Before switching a source, write down how to point it back to Opsgenie if something goes wrong. Move one source first and watch real alerts come through before moving the rest. You can cut over or roll back from Settings › On-call Migration; reconnecting the alert sources is still a separate step.
Is Moneat the right fit?
If your team already uses Atlassian heavily, Jira Service Management may be the easiest move. Atlassian automates much of that migration, though some accounts need manual steps. incident.io is another option worth comparing.
Moneat makes sense if you want your on-call and incident response tools alongside the errors, logs, traces, metrics, and monitors behind your alerts. Our pricing page has the current plans and responder allowances.
Want a hand?
Tell us about your Opsgenie setup. We’ll help you review the import, work out what needs setting up separately, and plan the checks your team needs before switching.
Keep reading
Migrate from Sentry to Moneat: what changes and what doesn’t
A staged guide to moving supported Sentry SDK telemetry to Moneat, including validation, source maps, alerts, historical data, and rollback.
Use Moneat with your existing Sentry SDKs and Datadog Agents
Keep existing instrumentation for supported signals, point it at Moneat, and verify the configuration and workflow differences before switching.