Migrating from Opsgenie

Opsgenie is shutting down in April 2027. As of February 2026, new sales have ended (since June 2025) and Atlassian is actively migrating customers. Start planning your migration now. See our Opsgenie Alternative page for a full comparison.

Overview

This guide helps you migrate from Atlassian Opsgenie to NearIRM. The migration focuses on recreating your critical alerting configuration.

Time estimate: 1-2 hours for a typical setup

Concept Mapping

Understanding how Opsgenie concepts translate to NearIRM:

What's Different

Unified policies: Opsgenie separates Alert Policies (filtering) from Escalations (routing). NearIRM combines these into a single Notification Policy with matching rules and escalation steps.

Simpler routing: Instead of routing alerts through integrations to teams to escalations, NearIRM routes directly from policy to target.

Migration Checklist

1. Create Teams

For each Opsgenie team:

• Create team in NearIRM (Teams > Create Team)
• Add team members
• Note which escalations reference this team

2. Create Schedules

For each Opsgenie schedule:

• Create schedule in NearIRM (Schedules > Create Schedule)
• Set rotation start day/time
• Add teams in rotation order
• Create overrides for current exceptions

Note: Opsgenie's time-based restrictions (on-call only during certain hours) translate to schedule design. Use weekly rotations with overrides for complex patterns.

3. Create Integrations

For each Opsgenie integration:

• Create integration in NearIRM (Settings > Integrations)
• Choose Grafana or Generic type
• Copy the new webhook URL

4. Create Notification Policies

For each Opsgenie escalation:

• Create policy in NearIRM (Policies > Create Policy)
• Add matching rules based on Opsgenie's alert policies
• Add escalation steps matching Opsgenie's escalation rules
• Set timeouts to match Opsgenie's "escalate if not acked" settings

5. Update Monitoring Tools

For each integration:

• Update your monitoring tool with new webhook URL
• Test with a manual alert
• Verify alert appears in NearIRM

6. Configure User Preferences

Each team member should:

• Log in to NearIRM
• Configure notification channels in Settings > Preferences
• Set up WhatsApp if using

Example Migration

Opsgenie Setup

• Integration: "Grafana Production"
• Team: "Platform Engineering"
• Escalation: "Platform Escalation"
  • Rule 1: Notify schedule "Platform On-Call" (5 min)
  • Rule 2: Notify team "Platform Leads" (15 min)

NearIRM Equivalent

Integration: "Grafana Production" (Grafana type)

Schedule: "Platform On-Call"

• Weekly rotation of Platform Alpha, Platform Beta

Policy: "Platform Alerts"

• Matching Rules: label team = platform
• Step 1: Schedule "Platform On-Call", 5 min timeout
• Step 2: Team "Platform Leads", 15 min timeout

Key Gotchas

No Responders

Opsgenie's "Responders" concept (multiple notification paths) maps to multiple escalation steps in NearIRM. Configure each responder as a step in your policy.

No Alert Actions

Opsgenie's custom alert actions (buttons that trigger webhooks) don't exist in NearIRM. Actions are limited to Acknowledge and Resolve.

No Heartbeat Monitoring

Opsgenie's Heartbeat feature doesn't exist. Use your monitoring tool's heartbeat alerting instead.

Simpler Schedules

NearIRM has weekly team rotations. Opsgenie's complex rotation types (daily, custom) need simplification.

Migration tip: Most teams using complex rotations can simplify to weekly without issues.

What NearIRM Does Better

• No Atlassian tax - Simple pricing, no enterprise upsell
• Faster configuration - Less clicking through nested menus
• Essential features - What you actually use daily
• Modern stack - Built for today's DevOps workflows

Need Help?

Migration support is included. Email [email protected] with:

• Your current Opsgenie setup (export or screenshots)
• Questions about mapping specific configurations

---

See also: Opsgenie Alternative — Full Comparison