Documentation
Secrets and guided setup
Miglify helps identify required secret names and guide destination setup without exporting source secret values.
What Miglify can detect
- Names of secrets referenced by Edge Functions.
- Which secrets already exist at the destination.
- Which secrets still need to be configured before deployment.
What Miglify cannot export
- Source secret values
Source secret values
Secret values cannot and should not be exported from the source project. You provide destination values directly.
Destination secret values
Set destination secret values manually, or use the automatic flow with a one-time Supabase Management Access Token.
Automatic setup using one-time Supabase Management Access Token
Provide a one-time Supabase Management Access Token, the secret name, and the value. Miglify applies it to the destination and clears the sensitive fields from local state immediately.
Manual setup confirmation
You can always configure destination secrets by hand in Supabase and mark them as ready in Miglify.
Security notes
Important
- Source secret values cannot be exported.
- Secret values are not displayed after saving.
- Users provide destination secret values when needed.
- Miglify does not store Supabase Management Access Tokens.
- Miglify does not store secret values.
- Manual setup remains available.
Best practices
- Rotate secrets after testing.
- Use least-privilege values scoped to the destination project.
- Do not share secret values in support channels.
Related docs
Need beta access?
Miglify is currently in controlled private beta.