Sign inGet started
Migration

Move your site to a new server with minutes of downtime

Bigger server, new provider, newer OS. Your AI builds a matching stack on the new server, copies everything directly between the two servers while the site stays live, then does a short catch-up during a maintenance window you choose. The old server stays untouched as the way back.

Connect your server free See the prompt

Works with Claude, Claude Code, ChatGPT and Cursor.

How your AI does it

  1. STEP 1

    It looks at both servers

    Site size, database size, PHP version and extensions, database and search versions, Redis, cron, certificates and the web server config. It checks the new server has room and tells you the plan and the expected downtime before starting.

  2. STEP 2

    It builds a matching stack

    Same PHP minor version and extensions, same database and search engine major versions, same owner user and the same vhost on the new server.

  3. STEP 3

    First copy while the site stays live

    db_dump dumps the database with the site's own credentials, and transfer copies files and dumps straight from one server to the other with rsync. Nothing passes through the chat or through SudoWhizzy. Caches and generated files are skipped.

  4. STEP 4

    Tested before DNS

    On the new server, without going live: ownership, PHP-FPM pool, cron, cache and search settings, then a full test of the site with curl --resolve, and for Magento a reindex and cache flush. Every error is fixed before the switch.

  5. STEP 5

    A short maintenance window

    At the moment you choose: maintenance mode and cron off on the old server, a fresh dump, a catch-up copy that moves only changes, import, and the site is back up on the new server.

  6. STEP 6

    DNS and the way back

    Your AI tells you exactly which DNS records to change. The old server stays in maintenance mode, untouched, so switching DNS back is the rollback. The temporary copy key is removed at the end.

How the copy stays safe

  • The new server makes a throwaway ed25519 key just for this copy
  • The old server accepts it only from the new server's IP addresses
  • The key expires within 24 hours and can only read the folder being moved
  • It can only run rsync in sender mode; no shell
  • The old server's host key is pinned, so the copy cannot be redirected
  • transfer_close removes the key as soon as you are done

Tested on real servers

From our own test runs with Claude Code on fresh Rocky Linux 10 servers.

56 s

of maintenance when a live Mage-OS shop was moved to a raw Rocky Linux 10 server

21 min

for the whole move, including building a matching stack, in 99 tool calls

26 MB/s

server to server for 759 MB of shop files, never through the chat

Start with this prompt

Paste it into your AI with SudoWhizzy connected. It fetches the matching playbook and explains its plan before changing anything.

Using SudoWhizzy, move my site from server <old server> to server <new server>. Follow the migrate playbook (get_playbook). Look at both servers first and tell me the plan: what the new server needs, how big the copy is, and how long the site will be in maintenance mode. Copy files and database dumps with transfer, never through the chat. Ask me before the maintenance window and before anything is deleted, test the site on the new server before I change DNS, then tell me exactly which DNS records to change. Leave the old server untouched as the way back, and close the copy link at the end.

Move a shop or site to another server · all prompts

Which plan

Both servers must be connected to SudoWhizzy, so a migration needs a plan with at least two servers: Pro (5) or Agency (25). Pricing.

Questions

Do both servers need SudoWhizzy?

Yes. Both run the agent, which is how the new server can pull the files directly from the old one with a temporary, restricted key.

How long will my site be down?

Only for the catch-up: a fresh database dump, copying the files changed since the first copy, and the import. For our test shop that was 56 seconds. Your AI tells you its estimate before it starts.

What if something is wrong after the switch?

The old server is left untouched, in maintenance mode with cron off. Point DNS back at it and you are where you started. Deleting anything on the old server is your decision, later.

Can it move from another provider?

Yes, as long as you can install the agent on the old server. Provider does not matter: the copy goes over SSH directly between the two machines.

Safety on every task: destructive actions wait for your approval, /etc is saved before changes, and every action is logged. How it works.

More your AI can do

Magento and Mage-OS

Your Magento server, run by your AI

WordPress and WooCommerce

A fast, secure WordPress server, run by your AI

Fresh VPS

From an empty VPS to a secure web server, by asking

Hardening

Harden your Linux server without locking yourself out

Hacked site

Hacked shop or site? Find it, clean it, close the door

Connect your first server

Start free with one server in read-only mode. Upgrade when you want your AI to fix things.

Get started