DEV Community

Cover image for Opsgenie Schedule Export and Calendar Sync: Every Option
Yathartha Shekhar
Yathartha Shekhar

Posted on Originally published at fluidify.ai

Opsgenie Schedule Export and Calendar Sync: Every Option

Cross-posted from the Fluidify blog.

There are three reasons to get your on-call schedules out of Opsgenie: so engineers see their shifts in Google Calendar or Outlook, so you have a backup, and because Opsgenie shuts down on April 5, 2027 and the schedules have to go somewhere. This guide covers every Opsgenie schedule export option, from the one-click calendar subscription to the Schedule API, what each one keeps and loses, and how to sync or move schedules into another tool.

Key takeaways

  • Opsgenie calendar sync works through iCalendar (.ics). Each user can subscribe to their own schedule with "Open calendar" or download a file with "Export team schedule," and the API exposes the same export at GET /v2/schedules/:identifier.ics.
  • An .ics export holds the resulting shifts (who, when), not the rotation rules that produce them. To rebuild a schedule in another tool, export the schedule and rotation definitions as JSON through the API too.
  • If you're migrating, an importer that reads Opsgenie's API is faster and more accurate than recreating schedules from calendar files. Check exactly which objects it reads, since overrides and time restrictions are the usual gaps.

Opsgenie schedule export options at a glance

Method What you get Best for
Open calendar (subscription) A live calendar feed of the current month, refreshed monthly Engineers seeing their own shifts
Export team schedule (download) A one-time .ics file of the current month from today Quick snapshot of a schedule
Schedule API .ics export An .ics file per schedule, scriptable Bulk backups
Schedule timeline API JSON of who is on call over a time window Reporting, payroll, audits
Schedule and rotation API JSON of the rotation rules themselves Rebuilding schedules in another tool

Sync your Opsgenie schedule to Google Calendar or Outlook

This is the option for day-to-day visibility, so each engineer sees their shifts next to their meetings.

  1. In Opsgenie, open your schedules from When am I on-call in the profile menu, or Your on-call schedule in Settings.
  2. Select Open calendar on the schedule's icon bar and confirm.
  3. Your calendar app adds the feed as a subscribed calendar.

According to Atlassian's documentation, this adds the current month starting from today, and Opsgenie keeps exporting the schedule each month so the calendar stays current. Your calendar app must allow adding external calendars. Google Calendar and Outlook refresh subscribed calendars on their own schedule rather than instantly, so a last-minute override can take a while to show up. Treat the calendar as a convenience view and Opsgenie as the source of truth.

To subscribe to someone else's schedule, such as a team rotation, use Open calendar on that schedule instead of your own.

Download an Opsgenie schedule as an .ics file

Select Export team schedule on the schedule's icon bar to download an iCalendar file you can import into any calendar tool. Atlassian's current docs say this covers the current month of the schedule starting from today. Older Opsgenie documentation and some third-party guides mention exports covering the next 12 months, so check the date range in your own file before relying on it for a backup.

A downloaded file is a snapshot. It won't update when the rotation or an override changes.

Export Opsgenie schedules with the API

For more than a handful of schedules, script it. The Opsgenie Schedule API has an export endpoint that returns an .ics file named after the schedule:

curl -s "https://api.opsgenie.com/v2/schedules/Platform%20Primary.ics?identifierType=name" \
  -H "Authorization: GenieKey $OPSGENIE_API_KEY" \
  -o platform-primary.ics
Enter fullscreen mode Exit fullscreen mode

identifierType can be id (the default) or name. EU accounts use https://api.eu.opsgenie.com instead. An Atlassian staff answer on the community forum says the webcal subscription link itself isn't available through the API, so the API gives you files, not live feeds.

To export every schedule in an account, list them first and loop:

curl -s "https://api.opsgenie.com/v2/schedules" \
  -H "Authorization: GenieKey $OPSGENIE_API_KEY" \
| jq -r '.data[].id' \
| while read -r id; do
    curl -s "https://api.opsgenie.com/v2/schedules/$id.ics" \
      -H "Authorization: GenieKey $OPSGENIE_API_KEY" \
      -o "schedule-$id.ics"
  done
Enter fullscreen mode Exit fullscreen mode

The key needs read access to configuration. An account-level key from API Key Management with Read and Configuration Access works, as does a global API integration key. Our Opsgenie API guide explains the key types.

Export who was on call: the timeline API

For reporting, on-call pay, or an audit trail, the timeline endpoint returns JSON instead of calendar events:

curl -s "https://api.opsgenie.com/v2/schedules/$SCHEDULE_ID/timeline?interval=1&intervalUnit=months&expand=base,override" \
  -H "Authorization: GenieKey $OPSGENIE_API_KEY"
Enter fullscreen mode Exit fullscreen mode

intervalUnit can be days, weeks, or months, and interval sets how many. date sets the starting point (format yyyy-MM-dd'T'HH:mm:ssZ, with + encoded as %2B in curl). expand adds the base, forwarding, or override timelines, which lets you see which shifts were swaps rather than the normal rotation. The flattenedRecipients field only appears for periods that have already finished.

