Skip to main content
Squasher has no importer for Opsgenie. You recreate your schedules by hand, and you point your alert sources at Squasher, where each alert opens an incident.

​
What moves and what does not

Squasher uses a schedule to show who is on call now. When AI triage fails on an issue or an incident, Squasher assigns it to that person.
Squasher does not call, text, or push to responders. If your team needs phone or SMS paging, keep a paging tool and send Squasher incidents to it with the PagerDuty destination.

​
Run both tools side by side

Keep Opsgenie paging while you set up Squasher. In each alert source, add the Squasher connector as a second target next to Opsgenie. For example, add a second integration to a Grafana contact point, or a second receiver in Alertmanager. See Inbound alert connectors.

​
Recreate your schedules

1

List what you have

For each Opsgenie schedule and layer, write down the members in order, the handoff day and time, and the time zone.
2

Create the schedule in the dashboard

  1. Select On-call in the sidebar, then select Create schedule.
  2. Enter a Name, select the Rotation members, and set the Timezone.
  3. Select Create.
The dashboard hands off every Monday at 09:00 in that time zone. It cannot edit a schedule after you create it.
3

Use another handoff time

To choose the day, the time, or the order of members, create the schedule with the Squasher CLI:
--handoff-day is 0 for Sunday through 6 for Saturday. List the members in rotation order. squasher on-call members --schedule <schedule-id> shows the user IDs in a schedule.
4

Add overrides

Each responder must have a Squasher account in your organization before you add them. The CLI reads the project from SQUASHER_PROJECT_ID, or from --project.

​
Move alerts and on-call

  1. Connect each alert source with an inbound alert connector.
  2. Recreate your Opsgenie heartbeats as heartbeat monitors, and point your jobs at the new URLs.
  3. Recreate your notification channels as destinations and routes: Slack, email, Telegram, webhook, or PagerDuty.

​
Check parity

  • squasher on-call current names the same person as Opsgenie.
  • squasher on-call calendar --schedule <schedule-id> shows the same shifts for the next weeks.
  • A test alert from each source opens an incident in Squasher and reaches the right channel.
  • Every responder can sign in to Squasher.

​
Turn off Opsgenie

  1. Remove Opsgenie from each alert source. Keep the Squasher connector.
  2. Turn off the Opsgenie heartbeats after the Squasher heartbeat monitors have run for one week.
  3. Turn off the Opsgenie schedules after one week without missed alerts.

​
Next steps

On-call

Learn how rotations and handoff work.

Inbound alert connectors

Open incidents from your monitoring tools.

Set up notifications

Route incidents to Slack, email, or PagerDuty.

CLI reference

Get the CLI and see every on-call command.