Audit existing Rulesets via the PagerDuty API (Rulesets remain API-accessible in read-only state after the January 31, 2025 UI end-of-life).
For each Ruleset, use the PagerDuty-provided push-button migration tool or the REST API convert endpoint to port rules into an Event Orchestration.
Map Ruleset conditions to Event Orchestration routing rules, preserving priority order and any suppression or severity-override actions.
Update integration keys: if using global integration key migration, replace Ruleset integration keys with the new Event Orchestration routing keys in your alert sources.
Test the new orchestration with sample events before decommissioning the legacy Ruleset configuration.
Known gotchas
As of January 31, 2025, the Rulesets UI is no longer visible in the PagerDuty web app; rules continue to process events but can only be read or modified via API — PagerDuty (not any third party) recommends completing migration to Event Orchestrations.
Event Orchestration routing rules support nesting and more expressive conditions than Rulesets; review migrated rules for logical equivalence rather than assuming the automated conversion is always exact.
Global Ruleset integration keys and Service Ruleset integration keys migrate via different paths; confirm which migration mode applies to each Ruleset before executing.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp