Edge Functions look like just another migration surface until you try to redeploy one you cannot see the code for. The difference between an automatic and a manual deployment usually comes down to a single question: does the migration tool have access to the source code?
Why Edge Functions are different from database rows
Rows can be read and written through the database API. Edge Functions are compiled and deployed artifacts — you cannot copy a function by SELECTing it. The source has to come from somewhere, and platforms do not expose the compiled bundle for export.
Detection versus source code access
Detection can tell you a function exists, what it is called, and which secrets it needs. Source code access is what lets a tool actually redeploy it. These are two very different levels of readiness.
GitHub-backed Edge Functions
GitHub-backed Edge Functions can be deployed automatically because Miglify can access source code through the connected repository. The function definition lives in a place the tool can read, so the deploy step becomes routine.
Supabase-detected-only Edge Functions
Supabase-detected-only functions require manual deployment because detection can identify function names but cannot export source code. Teams need to bring the source themselves and redeploy on the destination.
Why automatic deployment needs source code
An automatic deploy needs the exact function source, the runtime configuration, and the list of secrets. Two of those come from the repository. Without it, the deploy is guesswork.
Required secrets and environment variables
Even a fully automatic deploy still needs its secrets to be set on the destination. See our Supabase secrets setup guide and the Secrets and Environment Variables Migration guide for how to prepare secret names, destination values, and rotation.
Manual fallback workflows
- Locate the current source for each detected-only function.
- Package dependencies with pinned versions.
- Set the required secrets on the destination first.
- Deploy the function and run a smoke test before shifting traffic.
Testing after deployment
Invoke each function with a known-safe payload, verify logs on the destination, and confirm that any webhooks from third-party services reach the new endpoint.
How Miglify helps
Miglify shows which Edge Functions are GitHub-backed and which are detection-only, lists the secrets each one requires, and offers automatic deployment when source access is available. For detection-only functions it produces a manual checklist so nothing falls through the cracks. See also the Edge Functions Migration guide for a broader view.
Final thoughts
Source code access is the single biggest factor in how quickly Edge Functions can move. Connect the repository where possible, and plan a manual path for the rest. Read the Edge Functions Migration and Supabase secrets setup guides next.
Miglify keeps every step observable — analyze source, validate destination, and prepare rollback-aware runs before you cut over.