Sentry Migration Deep Dive

Prerequisites

• Current error tracking tool access

• Sentry project created

• API access to old tool (for data export)

• Parallel run timeline established

Instructions

• Complete assessment phase documenting current tool usage

• Set up Sentry projects matching existing structure

• Install Sentry SDK alongside existing tool for parallel running

• Map feature equivalents between old tool and Sentry APIs

• Run both tools in parallel for 2-4 weeks

• Compare error capture rates and verify parity

• Recreate alert rules in Sentry matching old tool

• Export historical data from old tool API if needed

• Remove old SDK dependencies and configuration

• Train team on Sentry dashboard and cancel old subscription

Output

• SDK migration complete

• Historical data exported (if needed)

• Alert rules recreated

• Team transitioned to Sentry

Error Handling

See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.

Examples

See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.

Resources

• Sentry Migration Guide

• SDK Documentation

Overview

Execute migrate to Sentry from other error tracking tools.