# Migrate to Jira Service Management

Source: https://www.youtube.com/watch?v=BRkYpKNJjPM
Recap page: https://rapidrecap.app/video/BRkYpKNJjPM
Generated: 2025-11-12T19:03:59.834+00:00

---
## Quick Overview

Jira Service Management (JSM) allows teams to migrate from Opsgenie while maintaining alerting and on-call features, providing expanded incident management capabilities, advanced automations, AI operations, and seamless integration with over 200 monitoring tools, all without downtime during the transition process.

**Key Points:**
- The migration from Opsgenie to Jira Service Management is presented as a fully automated process requiring no downtime for ongoing operations.
- JSM retains key Opsgenie features like integrated alerting and on-call management, which are shown in the new interface (00:03, 01:00).
- JSM offers robust incident management capabilities, including advanced automations and AI Operations, available in Premium and Enterprise plans (01:14).
- Teams can customize roles, set up alert/notification policies, and configure incoming call routing within JSM (01:50, 01:54, 02:08).
- Rovo agents assist by identifying probable root causes, suggesting resolutions, and generating first drafts of post-incident reviews (3:13, 3:37).
- After migration, users can run both Opsgenie and JSM in parallel for up to 20 days to ensure consistent coverage before turning off Opsgenie (04:06, 04:54).

![Screenshot at 00:01: Visual demonstration of dragging an item from an external source \(indicated by a LinkedIn icon\) into the Jira Service Management list, illustrating the integration capabilities.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-00-01.png)

**Context:** This video serves as a tutorial demonstrating the process and benefits of migrating incident management operations from Atlassian's Opsgenie platform to Jira Service Management (JSM). It emphasizes that the move is seamless, preserving essential alerting and on-call functionalities while integrating newer, more advanced features specific to JSM, such as AI-driven incident analysis and automated post-incident reporting.

## Detailed Analysis

The video confirms that migrating from Opsgenie to Jira Service Management is a fully automated process that ensures zero downtime for ongoing operations (00:18). JSM incorporates core Opsgenie functionalities such as centralized Alerts, On-call scheduling, and Incident management (00:06). Key features highlighted for JSM Premium and Enterprise plans include Advanced Automations and AI Operations (01:14). The platform allows for granular control over alert delivery via customizable alert and notification policies (01:52), and management of incoming call routing (02:08). Furthermore, the integrated agent, Rovo, accelerates resolution by suggesting root causes, providing recommendations based on past incidents, and automatically generating first drafts of Post-Incident Reviews (PIRs) (03:13, 03:37). Teams can integrate with over 200 tools via the Sync tab (01:40). During the transition, users can run both the old Opsgenie site and the new JSM instance in parallel for up to 20 days to maintain consistent coverage before finalizing the switch by turning off Opsgenie (04:06, 04:50).

### Migration Overview

- Automated transition from Opsgenie to JSM
- Zero downtime guaranteed
- Continued support for existing alerting/on-call features

### JSM Incident Management Capabilities

- Access to Advanced Automations and AI Operations (Premium/Enterprise)
- Integration with 200+ monitoring tools (01:40)

### Configuration Parity

- Ability to set up routing rules, escalation policies, and on-call schedules similar to Opsgenie (01:32)

### Rovo Agent Assistance

- Agent provides context-aware suggestions for root cause analysis and recommends playbook actions for faster resolution (03:13
- 03:32)

### Post-Incident Review (PIR)

- Rovo automatically generates the first draft of the PIR from incident details, saving significant time (03:35)

### Coexistence Period

- Ability to run both Opsgenie and JSM in parallel for up to 20 days for dual coverage during setup (04:06
- 04:55)

![Screenshot at 00:01: Demonstration of dragging an alert/item into the Jira Service Management view, symbolizing the integration of external data.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-00-01.png)
![Screenshot at 00:06: Visual representation of the three core operational capabilities in JSM: Alerts, Incidents, and On-call.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-00-06.png)
![Screenshot at 00:14: Clicking the 'Migrate' button to initiate the transfer process from Opsgenie to Jira Service Management.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-00-14.png)
![Screenshot at 01:30: The JSM interface showing the 'payment-incident-response-team' overview, highlighting On-call scheduling, Routing rules, and Escalation policies tabs.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-01-30.png)
![Screenshot at 01:39: Display of the Integrations tab showing available connectors, emphasizing connectivity with over 200 tools.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-01-39.png)
![Screenshot at 02:02: The 'Create custom role' dialog box, showing granular permissions that can be defined for users beyond default roles.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-02-02.png)
![Screenshot at 03:24: The Alerts view in JSM where similar alerts are actively grouped, reducing noise and improving triage efficiency.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-03-24.png)
![Screenshot at 03:44: The browser tab showing the Opsgenie interface being viewed concurrently with JSM during the parallel run period.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-03-44.png)
![Screenshot at 04:21: The 'Migration Guide' sidebar open, displaying a checklist of actions remaining for the user to complete the transition.](https://ss.rapidrecap.app/screens/BRkYpKNJjPM/00-04-21.png)