Migrate from Vercel to Stackr

Move a prebuilt Vite or static site in stages. Review your Vercel settings, compare your workload, and test a private preview before switching traffic.

Compare the deployment workflow

StepVercelStackr static hosting
BuildBuilds linked repositories using project settings. Build docsBuild locally or in GitHub Actions, GitLab CI, or Bitbucket Pipelines. Stage the generated ZIP.
PreviewPreview deployments run separately from production. Environment docsOpen a private preview from the staged release. Use Delivery for a named preview channel.
RestoreInstant Rollback can restore an eligible deployment. Rollback docsChoose Restore release on an earlier retained release in deployment history.

Compare a month of usage

Open Vercel Usage and select your project. Record 30 days of requests, transfer, and cost. Stackr's migration calculator compares request allowance, estimated response volume, and the p95 time to first byte you measure on each host. Match the route, region, and cache conditions for both measurements. Vercel usage docs

Stackr currently includes 10,000 requests per UTC calendar month across the projects in a workspace. All workspaces share a platform limit of 15,000 hosted requests per UTC day. Check your busiest day as well as your monthly total. Count asset requests as well as page requests, and keep any separate database, CI, and storage costs in the comparison. Stackr usage estimates

Stage the site before changing DNS

  1. In Stackr Delivery, open Import from Vercel. Use a short-lived Vercel token scoped to the source team to review the repository, branch, output directory, and domains. Choose the repository you want to link.

  2. Generate a CI workflow or build locally. Package the generated site with index.html at the ZIP root. For a linked Vercel checkout, vercel build --prod can produce static assets under .vercel/output/static. Vercel build command Build output docs

  3. Stage the ZIP and open its private preview. Test navigation, nested routes, and assets. Check any database integration on a separate live Stackr URL before moving the production hostname.

  4. Promote the tested release. If custom domains are available for the project, verify routing and HTTPS in Delivery before switching DNS. Keep a prior release available for rollback.

Keep your existing backend

Connect a hosted Supabase project you already own with its project URL and publishable key. Review allowed authentication redirects, row-level security, and application behavior on the target hostname. Check browser network restrictions before using another API with a static release.

Request-time rendering, Vercel Functions, middleware, and Server Actions require a compatible runtime or a separate backend. For Next.js pages that can render at build time, review static export support and test the resulting routes. Next.js static export guide