Migrate from Vercel

This guide walks you through migrating your application from Vercel to Zeabur. If you’re looking for a single platform that handles both frontend and backend services — databases, caches, background workers — alongside your web application, Zeabur is a natural fit.

Before You Begin

• A Zeabur account.
• Your application source code in a Git repository (GitHub).
• Access to your Vercel dashboard.

Step 1: Connect Your Git Repository

Your Vercel project is already connected to a Git repository. Connect the same repo to Zeabur:

1. Log in to the Zeabur dashboard.
2. Create a new project and select a dedicated server (or purchase a new one).
3. Click Add Service → Git and connect your GitHub account.
4. Select the same repository your Vercel project uses.

Zeabur natively supports all major frameworks including Next.js, Nuxt, Astro, Remix, SvelteKit, Vite, and static sites.

Step 2: Transfer Environment Variables

1. In your Vercel project, go to Settings → Environment Variables. Copy each variable’s key and value.
2. In the Zeabur dashboard, click your service and go to the Variables tab.
3. Add your variables. Use Bulk Edit to paste multiple key-value pairs at once.

Step 3: Handle Framework-Specific Settings

Next.js

• No changes required. Zeabur auto-detects Next.js and builds it correctly.
• next.config.js features like rewrites, redirects, headers, and image optimization work out of the box.
• API routes and Server Actions work natively — Zeabur runs your Next.js app as a full server, not as serverless functions.
• If you use output: 'standalone' in your Next.js config, Zeabur handles it automatically.

Nuxt / Astro / Remix / SvelteKit

• These frameworks are auto-detected and built with their standard build commands.
• No framework-specific configuration changes are needed.

Static Sites (Vite, Create React App, etc.)

• Zeabur auto-detects static builds and serves them with a built-in web server.
• If your project has a vercel.json with custom routing, you may need to configure equivalent redirects in your framework’s config.

Step 4: Vercel-Specific Features Mapping

Some Vercel features map differently on Zeabur:

Step 5: Add Backend Services (If Needed)

One of the main reasons to migrate from Vercel is to consolidate your entire stack in one platform. On Zeabur, you can add databases and backend services alongside your frontend:

• PostgreSQL, MySQL, MongoDB: Click Add Service → Database and select your database.
• Redis: Available as a prebuilt service for caching and session storage.
• Backend APIs: Deploy a separate backend service (Node.js, Python, Go, etc.) in the same project. Services within a project can communicate via private networking.

Step 6: Set Up Custom Domains

1. In the Zeabur dashboard, click your service and go to the Networking tab.
2. Click Generate Domain for a free .zeabur.app subdomain, or click Custom Domain to add your own.
3. Update your DNS records:
   • Remove the old Vercel CNAME record (usually pointing to cname.vercel-dns.com).
   • Add a CNAME record pointing to the Zeabur-provided target.

Step 7: Verify and Go Live

1. Push a commit to trigger a deployment, or click Redeploy in the dashboard.
2. Check the Logs tab to confirm your app builds and starts correctly.
3. Test all routes, API endpoints, and server-side rendering.
4. Once verified, switch your production DNS to Zeabur.

Key Differences: Vercel vs Zeabur

That’s it. Your Vercel application is now running on Zeabur as a full-stack platform with databases, backend services, and your frontend — all in one place. If you run into any issues, reach out on our community forum.