Skip to content
OpsGenieSpike

How to migrate from
Atlassian OpsGenie to Spike

Moving from Atlassian OpsGenie to Spike takes three steps: get ready, set up Spike, and switch over. After the first two, run both tools side by side until you are confident. Each step links to a resource with the details.

Read the full OpsGenie migration guide

The path in three steps

Download PDF

Step 1

Get ready

Learn how your OpsGenie setup maps to Spike, then take stock of what you have. Your schedules, escalation policies, routing rules, and integrations all have a Spike equivalent, and you can search any OpsGenie term in the concept mapping sheet. Export your teams, users, schedules, and escalation policies through the OpsGenie API, and list the tools that send you alerts. The Get ready steps in the migration checklist cover this.

Step 2

Set up Spike

Create your account, build your schedules and escalation policies, and connect Slack or Microsoft Teams. Use the dashboard, or build it as code with the Terraform provider, the Spike API, or the Spike MCP server. Then add each Spike webhook to your monitoring tools. The integration guide covers Datadog, Prometheus, AWS, Grafana, New Relic, Sentry, Azure, and Google Cloud, and shows what to do for other tools. The migration checklist lists every step.

Step 3

Switch over

Keep OpsGenie paging while Spike receives every alert, compare them each day, and move paging to Spike in phases. See the parallel run plan. When you are confident, turn off OpsGenie notifications, remove its webhooks from your monitoring tools, and cancel OpsGenie well before April 5, 2027.

Choose your path

  • A small team that prefers the dashboard.Start with the migration checklist and build your schedules and escalation policies in the dashboard. Our team can also import them for you.
  • A DevOps or SRE team that prefers code.Create your services, escalation policies, integrations, routing rules, and schedules with Terraform, the Spike API, or the MCP server. Each integration returns its webhook URL, so you can pass it straight to your monitoring config.
  • A larger or more complex setup.Book a call with our team, and we will help you map your setup.

Also useful

Moving off OpsGenie?
You don’t have to figure it out alone.

Book a call and we will help you map your schedules, escalation policies, and integrations.

Spike incident timeline showing an alert escalating through on-call responders

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh