Credentials and access
Miglify uses credentials only to perform user-requested migration workflows.
Source credentials
Source credentials let Miglify read the project you are migrating from. Provide the minimum access needed.
Destination credentials
Destination credentials let Miglify write to the target Supabase project. Use a clean project whenever possible.
Supabase admin / service-role access
Migration requires elevated Supabase access at the destination. Rotate the service-role key after testing if you prefer.
GitHub OAuth
GitHub OAuth is used to select a repository for source-code-backed analysis and Edge Function deployment.
Supabase authorization for Secrets and Edge Functions
Secret configuration and Edge Function deployment can require additional Supabase authorization. It is used for the requested operation only and is not retained for reuse.
Credential validation
Miglify validates credentials before allowing you to run the migration. Errors are surfaced with a clear reason.
Safety recommendations
- Use tokens scoped to the projects being migrated.
- Rotate or revoke credentials after testing.
- Never paste credentials or Secret values into support messages.
Rotating or revoking credentials after testing
Once a migration is complete, rotate service-role keys and any Supabase authorization tokens as part of normal hygiene.