When does OpsGenie shut down?
Atlassian scheduled OpsGenie's end of life for April 2027. New sales stopped in June 2025, and teams bundled through Jira Service Management lost OpsGenie access in October 2025. After April 2027, all OpsGenie APIs, integrations, on-call schedules, and status pages stop working.
What does the white-glove migration include?
Send us your OpsGenie export (or a screen-share). Within 48 hours we recreate your monitors and heartbeats, escalation policies, on-call schedules, alert routing (Slack, Teams, SMS, voice), and your status page in Hyperping — then walk you through everything in a 30-minute handover call. It's free on any paid plan.
Can I run OpsGenie and Hyperping in parallel?
Yes, and we recommend it. Hyperping's native OpsGenie integration lets you send alerts to both systems during the transition, so you can validate routing against your existing setup before cutting over.
How long does the migration take?
We deliver your rebuilt setup within 48 hours of receiving your OpsGenie configuration. Most teams then run both platforms in parallel for one to two weeks before fully cutting over.
Why not migrate to Jira Service Management?
JSM is Atlassian's recommended path, but per-agent pricing starts at $17.65/month — nearly double OpsGenie's Essentials plan — and it still has no built-in monitoring, so you keep paying for a separate tool. Hyperping replaces the monitoring tool and OpsGenie in one flat-priced platform.
What should I export from OpsGenie before the shutdown?
Alert history can be exported as CSV from the alert list or Analytics reports. On-call schedules, escalation policies, routing rules, and your integration list don't export from the UI, so pull them as JSON through the OpsGenie API (the schedule, escalation, and policy endpoints) while it's still available. Even if you don't migrate right away, exporting early protects you — Freshping users who waited lost their data permanently.