Thanks for attending Opsgenie Migration Office Hours - October 7 recording & follow up

[Brennan Kiely]

Hi Community,

Thank you for taking the time to attend our Opsgenie Migration Office Hours on [date]!

We look forward to continuing to work with you to ensure a smooth transition from Opsgenie.

Recap & follow up questions:

We went through a demo of scheduling the migration and showed some features that have been added to JSM Operations that aren't available in Opsgenie.

If there are issues scheduling the migration or any additional questions, please reach out to support through our portal.

You will need to be an Opsgenie Owner and an Atlassian Site/Billing Admin to see the migration page.

If you pay for Opsgenie or JSM through one of our partners, they will need to take action in their partner portal to enable the migration for your account.

If you would like to use the migration demo site with your production configuration in place, you can use our backup tool to move your configuration to the demo Opsgenie site that was created. The page says that the tool has been deprecated, but it still works.

After migration, Opsgenie will be fully available alongside JSM Operations for 120 days. Our engineering team can extend this time and we suggest reaching out around the 100 day mark if you believe you will need an extension.

Our main doc still needs to be updated, but any integration API endpoints and existing Opsgenie Edge Connectors will continue to work after the migration and after Opsgenie EOL on April 4, 2027. There is no action needed to ensure these continue to work.

After Opsgenie EOL, the configuration API endpoints (teams, schedules, escalations, etc) will stop working and you will need to use the JSM Operations API at that point.

If you are migrating to Compass, Operations will also live in its own section within that app. The UI is similar to JSM, but we weren't able to cover it due to some technical issues.

Manual steps before/after migration:

There are some integrations that will not automatically copy over to JSM, but will still work through Opsgenie during the 120-day period. These include, Slack, MS Teams, and incoming call (if you are using a number provided by Atlassian/Opsgenie).

After migration, you will need to authenticate for Slack/MS Teams to continue using the integrations in JSM.

For incoming call, you will need to move the number to your own Twilio account. This can be done before the migration to ensure the integrations are brought over. This doc has details on setting up a number from your own Twilio account.

Incident rules will also need to be moved over to automations to automatically create incidents from alerts. These rules should all be simple to set up (When alert created > [match filters] > Create incident), but please reach out to support if any guidance is needed.

The Opsgenie app will remain available for push notifications during the 120-day window, but users will also need to install the Jira Cloud app and ensure that it is set up for alert notification. After the 120-day period, the contact numbers for voice and SMS will also change. We have a vCard available that contains all numbers that will be used to contact you. I mentioned that the app might have a link to this as well, but after testing again, that doesn't appear to be the case.

Enhanced features in JSM:

JSM now includes Rovo AI, which can be used to further reduce alert noise outside of alert deduplication. When the AI finds similar alerts, it will create an alert group, which can be used to quickly create an incident and track similar alerts.

The AI in JSM can also be used to expedite incident resolution by providing next steps in incident investigation based on previous incidents. Once the incident is closed, it can also create a full PIR for you.

A couple of our most-requested feature requests have also been added to JSM Operations.

• Users can now continue to get notified by alerts after they have been seen. This is configured on the users' alert notification preferences.
• Incident rules can now be used to create multiple open incidents at the same time. This will allow incident automation rules to be less complex than what was necessary in Opsgenie.

Recording:

View recording here. 

Best regards,

Brennan, Chris, and Don