Migrate from Vercel

Bring your Vercel project to servers you own

Same repository, same framework, same git-push workflow. Most projects move over in minutes, and you can test everything on a preview URL before switching your domain.

Start freeChapong vs Vercel

Six steps

  1. Sign up on the Free plan, or log in.

  2. Create a site from the same Git repository (GitHub or Gitea). Chapong detects the framework and fills in the build and start commands.

  3. Copy your environment variables from Vercel into production, preview or shared scopes.

  4. Deploy a preview and click through it.

  5. Add your domain and update the DNS record to the target Chapong shows. HTTPS is issued automatically.

  6. Keep Vercel running until DNS has switched over, then remove the old project.

What carries over

  • Your Git repository and branches
  • Framework builds: Vite, React, Vue, Next.js, Nuxt, Astro and more
  • Environment variables (copied by you, scoped to production and preview)
  • Your custom domains, with HTTPS
  • Preview URLs per pull request

What to check

  • Next.js runs as a regular Node server (next start); features specific to another host’s runtime may behave differently
  • Serverless or edge functions: move them into a Node app or Da8a edge functions
  • Redirects and headers kept in host-specific config files
  • Any database or auth you connected through integrations: consider a Da8a backend

Or deploy from your terminal

The avoca CLI uploads a folder and skips a local .vercel/ folder automatically. The CLI isn’t on npm yet; until it is, use the dashboard or the management API.

CLI docs →

shell
$ avoca sites link my-site
$ avoca deploy                # preview
$ avoca deploy --prod

Move your first Vercel project today.

Start free and test on a preview URL before you switch DNS.

Start freeGetting started