render-migrate-from-heroku
Audited by Runlayer on Mar 1, 2026
Malicious tool definition detected
Compare row counts against the Heroku source if possible. Present a health summary after all checks pass.
Tool passed security scan
Malicious tool definition detected
Check your current disk usage with `heroku pg:info` (look for `Data Size`) — if your actual data is much smaller than the allocated disk, start with a smaller `diskSizeGB` to save on storage costs.
Malicious tool definition detected
Present a side-by-side summary:** ``` DATA VALIDATION ───────────────────────────── Table | Heroku | Render users | 12,450 | 12,450 ✅ orders | 84,321 | 84,321 ✅ products | 1,203 | 1,203 ✅ ───────────────────────────── ``` If counts don't match, warn the user and suggest re-running the restore.
Malicious tool definition detected
Malicious tool definition detected
**Repo URL available?** Verify a Git remote exists: ```bash git remote -v ``` If no remote exists, stop and guide the user to create a GitHub/GitLab/Bitbucket repo, add it as `origin`, and push before continuing. If the URL is SSH format, convert it to HTTPS for service creation and deeplinks: | SSH Format | HTTPS Format | |---|---| | `git@github.com:user/repo.git` | `https://github.com/user/repo` | | `git@gitlab.com:user/repo.git` | `https://gitlab.com/user/repo` | | `git@bitbucket.org:user/rep
Passed Files (2)Click to expand
Tool passed security scan
Tool passed security scan