OpsGenie to Spike Migration Checklist

Basic settings

Everything you need to start paging from Spike.

0 of 12 done

Stage 1

Export your setup from OpsGenie.Use the REST API to export your teams (GET /v2/teams), users (GET /v2/users), schedules (GET /v2/schedules), and escalation policies (GET /v2/escalations). The dashboard export gives only an iCalendar file, so the API is the complete source.
List the tools that send alerts to OpsGenie.Integrations cannot be exported, so note each tool and who owns it.

Stage 2

Create your account and invite your team.Start your free trial, which lasts 14 days and needs no credit card. Ask everyone to verify their phone number and email, because Spike alerts go to verified contacts. See adding team members and checking that your team is getting alerts.
Add an integration for each monitoring tool.Create a service, add the integration, and copy its webhook URL. See creating integrations and services.
Build your on-call schedules.Recreate each rotation as a layer, and use slots for time restrictions. Templates are available. See creating an on-call schedule.
Build your escalation policies.Add each schedule as a step, choose a channel for every step, and attach the policy to each integration. Templates are available. See creating an escalation policy.
Connect Slack or Microsoft Teams.The OpsGenie connection does not carry over, so install the Spike app or bot and choose the channels for incident alerts. See Slack and Microsoft Teams.
Ask everyone to set their alert preferences.Each person chooses how they are alerted, installs the mobile app, and adds Spike’s contact card so alerts get through Do Not Disturb. See notification numbers.

Stage 3

Test your setup.Send a test alert to each person (Settings, then Team, then Send test alerts), run Test Escalation on each policy, and trigger a test incident from each integration.

Stage 4

Run Spike alongside OpsGenie.Add the Spike webhook to each monitoring tool next to the OpsGenie one, then compare each day. Every OpsGenie alert should have a matching Spike incident that reaches the right people. Fix any gaps you find.
Cut over.Tell the team the date and what changes, remove the OpsGenie webhook from each monitoring tool, and turn off OpsGenie notifications. OpsGenie URLs stop working at the shutdown.
Cancel OpsGenie once you are confident.Do this well before April 5, 2027.

Add these when you need them, and skip any you do not use in OpsGenie.

Show the 8 optional steps

Recreate your routing rules and alert policies.Both become alert routing rules in Spike, and Title Remapper covers title changes. See alert routing rules.
Set repeat escalation, acknowledge timeout, and auto-resolve.Configure these on each integration to match what you used in OpsGenie. See repeat escalations and acknowledge timeout.
Create your teams.Multiple teams are available on the Business and Enterprise plans.
Set up Live Call Routing.If you use incoming call routing, connect a Twilio or Plivo number. See Live Call Routing.
Connect your ticketing tools and Playbooks.Connect Jira, ClickUp, or Linear, and use Playbooks in place of OpsGenie alert actions.
Replace heartbeats and maintenance windows.Spike has no heartbeat monitoring, so send alerts from a tool such as Cronitor or Healthchecks into a Spike integration. For recurring quiet periods, use an alert routing rule with a Time of day condition and the Ignore incident action.
Export your alert history.Atlassian deletes it at the shutdown, so save a copy if you need it for reports or audits.
Review the first week.Tune noisy integrations and acknowledge timeouts, and check the on-call shift report (available on Business plans and higher).