Migrate
Migrate
Guides for moving an existing app onto Stackap, with an inventory first and the known gaps stated before the steps.
Guides for moving an existing app onto Stackap, with an inventory first and the known gaps stated before the steps.
Each guide is based on a move that was actually done, and says which steps have been checked and which are still a plan.
A migration is worth doing when a hosting bill has grown and the app is conventional. It is not worth doing for an app that sits comfortably inside a free plan, or one that depends on features Stackap does not have.
Pages in this section
- Migrate from Vercel: Moving an app from Vercel to Stackap when the database stays put: variables, crons, domain and the Vercel-only settings that need recreating.
- Migrate from Supabase: Moving a Supabase database and storage onto Stackap: the tables and rows that copy, the functions that do not, and sign-in that blocks the move.
- Migrate from Vercel and Supabase: The steps, the inventory and the known gaps for moving an app from Vercel and Supabase onto Stackap, based on the first real move.
Stackap is in early access. Tell us what you run and we will reply with a straight answer about whether it fits.
Ask for an invitationLast updated .