Sentry Migration Deep Dive

Overview

Replace an existing error tracking tool (Rollbar, Bugsnag, New Relic, Raygun, Airbrake) with Sentry using a phased migration that runs both tools in parallel before cutover. This skill covers concept mapping between providers, SDK swap patterns, alert rule migration, team training, and rollback strategy.

Current State

!npm list 2>/dev/null | command grep -iE "sentry|rollbar|bugsnag|raygun|airbrake|honeybadger|newrelic" || echo 'No error tracking packages found'

Prerequisites

• Admin access to the current error tracking tool (API keys, alert rule access)
• Sentry project created with DSN available in environment variables
• Source maps or debug symbols configured for stack trace resolution
• Parallel run timeline agreed with team (2-4 weeks recommended)
• Inventory of current alert rules, integrations, and custom filters

Instructions