Migrate from Compass to Jira Service Management
If your team plans to migrate operations capabilities from Compass to Jira Service Management, then the migration must be started before the end of your Compass contract or by the time Compass is no longer supported (December 31, 2027), whichever is earlier.
As Compass transitions to DX for catalog and scorecard functionality, Alerts and On-Call will continue to be available in Jira Service Management (now part of Service Collection), where you will be able to keep your existing workflows and configurations intact once you purchase a license.
Only Atlassian admins can migrate and sync data from Compass into Jira Service Management.
Syncing data between Compass and Jira Service Management
Operations is a platform-wide capability across Atlassian apps, meaning that Jira Service Management and Compass share the same backend. Most Compass alerting and on-call data, such as alerts, on-call schedules, and escalation policies, will automatically synchronize into Jira Service Management when added to an Atlassian site that already has Compass.
How is data synced from Compass to Jira Service Management?
A Compass catalog contains components, some of which are of type Service. When Jira Service Management is purchased and added to an Atlassian site that already has Compass, all Compass components of type Service are automatically synced into Jira Service Management as services.
Once the Compass components have been synced as services, these operations features become available in Jira Service Management automatically:
Alerts
Note: Alerts created in the Compass UI or Compass Ops API are synced with Jira Service Management. Alerts created from Compass integrations are not synced.
On-call (scheduling and policies)
Member roles
Notification preferences
Audit logs
Alert policies (only in Jira Service Management Premium)
Notification policies (only in Jira Service Management Premium)
Global policies, maintenance, and configuration
REST APIs
Team maintenance
Team sync
What data is not synced between Compass and Jira Service Management?
There are three areas that are not synced automatically when Jira Service Management is added to an Atlassian site with Compass on it:
1.Alerts and attached components or services
When an alert is created in Compass, the relevant component can be linked to that alert. Although the alert becomes available within Jira Service Management, the linked component/service is not attached to it.
To ensure services are properly attached to incoming alerts, they should first be connected to integrations. When setting up integrations in Jira Service Management and creating alerting rules, you can connect any relevant Affected Services imported from Compass.
If you need to re-attach services to previously created alerts, navigate to Alerts within Jira Service Management and open any relevant alerts.
On the right side, select Affected Services, then + Add a Service, then type in and select the correct service.
2. Component Owner or Service Responder team
Each service within Jira Service Management has a Responder Team – the team that is alerted if the service has an issue. In Compass, each component has an Owner Team. The Responder Team is not necessarily always the same as the Owner Team for a service, and so that property is not carried over from Compass to Jira Service Management.Read how to add and manage incident responders in Jira Service Management
3. Integrations
Forge integrations set up in Compass will not be synced to Jira Service Management. They will need to be added and configured to Jira Service Management. Read how to add an integration at the team level
Ready to migrate?
To begin the migration to Jira Service Management, please reach out to your Account Representative - they can help provision Jira Service Management and discuss pricing details with you. For other questions about Jira Service Management, please reach out to our support team.
Was this helpful?