Migration Guides
Migrate from your existing incident management platform to a11ops with minimal disruption. Our step-by-step guides ensure a smooth transition.
Select Your Current Platform
Why Migrate to a11ops?
Instant Setup
Get started in minutes with our simple SDK. No complex configurations or lengthy onboarding processes.
Better Developer Experience
Built for developers with clean APIs, great documentation, and intuitive interfaces.
No Vendor Lock-in
Export your data anytime. Standard webhook formats make it easy to integrate or migrate.
Cost Effective
Transparent pricing with no per-user fees. Pay only for what you use, not for seats.
Migrating from PagerDuty
PagerDuty and a11ops share similar concepts, making migration straightforward:
| PagerDuty Concept | a11ops Equivalent |
|---|---|
| Service | Workspace |
| Integration Key | Workspace API Key |
| Incident | Alert |
| Escalation Policy | Alert Rules (coming soon) |
| Schedule | On-call Schedule (coming soon) |
Step 1: Create a11ops Workspaces
Create a workspace for each PagerDuty service you want to migrate:
- Log in to a11ops dashboard
- Create a new workspace (e.g., “Production API”, “Database”)
- Note the workspace API key
- Add team members who were on the PagerDuty service
Step 2: Update Integration Endpoints
Replace PagerDuty integration URLs with a11ops webhooks:
PagerDuty Events API v2:
https://events.pagerduty.com/v2/enqueueReplace with a11ops:
https://api.a11ops.com/alerts/YOUR_WORKSPACE_API_KEYStep 3: Update Alert Payloads
Modify your alert sending code:
// PagerDuty payload
{
"routing_key": "YOUR_INTEGRATION_KEY",
"event_action": "trigger",
"payload": {
"summary": "Database CPU high",
"severity": "error",
"source": "monitoring",
"custom_details": { ... }
}
}
// a11ops payload (simpler!)
{
"title": "Database CPU high",
"severity": "high",
"source": "monitoring",
"metadata": { ... }
}Step 4: Test and Validate
- Send test alerts to verify integration
- Confirm team members receive notifications
- Run both systems in parallel for 1-2 days
- Gradually migrate services one by one
- Decommission PagerDuty services after validation
Typical Migration Timeline
Week 1: Planning & Setup
Create workspaces, add team members, document current configuration
Week 2: Integration Updates
Update monitoring tools to send alerts to both platforms (dual-run)
Week 3: Validation
Compare alerts between platforms, fix any discrepancies
Week 4: Cutover
Switch to a11ops as primary, keep old platform for reference
Complete
Decommission old platform after 30 days of stable operation
Migration Checklist
Need Migration Assistance?
Our team is here to help ensure a smooth migration to a11ops.