• 使用を開始する
  • 関連ドキュメント

End of sales and support for Opsgenie

Atlassian will discontinue new sales of Opsgenie on June 4, 2025 and end support for Opsgenie on April 5, 2027. Read the full announcement and learn about next-generation incident response options via Jira Service Management and Compass.

Data encryption after migration

Opsgenie’s edge encryption is no longer available

  • You can use Atlassian’s BYOK (Bring your own key) encryption as an alternative to edge encryption if you’re migrating to Jira Service Management Enterprise plan. Compass doesn’t offer an alternative solution at this time.

  • BYOK encryption can only be enabled on a new site. You should contact support to get support team to create a BYOK-enabled site for you. In this case, you cannot migrate your data automatically with Opsgenie’s migration tool. You must migrate your data manually.

  • Regardless of whether you are migrating to Jira Service Management or Compass, your previously encrypted alerts will remain encrypted during the migration and cannot be decrypted.

Data encryption in Opsgenie transitions differently depending on whether you're migrating to Jira Service Management or Compass. In Jira Service Management we recommend using edge encryption with Bring Your Own Key (BYOK) encryption, Compass doesn’t currently support an alternative for this functionality. Read more about BYOK encryption.

Migration summary

Is this feature fully available in all Jira Service Management and Compass plans?

Jira Service Management supports encryption through BYOK in Enterprise plan. Compass doesn’t currently offer an alternative for edge encryption.

Is this feature auto-synced after data migration?

Opsgenie data that was previously encrypted remains encrypted after migration, except for the fields that were never encrypted such as alias, message, tags, and priority. You can’t continue to receive encrypted alerts unless you enable BYOK encryption in a new Jira Service Management instance.

Are there required actions for full workflow parity?

If you want to enable edge encryption post-migration, you must manually migrate your data to a BYOK-encrypted Jira Service Management site. If you’re migrating to Compass or an existing Jira Service Management site, you won’t be able to replace edge encryption with BYOK.

変更内容

Jira Service Management replaces edge encryption with BYOK encryption

If encryption is required, you can configure BYOK encryption in Jira Service Management to replace edge encryption. To migrate to a BYOK-enabled Jira Service Management site, contact Atlassian Support to request a destination site that supports BYOK encryption. Even if you have an existing Jira Service Management site, you must migrate to a new Jira Service Management site that supports BYOK. It can’t be enabled on an existing site.

Review your security policies to ensure that BYOK encryption settings align with your organization’s security requirements.

Read more about BYOK encryption.

Compass doesn’t support edge encryption or BYOK

Similar to Jira Service Management, once migrated, encrypted data from Opsgenie remains encrypted in Compass, and there is no way to decrypt it. The only unencrypted fields are alias, message, tags, and priority, which were already unencrypted in Opsgenie.

If encryption is critical to your workflows, consider migrating to a Jira Service Management plan instead of Compass.

 

さらにヘルプが必要ですか?

アトラシアン コミュニティをご利用ください。