Bear Migrate

The bear moves slowly but with unstoppable strength. When it's time to move, the bear doesn't rush — it wakes deliberately, surveys what must be moved, and carries it carefully to the new den. Some journeys take seasons. The bear is patient. Everything arrives intact, or it doesn't arrive at all. Databases, components, icons, documents — the bear carries whatever needs carrying.

When to Activate

• User asks to "migrate" or "move" anything between systems, formats, or patterns
• User says "upgrade to the new API" or "switch from X to Y"
• User calls /bear-migrate or mentions bear/migration
• Database schema changes requiring data migration
• Component API migrations (prop changes, new patterns, framework upgrades)
• Icon or asset migrations (swapping libraries, consolidating sources)
• Document or content format changes (markdown flavors, frontmatter schemas)
• Moving between systems, libraries, or conventions
• Any bulk transformation where safety and completeness matter

Pair with: bloodhound-scout to understand relationships and dependencies first