Export the rotation rules, not just the shifts

Here's the catch with every calendar-based export: an .ics file records that Priya was on call from Monday 09:00 to the next Monday 09:00. It doesn't record that she's in a weekly rotation with three other people, that the rotation only runs during business hours, or that one shift was an override. If you rebuild a schedule from calendar files, you're reverse-engineering the rules by hand.

The rules live in the schedule and rotation endpoints:

curl -s "https://api.opsgenie.com/v2/schedules/$SCHEDULE_ID/rotations" \
  -H "Authorization: GenieKey $OPSGENIE_API_KEY"
Enter fullscreen mode Exit fullscreen mode

Each rotation includes its type (daily, weekly, or hourly), length, start date, participants in order, and any time restriction. Save this JSON for every schedule along with the schedule's own timezone from GET /v2/schedules/:identifier. It's the copy you'll actually rebuild from, whichever tool you move to.

Moving Opsgenie schedules to another tool

With Opsgenie's shutdown on April 5, 2027, most teams exporting schedules today are doing it to migrate. There are three ways to get them into a new tool, in order of how much rework they save:

An API-based importer: the destination tool reads your schedules and rotations directly from Opsgenie's API and recreates them. incident.io, Grafana Cloud IRM, ilert, and FluidifyAI Regen all have one in some form. Ask what each importer skips: overrides, time restrictions, and rotations that include teams or escalations instead of users are common gaps.

Calendar import: some tools can read an .ics feed as a schedule. Grafana's docs note that iCal-imported schedules are read-only, so you'd recreate them to edit later. This preserves who's on call but not the rules.

Manual rebuild from the JSON: recreate each rotation in the new tool using the rotation export as the spec. Slow, but it's also a chance to simplify years of drift.

Whichever route you take, compare the new tool's next four weeks of on-call against Opsgenie's timeline export for the same period before cutting over. Timezone and handoff-time mistakes show up right away in that comparison. The full sequence is in our Opsgenie migration checklist.

Importing Opsgenie schedules into FluidifyAI Regen

FluidifyAI Regen has a built-in Opsgenie importer, available in the UI and as a CLI command. It reads your Opsgenie users, schedules, rotations, and escalation policies through the Opsgenie REST API:

regen import opsgenie --api-key=$OPSGENIE_API_KEY --dry-run
regen import opsgenie --api-key=$OPSGENIE_API_KEY --region=eu
Enter fullscreen mode Exit fullscreen mode

The dry run fetches and validates everything and prints how many schedules, escalation policies, and users it found, without writing anything. A real run writes a JSON report of what was imported, skipped, and warned about. Here's how it maps Opsgenie concepts:

  • Each Opsgenie schedule becomes a Regen schedule with the same name, description, and timezone (UTC if none is set).
  • Each rotation becomes a layer in that schedule, in the same order. A weekly rotation of length 1 becomes a weekly layer and a daily rotation of length 1 becomes a daily layer. Anything else, including hourly rotations and multi-week lengths, becomes a custom layer with the equivalent shift length.
  • User participants carry over in order. Rotation participants that are teams or escalations are skipped.
  • A schedule whose name already exists in Regen is skipped unless you pass --force.

What it doesn't import: overrides, rotation time restrictions, and teams. Add those by hand after the import and check them against your Opsgenie timeline export. Regen also doesn't have an iCal export for shifts yet, so if calendar sync is a hard requirement for your team, factor that in. The rest of the move is covered in our Opsgenie-to-Regen walkthrough.

FAQ

How do I export my Opsgenie schedule to Google Calendar? Open the schedule in Opsgenie, select Open calendar, and confirm. Google Calendar adds it as a subscribed calendar that Opsgenie keeps updating monthly. You can also download an .ics file with Export team schedule and import it, but that won't update.

Can I export Opsgenie schedules through the API? Yes. GET /v2/schedules/:identifier.ics returns an .ics file per schedule, and the timeline and rotation endpoints return JSON.

How far ahead does the Opsgenie .ics export go? Atlassian's current documentation says the current month starting from today. Older docs mention 12 months. Check the range in your own export.

Does the .ics export include rotation rules and overrides? It includes the resulting shifts, overrides included, but not the rules that generate them or which shifts were overrides. Use the rotation and timeline APIs for that.

What happens to my Opsgenie schedules after April 5, 2027? Atlassian says data that hasn't been moved is deleted when Opsgenie shuts down. Export schedules and rotation definitions before then. Our post on the Opsgenie shutdown dates has the full timeline.

Get your schedules out early

Exporting is quick and costs nothing, so do it now even if the migration itself is months away. Keep the .ics files for history and the rotation JSON for the rebuild. If you want to try an importer against your real Opsgenie schedules, Regen is $100 a month flat with a free 30-day trial and the dry run shows exactly what it would bring over before it writes anything.

Top comments (0)