Migration Page Generator
Draft competitor migration landing pages and hub copy so switchers can import data and sign up with less friction.
Overview
Migration Page Generator is an agent skill for the Launch phase that produces competitor migration guide structure and copy for SaaS switchers reducing signup friction.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill migration-page-generatorWhat is this skill?
- Triggers on migration guide, migrate from X, switch to product, and import-from-competitor intents
- Initial assessment for source competitor, hub vs per-competitor URLs, and migration mechanism
- Structured page sections from headline through step-by-step import and FAQ
- Reads .claude or .cursor project-context.md when present for product and import capabilities
- Differentiates from rebranding-strategy for redirects and rename work
- Page structure table with 4+ core sections (headline, why switch, steps, CTA)
- Metadata version 1.0.1 in skill frontmatter
Adoption & trust: 720 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are winning comparison traffic but prospects bail because they cannot see a clear, trustworthy path to move data from a named competitor.
Who is it for?
Indie SaaS and productivity apps launching dedicated migrate-from-competitor pages linked from alternatives content.
Skip if: Domain-wide rebrands, redirect matrices, or engineering-only ETL runbooks without a public marketing page goal.
When should I use this skill?
User wants to create, optimize, or audit migration guides; mentions migration guide, migrate from X, switch to product, import from X, or data migration.
What do I get? / Deliverables
You get a complete migration page outline with headlines, switch rationale, import steps, and CTAs aligned to your actual migration capabilities.
- Migration page section outline with headlines and CTAs
- Step-by-step user-facing import instructions matched to migration type
Recommended Skills
Journey fit
Launch distribution is the canonical shelf because migration pages are go-to-market assets that convert competitor users at signup—not internal validation prototypes. Distribution fits competitor-switch guides, signup CTAs, and alternatives cross-links aimed at acquisition traffic.
How it compares
Use for competitor switch landing copy; use rebranding-strategy when the task is rename, redirects, and brand continuity—not import onboarding.
Common Questions / FAQ
Who is migration-page-generator for?
Solo founders and small GTM teams shipping self-serve tools who need polished migration pages without hiring a conversion copywriter.
When should I use migration-page-generator?
Use it in Launch when building distribution pages for users migrating from Notion, Trello, or other named competitors, or when the user mentions migration guides, import from X, or switch-to-product messaging.
Is migration-page-generator safe to install?
It generates marketing copy and reads optional local project context files; review the Security Audits panel on this page and avoid embedding secrets in published guides.
SKILL.md
READMESKILL.md - Migration Page Generator
# 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: 1. **Source**: Which competitor(s) to cover (Notion, Trello, etc.) 2. **Format**: Single hub vs. per-competitor pages (/migrate-from-notion) 3. **Migration type**: Manual import, automated tool, API 4. **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