How to export your data from PagerDuty
PagerDuty has no single "export all my data" button. You export incident/metrics data as CSV from the Insights reports, export on-call schedules as iCalendar/WebCal feeds, and pull everything else (services, users, escalation policies, raw incident records) as JSON via the REST API.
✓ Verified against PagerDuty's official documentation, October 2026
Step by step
- 1Go to Analytics > Insights > Incident Activity Insights, set your filters and date range, then click "Export CSV" to generate the file based on your current search/filter selections.
- 2If the report has more than ~10,000 rows, PagerDuty fetches it in the background and emails you a link to the .csv file instead of downloading it instantly — check your email, not the UI, for the success notice.
- 3Repeat the Export CSV step for other reports you need (Service Performance Insights, Responder Insights, Team Insights, Escalation Policy Insights, Event Analytics, User Onboarding Report) since each is exported separately.
- 4To export a single on-call schedule: go to People > Schedules, find the schedule, click "Export" next to it, then right-click "Everyone" under iCalendar file and copy the link (or download the .ics file).
- 5To export all of your personal on-call schedules at once: click your User Icon > My Profile > User Settings tab, then in the Calendar section right-click "WebCal feed" to copy the link, or click "iCalendar file" to download the .ics directly.
- 6Import the WebCal/iCal link or .ics file into Google Calendar, Outlook, Apple Calendar, or Confluence to keep a readable copy of on-call history.
- 7For anything not covered by the CSV/iCal exports — full configuration of services, escalation policies, users, teams, or raw incident objects — use the PagerDuty REST API (developer.pagerduty.com) to pull JSON records programmatically before you cancel.
What the export includes
- ✓Incident response metrics and the underlying Incidents List (via Insights CSV export)
- ✓On-call schedules as iCalendar/WebCal feeds, showing roughly 1 month of historical shifts and up to 6 months of upcoming on-call shifts
- ✓User onboarding/licensing status (via User Onboarding Report CSV export)
- ✓Event volume and integration breakdowns (via Event Analytics CSV export)
- ✓Full object data (services, schedules, escalation policies, users, incidents) if you query the REST API directly
What it doesn't include
- ✗A single bulk/account-wide export file — PagerDuty does not offer one-click export of the whole account
- ✗Schedule history older than about 1 month via the iCal/WebCal feed
- ✗Rows beyond your plan's CSV export limit (100,000 or 250,000 depending on plan) — the export is silently truncated if your result set is larger
- ✗Incident attachments, postmortem documents, or Jeli post-incident review content (these live in separate tools/exports)
- ✗Integration credentials, webhook secrets, or other sensitive configuration (never exposed via export)
Before you start
- ⚠There is no "Export All Data" button — budget time to export each report/schedule separately, or script it via the API
- ⚠CSV row limits differ by plan: 100,000 rows on Professional/Business, 250,000 rows on Enterprise Incident Management/Digital Operations (legacy); if your export hits that number exactly, assume it was truncated and re-export in smaller date-filtered batches
- ⚠Large CSV reports are generated in the background and delivered by email, not as an instant browser download — there's no success banner in the UI, so you must check your inbox
- ⚠The iCal/WebCal schedule feed only shows ~1 month of historical shifts even though up to 6 months of future on-call is included
- ⚠Each Insights report (Incident Activity, Service Performance, Responder, Team, Escalation Policy) has its own export action — exporting one does not export the others
Where to take your data
Free and cheaper tools that can take a PagerDuty export. See all PagerDuty alternatives →
Grafana OnCall
Recreate schedules by importing the exported .ics/WebCal feed as an iCal-based schedule source, and use the API to recreate escalation policies and integrations manually since Grafana OnCall does not have a native PagerDuty CSV importer.
Opsgenie has a dedicated PagerDuty migration/import tool in its settings that reads directly from the PagerDuty API (using an API key) to bring over schedules, escalation policies, and users, rather than relying on the CSV/iCal exports.
Squadcast
Use Squadcast's PagerDuty importer (connects via PagerDuty API key) to migrate services, schedules, and escalation policies; use the exported iCal feeds only as a manual fallback/verification source.
Exporting from PagerDuty: common questions
Can I export all my PagerDuty data in one click before cancelling?+
No. PagerDuty doesn't provide a single account-wide export. You export incident/report data as CSV, schedules as iCalendar/WebCal, and pull everything else (users, services, escalation policies) via the REST API.
What format do PagerDuty exports come in?+
Reports and dashboards (Incident Activity Insights, Event Analytics, User Onboarding Report) export as CSV. Schedules export as iCalendar (.ics) files or WebCal feed links. Anything pulled via the API comes back as JSON.
Is there a limit on how many rows I can export?+
Yes. CSV export limits depend on your plan: 100,000 rows on Professional and Business plans, 250,000 rows on Enterprise Incident Management and legacy Digital Operations plans. If your export count exactly matches the limit, your data was likely truncated and you should filter/export in smaller batches.
How far back does a schedule export go?+
The iCal/WebCal feed shows about 1 month of historical on-call shifts and up to 6 months of upcoming scheduled shifts.
Do large exports download instantly?+
Not always. Reports with more than roughly 10,000 rows are generated in the background and emailed to you as a CSV link rather than downloading immediately in the browser — there's no in-app success banner, so check your email.
What's the best way to migrate services, escalation policies, and users instead of just data?+
Use the PagerDuty REST API directly, or use the target tool's native PagerDuty importer (Opsgenie and Squadcast both offer one) which reads your PagerDuty account via API key rather than relying on manual CSV/iCal exports.
Sources
This guide was written from PagerDuty's own documentation and checked against it in October 2026. If a step has changed, the official page wins.
PagerDuty head-to-head
More Dev Tools tools people are leaving
All Dev Tools alternatives →What would you save without PagerDuty?
Pick your team size and see the yearly number.