Thanks for attending Opsgenie Migration Office Hours - November 11th recording.

[#1]

Hi folks, 

Thanks to those who registered for and attended the second session of Opsgenie Migration office hours! It's our pleasure to host these sessions & provide support to our community. Thank you for your time! 

November 11th - Recording 

After each session, we'll post a wrap-up and answer unanswered questions in the Opsgenie Migration group.

Thank you for raising these important questions about the Opsgenie to Jira Service Management (JSM) migration.

Question: Can we still view historical alerts, previous schedules & overrides after the migration?

Answer:

1. Access to Historical Alerts:
After migrating from Opsgenie to JSM, you will still be able to view your historical alerts within JSM. All existing alerts are automatically migrated and accessible under the Operations > Alerts section. However, please note that JSM enforces data retention policies based on your subscription plan (ranging from 1 month to 5 years). If you require access to alerts beyond your plan’s retention period, we recommend exporting any critical data before migration.

2. Viewing Previous Schedules and Overrides:
Your on-call schedules and overrides are also migrated to JSM. You can view both current and past on-call schedules, including overrides, through the On-call dashboard in JSM. This allows you to see who was on-call at any given time, provided the data falls within your plan’s retention window. For longer-term audit or compliance needs, consider exporting this information prior to migration.

Question: What happens to my Saved Searches, Services, and Heartbeats when migrating from Opsgenie to Jira Service Management? 

Answer:
1. Saved Searches:
All your saved searches from Opsgenie are migrated to JSM. You’ll find them available in the JSM Alert List Page, with permissions and filters preserved. This ensures you can continue using your existing searches seamlessly after migration.

2. Services:
Services are migrated to Assets (formerly Insight) within JSM. After migration, Assets becomes the primary location for managing all your service-related data, including stakeholders and responders. This transition ensures a unified and robust service management experience.

3. Heartbeats:
Heartbeats are also migrated and kept in sync during the transition. Please note that the heartbeat email domain will change in JSM, so you may need to update any references to heartbeat emails in your monitoring systems. While the global view of heartbeats from Opsgenie isn’t directly available in JSM, all core heartbeat functionality continues to be supported.

Question: Will our existing incident templates in Opsgenie be migrated automatically to Jira Service Management (JSM) as part of the OG to JSM migration? 

Answer: Incident templates from Opsgenie are not migrated to JSM at this time.
Currently, JSM does not support the automatic migration of incident templates. If you have custom incident templates in Opsgenie, these will not be transferred as part of the migration process. You will need to manually recreate any templates you require in JSM.

Don't hesitate to sign up for another session! We look forward to seeing you. 

Thanks again, 
Mubeen & Siddhartha.