render-migrate-from-heroku
Heroku to Render Migration
Migrate from Heroku to Render by reading local project files first, then optionally enriching with live Heroku data via MCP.
Prerequisites Check
Before starting, verify what's available:
- Local project files (required) — confirm the current directory contains a Heroku app (look for
Procfile,app.json,package.json,requirements.txt,Gemfile,go.mod, or similar) - Render MCP (recommended) — check if
list_servicestool is available. Required for MCP Direct Creation (Step 3B) and automated verification (Step 6). Not required for the Blueprint path — the Render CLI and Dashboard handle generation, validation, and deployment. - Heroku MCP (optional) — check if
list_appstool is available
If Render MCP is missing and the user needs it, guide them through setup using the MCP setup guide. If Heroku MCP is missing, note that config var values and add-on plan details will need to be provided manually.
Migration Workflow
Execute steps in order. Present findings to the user and get confirmation before creating any resources.
Step 1: Inventory Heroku App
More from render-oss/skills
render-deploy
Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.
59render-debug
Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.
47render-monitor
Monitor Render services in real-time. Check health, performance metrics, logs, and resource usage. Use when users want to check service status, view metrics, monitor performance, or verify deployments are healthy.
46render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
35render-env-vars
>-
14render-cli
>-
14