Feature changes and deprecations in Compass
See a detailed comparison of Opsgenie features and their availability in Compass after migration. View which features are automatically synced, which require manual configuration, and which have been deprecated or replaced with alternative solutions.
Use this guide to understand how your alerts, notifications, integrations, and on-call configurations will function in Compass and ensure a seamless transition with minimal disruptions to your workflows.
Operations capabilities are not available in Compass Free. To access alerting, on-call scheduling, and other operations features, consider Standard or Premium plan.
Feature name | Included in Compass plan | Mapped feature/Workaround |
|---|---|---|
警告 | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
Notifications - Contact Methods | Email and mobile push- Available in all standard and premium plans in Compass Note - Mobile push requires users to even have a valid Jira licence. SMS - Unlimited support in Standard ,Premium Voice - Only available in Premium
| Auto-synced, but requires downloading the Jira mobile app and updating settings in the Migration Guide. New vCards available for SMS and Voice. |
Notifications - Notifications | All 8 alert notifications available in standard and premium plans in Compass | Auto-synced. No additional configuration required. |
Notifications - Quiet and Mute hours | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
Forwarding Rules - Forwarded to you and by you | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
Global Policies - Alert and Maintenance | Global Alert policies across premium only and Maintenance across all plans | Auto-synced. No additional configuration required. |
All schedules - All global and team schedule list page | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
All escalations - All global and team escalation list page | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
Integrations - Incoming | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
Integrations - Global | Available on Premium plan. | Auto-synced. No additional configuration required. |
Integrations - Outbound, bidirectional with ITSM | Available on Premium plan. | Auto-synced. No additional configuration required. |
Integrations - Advanced alert customization | Available on Premium plan. | Auto-synced. No additional configuration required. |
Integrations - With in-house/On-prem systems (OEC-Opsgenie Edge Connector) | Available on Premium plan. | Must be reconfigured as Jira Edge Connector (JEC) after migration. |
Incoming Call Routing | Not available in Compass. | Will be disabled on the migration date and deleted a month later. |
Jira Software and Jira Service Management Sync | Team-level features are available across all paid plans (Standard, Premium), while site-level features are only available in Premium. | Auto-synced. No additional configuration required. |
ChatOps - Incident Management (via Slack, MS Team and Zoom) | Not available in Compass. | Will not be moved and will stop working on migration date |
ChatOps Alert Management - (Integrations with Slack and MS teams) - Team Integrations | Available on Standard and Premium plans. | Must be re-authenticated. |
ChatOps Alert Management - (Integrations with Slack and MS teams) - Global Integrations | Available on Premium plan. | Must be re-authenticated. |
Heartbeat | Available on Premium plan. | Auto-synced but some addition work required in cases where heartbeat as emails are referenced to update the heartbeat email domain. |
ユーザー | All roles are available, except for Stakeholders, which are not supported. | Auto-synced. No additional configuration required. |
ロール | Available on Premium plan. | Auto-synced, but some custom roles for incidents aren't migrated, and certain "admin" rights need to be reassigned. |
ログ | Available in all plans. Premium+ user should be able to access the customer logs API | Auto-synced. No additional configuration required. |
GitLab | Available on Premium plan. | GitLab won't be auto-synced. You can configure it again in Compass. |
General - Timezone + Heartbeat configurations + Deleted Users + HIPAA | Managed through Atlassian account. HIPAA compliance is not supported. | These settings are available under Compass General settings. |
Central Notification Templates | Available on Premium plan. |
|
オンコール | Available on Standard and Premium plans. Routing rule - 1 per team in freeplan but rest have 100 per team Escalations - All plans have 300 policy per team and 50 rules per policy Schedules - Unlimited across all plans | Auto-synced. No additional configuration required. |
サービス | Available in all plans. | Auto-synced. No additional configuration required. |
Incident Rules | Not available in Compass. | Not available after migration. |
チーム メンバー | Available in all plans. | Auto-synced. No additional configuration required. |
Team Custom Roles | Available on Premium plan. | Auto-synced. No additional configuration required. Managing team members and incident configurations is deprecated and won’t be migrated. |
Team Policies (Alert and Notification policies) | Available on Premium plan. | Auto-synced. No additional configuration required. |
Maintenance team policies | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
操作 | Not available in Compass. | Not available after migration. |
インシデント | Not available in Compass. | Not available after migration. |
オンコール担当者 | Available on Standard and Premium plans. | Auto-synced. No additional configuration required. |
チーム | Available in all plans. | Auto-synced. No additional configuration required. |
Analytics | Available in Premium plan except for Notification analytics which is available starting from the Standard plan. | Auto-synced. No additional configuration required. |
Deprecated features in Compass
The following Opsgenie features won’t be available in Compass because they have been deprecated or replaced with better alternatives:
Incident Management and Incident Templates – Compass doesn’t support incident management workflows or templates.
Stakeholder Role and Stakeholder Communications – Stakeholder roles and communications are not available in Compass.
Opsgenie Actions and Incident Rules – These features are not supported in Compass.
Incoming Call Routing – Compass does not support incoming call routing.
Integrations like Microsoft Teams and Zoom – These integrations are not available in Compass.
Slack Multi-Tenancy – One Slack workspace cannot be connected to multiple Compass sites, and vice versa.
API Key Management – Replaced by Atlassian Authetication
Edge Encryption and Enterprise Readiness Features (BYOK and FedRAMP) – Compass does not support Bring Your Own Key (BYOK) encryption or FedRAMP compliance.
Data Residency – Compass is only supported in the US region.
Compass Components Cannot Be Managed via API – Unlike Opsgenie, Compass does not provide API support for managing components.
Mobile App Limitations – The Compass mobile app will only function if the user has a Jira Software or Jira Service Management license on the same site.
Team-level details like Activity Streams and Conferences – These features have been deprecated due to low usage in Opsgenie. Team-level operations activity hasn’t been included in Compass.
MSP (Managed Service Provider) – Opsgenie-to-Opsgenie integration, which was the backbone of all sub-accounts, is no longer supported. MSP was deprecated a few years ago. Until migration, you can continue accessing child accounts, but after migration, they’ll be converted to free accounts and require their own migration path.
Old versions of some Opsgenie features: Groups, Heartbeats V1, Policies V1
Groups have been repaced by teams. You can manually convert groups to teams using a single-click button on the Groups page before migration, or we’ll automatically convert them for you during migration.
Groups used as responders – Since groups will be converted to teams, schedule start and end notifications won’t be sent to all members, as the structure has changed.
Groups used in call routing integrations – If you forward an incoming call to a group, it will call each member sequentially until it runs out of users or reaches the call limit. This isn’t possible with a team-based setup. Instead, you’ll need to update an escalation whenever a user is added or removed.
Notification Policies are now at the Team Level. With the new version, notification policies are team-based. You can convert your global notification policies manually before or after migration using a button in Settings > Global Policies. If this isn’t done before Opsgenie shuts down, deprecated policy configurations won’t be carried forward.
If an alert is set up globally with multiple responder teams and no owner team, policies will be applied differently:
If no responder team is assigned, no owner team will be set, and no policy will be applied.
If two or more responder teams are assigned, no owner team will be set, and no policy will be applied.
If a single responder team is assigned, that team will become the owner team, and its team-based policies will apply.
Users will be informed of these changes as part of the migration process.
Heartbeats are now team-based
Heartbeats have moved to a team-based configuration. You must manually update your Heartbeat settings in Opsgenie > Settings > General > Heartbeat Configuration > Activate Heartbeat. This update can be done either before or after migration but must be performed manually.
この内容はお役に立ちましたか?