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
1---
2name: migration-page-generator
3description: 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.
4metadata:
5 version: 1.0.1
6---
7
8# Pages: Migration
9
10Guides 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.
11
12**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.
13
14## Initial Assessment
15
16**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.
17
18Identify:
191. **Source**: Which competitor(s) to cover (Notion, Trello, etc.)
202. **Format**: Single hub vs. per-competitor pages (/migrate-from-notion)
213. **Migration type**: Manual import, automated tool, API
224. **Primary goal**: Sign up, start migration, reduce churn risk
23
24## Page Structure
25
26| Section | Purpose |
27|---------|---------|
28| **Headline** | "Migrate from [Competitor] to [Product] in Minutes" |
29| **Why switch** | Brief; link to alternatives for full comparison |
30| **What transfers** | Data, structure, attachments; what's supported |
31| **Steps** | Numbered guide; screenshots or video |
32| **Troubleshooting** | Common issues, support link |
33| **CTA** | Start migration, try free, contact support |
34
35## Best Practices
36
37### Clarity
38
39- **Explicit steps**: "1. Export from X. 2. Upload to [Product]. 3. Map fields."
40- **Time estimate**: "Takes ~10 minutes for most workspaces"
41- **Data scope**: What transfers; any limitations
42
43### Trust
44
45- **No competitor bashing**: Focus on your product's ease
46- **Support**: Offer help; link to docs, chat, email
47- **Success stories**: "10,000+ teams migrated from X"
48
49### SEO
50
51- **Intent**: Transactional; "migrate from X to Y"
52- **Title**: "Migrate from [Competitor] to [Product] | Step-by-Step Guide"
53- **Internal links**: Alternatives, features, pricing, docs
54
55## Output Format
56
57- **Headline** and intro
58- **Step-by-step** migration guide
59- **Data transfer** scope
60- **Troubleshooting** section
61- **Internal links**
62- **SEO** metadata
63
64## Related Skills
65
66- **alternatives-page-generator**: Link to migration from alternatives
67- **docs-page-generator**: Detailed migration docs
68- **landing-page-generator**: Migration as conversion page
69- **faq-page-generator**: Migration FAQ section
gabrielmoreira