> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/knowledge-base/getting-started-and-onboarding/opsgenie-migration-faq.md). # Opsgenie migration FAQ Short answers about moving from Opsgenie to ilert — what migrates, what does not, and the quickest way to start. Short answers to the questions Opsgenie customers ask most. For the full procedure, see [Migrate from Opsgenie to ilert](/knowledge-base/getting-started-and-onboarding/opsgenie-to-ilert-migration-guide.md). ## Can we migrate from Opsgenie to ilert? Yes. Atlassian stopped selling Opsgenie on June 4, 2025, and shuts off access to it on April 5, 2027. Every part of an Opsgenie setup has a home in ilert — see [How Opsgenie maps to ilert](/knowledge-base/getting-started-and-onboarding/opsgenie-to-ilert-migration-guide.md#how-opsgenie-maps-to-ilert) — and ilert's migration assistance is free. ## What is the quickest way to migrate? Let a coding agent do it with the [ilert CLI](/developer-docs/client-libraries/ilert-cli/migrate-to-ilert.md). The CLI ships a playbook for Opsgenie: the agent reads your configuration through the Opsgenie API, shows you the plan, and creates the ilert objects once you approve it. See [Migrate with the ilert CLI](/knowledge-base/getting-started-and-onboarding/opsgenie-to-ilert-migration-guide.md#migrate-with-the-ilert-cli). ## What can be migrated? Your configuration: * users, teams and their roles * on-call schedules, rotations and overrides * escalation policies * integrations, which become alert sources * services, status pages, heartbeats and maintenance windows * incoming call routing, which becomes call flows A few objects change shape on the way, and some of those changes decide who gets paged. See [Differences that change behavior](/knowledge-base/getting-started-and-onboarding/opsgenie-to-ilert-migration-guide.md#differences-that-change-behavior). ## What cannot be migrated? * **History.** Past alerts and incidents stay in Opsgenie. Save what you need before April 5, 2027. * **Integration keys.** Every alert source gets a new one, so every tool that sends alerts has to be re-pointed. * **Your call routing phone number.** Numbers cannot be ported into ilert, so your call flows get a new one. ## What is the process for migrating integrations? Each Opsgenie integration becomes an ilert alert source with a new integration key, so every tool that sends alerts to Opsgenie has to be pointed at ilert: * **Monitoring tools** — replace the Opsgenie endpoint with the alert source's URL or key. Where ilert has an integration for the tool, use it rather than a generic API alert source. * **Scripts and pipelines that call the Opsgenie Alert API** — rewrite them for the ilert Events API. The fields differ, not just the URL: see [Rewrite scripts that call the Opsgenie Alert API](/knowledge-base/getting-started-and-onboarding/opsgenie-to-ilert-migration-guide.md#rewrite-scripts-that-call-the-opsgenie-alert-api). To avoid switching everything on one day, forward your Opsgenie alerts into ilert with the [Opsgenie integration](/integrations/inbound-integrations/opsgenie.md) while you re-point tools one at a time. ## How do I get started? Pick a route in [Choose how to migrate](/knowledge-base/getting-started-and-onboarding/opsgenie-to-ilert-migration-guide.md#choose-how-to-migrate). For help planning, email — the assistance is free, and includes a review of your configuration and help with the setup. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ilert.com/knowledge-base/getting-started-and-onboarding/opsgenie-migration-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.