mcpbeat

Migration Page Generator

kostja94/migration-page-generator

When the user wants to create, optimize, or audit migration guides for users switching from competitors. Also use when the user mentions "migration guide," "migrate from X," "switch to [product]," "import from X," or "data migration." For rebrand and redirects, use rebranding-strategy.

690 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/kostja94/marketing-skills --skill migration-page-generator

The instruction itself

9 sections, as written by the author

Pages: Migration

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

| Section | Purpose |

|---------|---------|

| Headline | "Migrate from [Competitor] to [Product] in Minutes" |

| Why switch | Brief; link to alternatives for full comparison |

| What transfers | Data, structure, attachments; what's supported |

| Steps | Numbered guide; screenshots or video |

| Troubleshooting | Common issues, support link |

| CTA | Start migration, try free, contact support |

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

How to use it

Copy the folder

Take kostja94/migration-page-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.