Move your Opsgenie on-call schedule to Turnkeep (export and import)
Opsgenie can export a schedule as a calendar file, and Turnkeep reads that file, or a plain CSV from any spreadsheet, so your people and past shifts come across and the next plan stays fair. This page shows the export, what the import does with it, and what it cannot bring over.
Turnkeep plans, records and publishes a rota. It does not page anyone, so keep a paging tool for alerts. If you are still choosing, read the Opsgenie alternative guide first.
Step 1: export the schedule from Opsgenie
- Open the schedule in Opsgenie and choose the export icon on its toolbar. It downloads an iCalendar (
.ics) file. Atlassian's support page says the download covers the next 12 months from the current month, while the older Opsgenie docs describe a shorter window, so check what your file contains. - Do one file per schedule layer. A primary and a secondary schedule overlap in time, and one Turnkeep rota holds one layer.
- Want past months too, so fairness remembers who carried the load? Export from a calendar that holds them, or add a few past rows by hand in a CSV (below).
Step 2: or write a CSV
Any spreadsheet works. Three columns, person, start and end, with or without a header row:
person,start,end
Ana,2026-11-02,2026-11-08
Ben,2026-11-09,2026-11-15
Chen,2026-11-16,2026-11-22Dates are 2026-11-02 or with a time like 2026-11-02T09:00:00Z. Comma, semicolon and tab separators all work. For dates alone you say whether the end is the last day on call or the day the next person takes over. A file exported from Turnkeep (first_day,last_day,person) imports as is.
Step 3: import it
- Open the free app and create a workspace (no email or password).
- Set your time zone and handover time under Settings, so times in the file land on the right day.
- Open the Import tab, choose the file or paste its text and press Read the file. You see what will happen before anything is saved.
- Press Add to this rota. New names become people with a full share; change part-timers on the People tab.
What the import does with your file
| In the file | What Turnkeep does |
|---|---|
| A shift that starts or ends at a time other than your handover time | Rounds start and end to the nearest handover (so back-to-back shifts stay back-to-back) and tells you how many rows it touched. If every shift in the file starts at one time that is not your handover, it says so and suggests setting that time under Settings |
| Back-to-back days for the same person (daily blocks) | Merges them into one shift |
| Two people covering the same days (a second layer) | Keeps the earlier one, leaves the other out and says so |
A repeating event (RRULE) | Reads the first occurrence only and tells you |
Calendar reminders (VALARM) inside an event | Ignores them, so a reminder title is never read as a person |
| Shifts shorter than a day, or over 31 days | A shift of a few hours takes its whole day (and is counted as rounded); over 31 days is skipped and listed |
| Names already on your list | Matches them without regard to capital letters |
| Free plan limits | Leaves out shifts older than 28 days or more than 8 weeks ahead, and stops if the file has more new people than you have room for (the plan counts every person on the list, active or not) |
What does not come across
- Escalation policies, alert routing, integrations and notification rules. Turnkeep has none of these.
- Overrides as separate objects: they arrive only as far as they appear as events in the export.
- Leave. Add it on the People tab; planning then avoids it.
After the import
The Fairness tab now counts the imported shifts, weekends and holidays included (add your public holidays first), so the next preview gives the lightest-loaded people the next turns. See how the points work, and size the team with the team size calculator.