Advanced features
Migrating from Opsgenie
Atlassian stopped selling Opsgenie on June 4, 2025 and will shut it down on April 5, 2027. Parny includes a built-in migration that imports users, teams, integrations and on-call schedules from your Opsgenie account.
What the migration imports
Users — the people in your Opsgenie account.
Teams — your Opsgenie teams.
Integrations — the integrations your alerts come through.
On-call schedules — your Opsgenie schedules. Opsgenie limits how often a schedule can be read, so this step re-runs automatically, about a minute apart, until it finishes.
What you configure after the import
Rotations, escalation policies and notification settings are not migrated automatically. They are configured and validated with your team in Parny, followed by a final routing check: send a test alert through each integration before you move alert routing.
Before you start
Create an API key in Opsgenie under Settings → App Settings → API Key Management. Only Opsgenie account owners and global admins can create API keys.
Run the migration
Step 1: Click the Organization Settings button at the bottom-left corner, then select “Manage Your Organization” from the pop-up menu.
Step 2: In the organization management menu, go to the “OpsGenie Migration” tab in the top bar.
Step 3: Click the “New API Key” button.
Step 4: Paste the API key you created in Opsgenie and click “Register”.
Step 5: Once your key is registered, you’ll see four migration options: Users, Teams, Integrations, On-call schedules.
Step 6: Run each option separately, or use “Migrate everything” to run all four in order. Items already migrated are skipped if you run a step again, and Parny shows what was migrated, skipped or failed.
Plan the cutover with our team
For timelines, a parallel run with Opsgenie and the 6-month Parny On-call offer for Opsgenie migration customers, see Opsgenie migration.
