Move from XAMPP to VXOST
Your projects, your databases and your virtual hosts come across. Nothing is converted and nothing is rewritten: it is the same Apache, the same MariaDB and the same PHP, in a folder with a different name.
⚠️ Every step ends with a check. Do not go on until the check says what it should: each step here needs the one before it to have worked, and a mistake at step two shows up as a confusing error at step five. Set aside an hour, and keep XAMPP until you are sure.
- Find out your MySQL root password, before anything else
The export needs it, and the most common reason this guide fails is finding out at the wrong moment that you do not remember it. If you never set one, it is empty — press return when asked.
If a WordPress site runs on this machine, the password is written in plain text in its configuration:grep -h 'DB_PASSWORD\|DB_USER' \ /Applications/XAMPP/xamppfiles/htdocs/*/wp-config.php \ 2>/dev/null | sort -u
⚠️ That is the password of a project, which is often but not always the root password. Try it; if MySQL refuses it, look inphpMyAdmin, which you have been opening without a password all along — in that case root has none and you press return. - Stop XAMPP, then export every database
⛔ One line at a time. The second command stops and waits for the password: paste them together and the shell hands it the next line as the answer, the export fails, and it leaves an empty file behind without saying so.sudo /Applications/XAMPP/xamppfiles/xampp stopapache sudo /Applications/XAMPP/xamppfiles/xampp startmysql sudo /Applications/XAMPP/xamppfiles/bin/mysqldump -u root -p \ --all-databases --routines --events \ > ~/Desktop/vxost-migration.sql
Check: the last line of the file must say that the dump completed. mysqldump writes it only when it reached the end: a file cut short by an error, a full disk or a closed window has a size, looks fine, and does not have that line.tail -n 1 ~/Desktop/vxost-migration.sql
Expected:-- Dump completed on 2026-…
⛔ Anything else, or nothing at all, means stop here. An empty file is almost always a wrong password, and MySQL will have saidAccess denieda moment earlier: the shell creates the file before the command runs, not because anything was written. A file that ends anywhere else is a partial export, and restoring it would give you part of your data without saying which part. Everything after this step needs a complete file. - Stop XAMPP completely
Both want port 80 and port 3306. Two servers on the same port give an error that explains nothing, and it is easy to read it as a broken install.sudo /Applications/XAMPP/xamppfiles/xampp stop
Check: nothing should be listening on those two ports any more.lsof -nP -iTCP:80,3306 -sTCP:LISTEN 2>/dev/null | head
No output is the right answer. - Install VXOST
Download the disk image from the download page and open it. Inside there are two things and an Applications shortcut to drop them on:
1. drag the VXOST folder onto Applications — that is the server;
2. drag VXOST.app onto Applications too — that is the app you will open every day.
⚠️ Wait for the copy to finish. It is 900 MB and the Finder shows no bar for the last part: if you eject the disk too early you get a half-installed folder, which fails later in ways that look like something else entirely.
Check: every piece must be there. Any line saying MISSING means the copy did not finish, and doing it again is quicker than anything else.for f in vxost bin/mysql bin/httpd etc/httpd.conf \ etc/extra/httpd-vhosts.conf www/projects; do \ printf '%-34s ' "$f"; \ [ -e "/Applications/VXOST/vxostfiles/$f" ] \ && echo ok || echo MISSING; done - Let macOS trust what you just downloaded
⛔ Do not skip this, or nothing below will run.
Anything that arrives from the internet is flagged, and the flag spreads to every file you unpack. macOS then refuses to run those programs, and what you see in the Terminal isKilled: 9
and nothing else — not what stopped them, not why, not what to do. In the Finder the same thing reads “Apple cannot check it for malicious software”.
This clears the flag from the VXOST folder only, and asks for your password once:sudo xattr -dr com.apple.quarantine /Applications/VXOST sudo xattr -dr com.apple.quarantine /Applications/VXOST.app
Check: a program from the stack must answer instead of dying./Applications/VXOST/vxostfiles/bin/mysql --version
It should print a version. If it still saysKilled: 9, the command above did not run on the right folder. - Start VXOST
From the app, or from the Terminal. The app is the one you will use every day; the Terminal is here because it tells you what happened, line by line.sudo /Applications/VXOST/vxostfiles/vxost start
Check: the dashboard must answer.curl -sI http://127.0.0.1/dashboard/ | head -1
It must sayHTTP/1.1 200. If it saysConnection refused, Apache did not start — most often because XAMPP is still running: go back two steps.
⚠️ Open the app now and let the setup wizard run to the end. It adds the name virtualhost to this Mac, so that https://virtualhost/dashboard/ works. Until you do, only the numeric address answers. - Import the databases
Same file as step 2, the other installation. The export carries the accounts and their grants with it, so the usernames your projects already use keep working — which is what makes it unnecessary to touch a single configuration file later.
⛔ One line at a time: both ask for a password. On a fresh VXOST it isroot, set when the package was built. It is not empty, and pressing return gets you Access denied.sudo /Applications/VXOST/vxostfiles/bin/mysql -u root -p \ < ~/Desktop/vxost-migration.sql
Check: your databases must be listed.sudo /Applications/VXOST/vxostfiles/bin/mysql -u root -p \ -e 'SHOW DATABASES;' - Move the projects
One folder at a time, so you can see what arrives. The web root is calledwwwhere andhtdocsthere, which is the one name that does change. Replacemy-projectwith the name of yours.sudo cp -R /Applications/XAMPP/xamppfiles/htdocs/my-project \ /Applications/VXOST/vxostfiles/www/projects/
⚠️ If the project writes files — uploads, a cache, a log — those folders have to be writable bydaemon, the user Apache runs as. Everything else can stay yours.sudo chown -R daemon:daemon \ /Applications/VXOST/vxostfiles/www/projects/my-project/storage - Carry the virtual hosts over
Open the old file beside the new one and copy your blocks across, changing/Applications/XAMPP/xamppfiles/htdocsto/Applications/VXOST/vxostfiles/www/projectsin every path.
⚠️ The whole path, from the first slash: replacing only the second half leaves/Applications/XAMPP/at the front, and Apache looks for the site inside the installation you are leaving behind.
⚠️ The matchingListenlines live in a different file,httpd.conf. Copy one without the other and the site answers nothing while Apache reports no error at all.
⚠️ Write them with the address,Listen 127.0.0.1:4000, notListen 4000. VXOST ships listening on this computer only, and a line without an address listens on every interface: the project becomes reachable by anyone on the same wifi, and nothing tells you. The lines you are copying from the old installation are the second kind. If you do want a project reachable from your phone, the network step in the app opens every port at once and knows how to close them again.
⚠️ The VXOST files are protected and ask for your Mac administrator password: open them withsudo nanoin the Terminal (Ctrl+O then Return to save, Ctrl+X to leave). The old file only has to be read.open -e /Applications/XAMPP/xamppfiles/etc/extra/httpd-vhosts.conf sudo nano /Applications/VXOST/vxostfiles/etc/extra/httpd-vhosts.conf sudo nano /Applications/VXOST/vxostfiles/etc/httpd.conf
Check before restarting, not after.sudo /Applications/VXOST/vxostfiles/bin/httpd -t \ -d /Applications/VXOST/vxostfiles \ -f /Applications/VXOST/vxostfiles/etc/httpd.conf
It must saySyntax OK. Only then:sudo /Applications/VXOST/vxostfiles/vxost restartapache
The app writes these two files for you when you press New project, with a backup and a rollback. This is the manual route, for what you already have. - Open your sites, and keep the old one for a fortnight
The addresses change by one word: a project that was on localhost:4000 answers on virtualhost:4000, and localhost keeps working. The database name, the user and the port are the same, the only thing that changed is which program answers.
Do not uninstall XAMPP the day you migrate. Everything that is going to surprise you surprises you in the first two weeks, and a folder you have not deleted is the cheapest backup there is. After that, drag the old folder to the bin and empty it. ⛔ Notrm -rf: the bin can be undone, one mistyped path cannot.