Heroku to Render Migration

Migrate from Heroku to Render using the user's supplied inventory or local project files, then optionally enrich missing details with live Heroku data via MCP.

Prerequisites Check

Before starting, verify what's available:

1. App inventory (required) — use complete details supplied by the user, or inspect local project files such as Procfile, app.json, package.json, requirements.txt, Gemfile, or go.mod
2. Render MCP (recommended) — check if list_services tool 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.
3. Heroku MCP (optional) — check if list_apps tool is available

Do not require local files or MCP when the user has already supplied enough information for the requested plan, Blueprint, or migration instructions. If Render MCP is missing and the user actually needs live Render access, use the Render access workflow in references/render-access.md; the MCP setup guide adds Heroku-specific setup. If Heroku MCP is missing, use supplied values or ask only for missing config-var names and add-on details.

Migration Workflow

For an end-to-end migration, execute the applicable steps in order. Present findings to the user and get confirmation before creating any resources.

Before mapping Heroku process types to Render service types, read references/service-types.md.