Guides migration pages that help users switch from a competitor to your product. Reduces friction for switchers; often linked from alternatives pages. Common for SaaS, tools, and productivity apps.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, migration capabilities, and source platforms.

Identify:

• Source: Which competitor(s) to cover (Notion, Trello, etc.)
• Format: Single hub vs. per-competitor pages (/migrate-from-notion)
• Migration type: Manual import, automated tool, API
• Primary goal: Sign up, start migration, reduce churn risk

Page Structure

Best Practices

Clarity

• Explicit steps: "1. Export from X. 2. Upload to [Product]. 3. Map fields."
• Time estimate: "Takes ~10 minutes for most workspaces"
• Data scope: What transfers; any limitations

Trust

• No competitor bashing: Focus on your product's ease
• Support: Offer help; link to docs, chat, email
• Success stories: "10,000+ teams migrated from X"

SEO

• Intent: Transactional; "migrate from X to Y"
• Title: "Migrate from [Competitor] to [Product] | Step-by-Step Guide"
• Internal links: Alternatives, features, pricing, docs

Output Format

• Headline and intro
• Step-by-step migration guide
• Data transfer scope
• Troubleshooting section
• Internal links
• SEO metadata

Related Skills

• alternatives-page-generator: Link to migration from alternatives
• docs-page-generator: Detailed migration docs
• landing-page-generator: Migration as conversion page
• faq-page-generator: Migration FAQ section