DocsTroubleshooting
Documentation

Troubleshooting

Use this guide to understand common beta issues and what to check first.

Login or access issues

Confirm your beta request is approved. If you were approved but still cannot log in, contact support.

Beta request approved but cannot log in

Double-check the email you used to request access matches the login email. Try password reset if applicable.

Credentials validation failed

  • Re-check keys, URLs, and permissions.
  • Regenerate keys if you rotated them recently.
  • Confirm the destination project is reachable.

GitHub repository not showing

  • Confirm OAuth scopes were granted.
  • Confirm organization access is approved.
  • Reconnect GitHub and retry analysis.

Secrets not configured

Apply destination values manually or use the automatic flow with a one-time Supabase Management Access Token.

Edge Function deployment blocked

  • GitHub-backed: confirm source code is present in the repo.
  • Supabase-detected-only: deploy manually with your own tooling.
  • Confirm required secrets exist at the destination.

Storage migration issues

  • Files near the 100 MB per-file limit may be rejected in beta.
  • Confirm buckets exist and permissions are correct.

Auth migration issues

  • Existing destination users are not overwritten.
  • Confirm auth is enabled at the destination.

Rollback confusion

Rollback only removes items Miglify created during that migration. It does not delete pre-existing destination data.

When to contact support

  • Email: [SUPPORT_EMAIL]
  • Chat: [WHATSAPP_OR_SUPPORT_CHANNEL]
  • Do not paste secret values or Management Access Tokens in support messages.
Need beta access?
Miglify is currently in controlled private beta.
Request Private Beta Access