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

نصبش چطور است کپی

Claude Code / Claude Desktop

1. Create a folder named after the skill inside your skills directory:
   - Claude Code: `~/.claude/skills/<skill-name>/`
   - A project-local skill: `<project>/.claude/skills/<skill-name>/`
2. Save the text below as `SKILL.md` in that folder, keeping the
   `---` frontmatter block at the top — the `name` and `description`
   fields are what make the skill discoverable.
3. Restart Claude Code, or run `/skills` to confirm it is listed.

The skill loads only when its `description` matches what you are doing,
so a precise description matters more than a long body.

برای تو جواب داد؟

از کجا آمده

2025 kostja94