Build settings
Framework, install and build commands, output and root directory, and Node version.
Migrations
Hostingsurge brings over your project’s build settings, environment variables, domains, redirects and cron jobs. Check it on a preview URL, then point your domain here. SSL is issued automatically.
The import reads your Vercel project and sets up the same project on Hostingsurge.
Framework, install and build commands, output and root directory, and Node version.
Copied and stored encrypted. Values Vercel keeps hidden are listed for you to fill in.
Every domain on the project, including domain redirects, ready for the DNS switch.
Your redirects come along, so old links keep working after the move.
Scheduled jobs keep their schedule, and you can run any of them on demand.
If something can’t be carried over, the review tells you before anything is built.
Vercel keeps serving your visitors until the last step, and you check everything on a preview URL first.
Every source follows the same path: an analysis first, then a preview URL, then a guided DNS switch when you’re ready.
Build settings, environment variables, domains, _redirects and headers.
A public repository on GitHub, GitLab, Bitbucket, Codeberg, Gitea or your own server.
A private repository on any host, read through a read-only deploy key we generate for you.
Import through the Hostingsurge GitHub App and deploy automatically when you push.
A backup from All-in-One WP Migration, Duplicator or UpdraftPlus, or wp-content with an SQL dump.
Upload a full-account backup, or connect live for an analysis. Every site, database and mailbox is listed for you to choose.
Connect to any server over SFTP, FTPS or FTP and mirror one site: WordPress, PHP or static.
PostgreSQL, MySQL, MariaDB, MongoDB or Redis, restored into a managed database.
A static copy of a Wix, Squarespace or older site, made once you prove you own it.
Moving mailboxes too? Copy them over IMAP when you set up email on your domain.
Rather not do it yourself? Our team moves your site, app or database and hands it back ready for the DNS switch.
Where it runs today and what it is: a site, an app or a database.
Our team runs the import and checks everything on a preview URL.
It comes back ready for the switch. Your current host keeps serving until then.
The same import runs from the CLI and over MCP, with the same review and preview before anything goes live.
# Install the CLI and sign in npm i -g https://hostingsurge.com/cli/hostingsurge.tgz hostingsurge login # Import a Vercel project to a preview URL hostingsurge import vercel my-app # Or connect Claude Code over MCP claude mcp add --transport http hostingsurge \ https://hostingsurge.com/mcp
What happens to your site, your domain and your secrets.
No. Your current host keeps serving while the import runs and while you check the preview. Visitors move over only when you update DNS, and the SSL certificate is issued automatically as soon as your domain points here.
Only what the cutover lists. It shows exactly which records to change at your DNS provider and which to leave alone, like your mail records, so email keeps working. Changes usually take effect within minutes, sometimes a few hours.
Your visitors won’t notice, because the old site keeps serving until you switch DNS. A failed import shows the step it stopped at and its log, so you can fix the cause and run it again, or hand it to our team. Once you’re live, any deploy can be rolled back instantly.
Environment variables are stored encrypted and isolated to your team. Values Vercel keeps hidden, such as Sensitive variables, can’t be read by the import, so the review lists them and you enter them yourself. Nothing is guessed.
No. The import only reads from your current host, and nothing there is changed or deleted. Keep it running until you’ve switched DNS and you’re happy, then cancel it whenever you like.
Import it, check it on a preview URL and switch DNS when it looks right.