migration-page-generator
The migration-page-generator skill creates step-by-step guides that help users switch from competitor products to your own. Use it when developing migration content for SaaS, tools, or productivity apps, or when users request migration guides, competitor comparisons for switching, or data import instructions. The skill structures pages with clear headlines, numbered migration steps, data transfer details, troubleshooting sections, and conversion-focused CTAs to reduce friction for incoming switchers.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/migration-page-generator && cp -r /tmp/migration-page-generator/skills/pages/marketing/migration ~/.claude/skills/migration-page-generatorSKILL.md
# 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
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.