render-migrate-from-heroku

What problem does it solve?

This Skill prevents risky, error-prone Heroku-to-Render migrations by turning your local Heroku project files into a validated Render service plan with correct process types, runtimes, and environment variable handling.

Core Features & Use Cases

• Inventory-driven migration: Reads your Procfile and dependency files to infer runtimes, build/start commands, process types (web/worker/clock/release), static-site detection, and add-on needs.
• Optional live enrichment via MCP: When available, uses Heroku MCP to fetch dyno sizes, add-on plan slugs, config var names, and database sizing to avoid guessing.
• Two creation paths with guardrails: Defaults to Infrastructure-as-Code via Blueprint YAML (multi-service, databases, and workers), with an MCP direct-creation fallback for simple single-service cases.
• Post-migration verification and rollback guidance: Guides database/Redis migration, deploy verification (health, logs, metrics, env vars, DB connectivity), and manual DNS cutover with clear rollback principles.

Quick Start

Ask an AI to migrate your app by reading your local repo files and producing a validated render.yaml for deploying the equivalent Render services, using Blueprint as the default approach.