SIGQ, Inc., the developer of Incident Lake, is offering migration support to organizations using Opsgenie, which Atlassian will stop providing and supporting on April 5, 2027. Customers can build everything from on-call to ITSM with Incident Lake alone, or start by using Jira Service Management alongside Incident Lake and consolidate step by step. SIGQ has also published a page that explains how to approach the migration and the steps involved.
- Moving off Opsgenie: https://incidentlake.com/en/lp/opsgenie-migration
Opsgenie End of Support
Atlassian announced the end of Opsgenie on March 4, 2025, and ended new sales on June 4, 2025. According to Atlassian, Opsgenie can no longer be accessed after April 5, 2027, and any data not migrated to Jira Service Management will be deleted.
Choosing a Migration Path
Atlassian names Jira Service Management as the migration path. With Incident Lake, you can build everything from on-call to ITSM on Incident Lake alone. If you can't switch everything at once, start by using Jira Service Management alongside Incident Lake and consolidate step by step.
- Run everything on Incident Lake: With the on-call add-on, set up schedules, overrides, escalation and phone paging. Beyond incident response, Incident Lake covers problem management, change and release management, a service catalog and service requests, a self-service portal, IT assets and a CMDB, all on one shared record.
- Start alongside Jira Service Management: Migrate on-call and paging to Jira Service Management, and run first response, records and postmortems in Incident Lake. Response tasks can sync with Jira issues. Once your process is settled, you can migrate on-call to Incident Lake as well and run everything in one place.
What the Support Covers
- Deciding where paging goes: Decide whether to migrate on-call paging to Incident Lake now or keep it in Jira Service Management for the time being, then point alerts from monitoring tools such as Datadog, Grafana, Zabbix and Sentry to it.
- Setting up first response in Slack or Teams: Enable the agent and choose the channels where incidents are detected automatically.
- Importing past records: Import incident records exported from Opsgenie with CSV, and add postmortems and runbooks as knowledge so they can be matched against similar incidents.
- Starting small, then expanding: Check how it works with a single incident or one drill scenario, then extend to more teams and services.
On Annual plans, our forward deployed engineers (FDE) work with you from deciding where paging goes to importing past records. On the Free plan, you can connect one Slack or Teams workspace and one monitoring tool, and test it on your own incidents before signing a contract. For feature details, see the help center.
- Incident Lake help center: https://support.incidentlake.com/
About Incident Lake
Incident Lake is a service operations platform built around the incident, with everything running on one shared record. It covers an agent that runs first response in Slack or Microsoft Teams, problem, change and release management, a CMDB and impact map, service desk, task and improvement tracking, drills, regulatory reporting, and analytics with executive views.
It combines Otter, SIGQ's in-house AI model, with frontier models, and keeps one design principle: AI proposes, people decide. Incident Lake has received a SOC 2 Type 1 report, and SIGQ, the operator, is ISO/IEC 27001 certified. A Self-Hosted edition that runs inside the customer's own environment is also available.
- Website: https://incidentlake.com/en
About SIGQ, Inc.
SIGQ, Inc. is a startup based in Tsukuba, Japan, that develops, provides and supports the adoption of Incident Lake, a service operations platform built around the incident. Founded in August 2024, the company is led by Founder and CEO Takaaki Kanetsuki.
- Corporate website: https://company.sigq.io/
Contact
SIGQ, Inc., Marketing Department
Email: sales@sigq.co.jp
- Contact form: https://incidentlake.com/en/contact
Dates and terms are based on information published by Atlassian as of November 17, 2026. Source: Atlassian, “Opsgenie licensing” https://www.atlassian.com/licensing/opsgenie. Incident Lake features are based on the help center as of November 17, 2026. On-call is an add-on.
Opsgenie and Jira Service Management are trademarks of Atlassian. All other company and product names are trademarks or registered trademarks of their respective owners.
