# Overhauling PagerDuty's data model: a better way to route alerts

DevFeed: [Overhauling PagerDuty's data model: a better way to route alerts](<https://devfeed.tech/articles/overhauling-pagerduty-s-data-model-a-better-way-to-route-alerts-11952.md>)

Original publisher: [Read original article](<https://incident.io/blog/overhauling-pager-dutys-data-model-a-better-way-to-route-alerts>)

Author: Chris Evans

Published: 2025-01-20T06:57:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [site-reliability-engineering](<https://devfeed.tech/topics/site-reliability-engineering.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Microsoft Teams](<https://devfeed.tech/topics/microsoft-teams.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [communication](<https://devfeed.tech/tags/communication.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [operational](<https://devfeed.tech/tags/operational.md>), [operations](<https://devfeed.tech/tags/operations.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [routing](<https://devfeed.tech/tags/routing.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

The article compares PagerDuty's established but aging data model for routing alerts with incident.io On-call's redesigned approach. It explains the challenges of configuring services, monitoring integrations, escalation policies, and routing flexibility, then introduces migration paths from PagerDuty to incident.io.

## Source excerpt

PagerDuty has long been the go-to solution for reliable on-call management, but its aging data model and lack of innovation have become a challenge. In this post we explore how incident.io On-call offers a better, more flexible approach to alert routing and provide practical advice on how to migrate smoothly from PagerDuty.