Can I migrate to deploybase from Netlify or Vercel?

Yes, if your site is a static build with an optional serverless function, deploybase is designed to accept it. The site provides a dedicated migration entry point for Netlify and Vercel users that lets you bring your existing settings with you, and it connects to the same Git providers you likely already use. The main caveat is that functions are in beta and only available on paid plans, so a migration that depends on functions is not a like-for-like free move.

What carries over

deploybase's own migration path is described as "Moving from Netlify or Vercel? Bring your settings with you." That means you do not have to rebuild your configuration from scratch — the intent is to reuse what you already have.

The deployment model you get after migrating keeps the workflow most Netlify/Vercel users expect:

• Branch previews — every branch gets a preview link, so pull requests stay reviewable.
• Instant rollback — production is described as "a pointer," so rolling back means repointing rather than rebuilding.
• Git-connected deploys — every push updates the site automatically.

Supported Git providers

You connect a repository rather than uploading a build artifact, so the first check is whether your host is supported:

If your Netlify or Vercel project is already wired to one of these, the migration is mostly a matter of reconnecting the same repo.

The three ways to get a site live

Migration does not force one route. deploybase offers three:

1. Ask your AI agent — paste a setup prompt into Claude, Cursor, or any MCP client; it fetches instructions, connects itself, and asks you for one key that only a person can create. This route currently needs a Git repository.
2. Drag and drop your files — no build, no repository. Up to 250 MiB on the free plan. Create an account, start a new project, choose "Upload a folder," and drag in the folder containing your index.html.
3. Push from Git — create an account, connect your repository, and push. Code in a functions/ directory runs beside the site.

For a Netlify/Vercel migration, route 3 is the closest match to what you already do.

What the deploy actually looks like

deploybase publishes a real build log, which is useful for judging whether your own build fits. In the recorded example (a Vite/npm site with one function):

• Queued: waited 1.7 s
• Cloned the repository: 0.0 s
• Built: 13.6 s (tsc --noEmit && vite build)
• Uploaded 12 files, bundled 1 function: 7.4 s
• Live 32 seconds after push

The site landed at eu-check.sites.deploybase.eu and the function at scan-eu-check.fn.deploybase.eu. If your Netlify/Vercel build is a standard static framework build, expect a similar shape — a short queue, a clone, a framework build, an upload, then live.

What to check before you commit

• Functions are beta and paid. The example function ran on a paid plan. If your Netlify/Vercel project relies on serverless functions, confirm plan and beta status before migrating.
• Functions get their own hostname. They are not served from the same path as the site — the pattern is <name>-<site>.fn.deploybase.eu. Any hardcoded function URLs in your frontend need updating.
• Forms have a no-backend option. deploybase lists "Forms without a backend," which matters if you currently use Netlify Forms.
• Hosting is European. If your reason for migrating is data location, that is the core selling point.
• Pricing is flat, in euros. Check the pricing page for current figures rather than assuming parity with your existing plan.

A practical migration sequence

1. Create a free account.
2. Start a new project and connect the same repository you use on Netlify or Vercel.
3. Bring your build settings across using the migration entry point.
4. Push a branch first and confirm the preview link renders correctly.
5. Move any function code into functions/ and update frontend URLs to the fn.deploybase.eu hostname.
6. Point production at the branch you trust, then add your own domain.

The migration is convenient for static sites and low-risk for anyone already on Git-based deploys. The decision point is functions: if your app depends on them, treat the move as a paid, beta-stage migration rather than a drop-in replacement.