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 Concepta11ops Equivalent
ServiceWorkspace
Integration KeyWorkspace API Key
IncidentAlert
Escalation PolicyAlert Rules (coming soon)
ScheduleOn-call Schedule (coming soon)

Step 1: Create a11ops Workspaces

Create a workspace for each PagerDuty service you want to migrate:

  1. Log in to a11ops dashboard
  2. Create a new workspace (e.g., “Production API”, “Database”)
  3. Note the workspace API key
  4. 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/enqueue

Replace with a11ops:

https://api.a11ops.com/alerts/YOUR_WORKSPACE_API_KEY

Step 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

  1. Send test alerts to verify integration
  2. Confirm team members receive notifications
  3. Run both systems in parallel for 1-2 days
  4. Gradually migrate services one by one
  5. Decommission PagerDuty services after validation

Typical Migration Timeline

1

Week 1: Planning & Setup

Create workspaces, add team members, document current configuration

2

Week 2: Integration Updates

Update monitoring tools to send alerts to both platforms (dual-run)

3

Week 3: Validation

Compare alerts between platforms, fix any discrepancies

4

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.