Moving off XAMPP sounds like a weekend project. It isn’t. LampRabit uses the same database defaults as XAMPP, Apache still reads your .htaccess files, and your XAMPP folder stays untouched until you decide to remove it. Here’s the short version; the full XAMPP migration guide has every detail.
What you’ll gain
C:\xampp\htdocs\shopathttp://localhost/shopbecomesC:\lampRabit\www\shopathttps://shop.test, with a trusted certificate.- Several PHP versions side by side instead of one per XAMPP install.
- Mailpit catching every email, with no Mercury configuration.
1. Install LampRabit and your stack
Download LampRabit, open Services, and install Apache, PHP and MariaDB (plus phpMyAdmin if you use it). If your projects need a specific PHP version, install that too; you can have several.
2. Export your databases from XAMPP
Start MySQL in the XAMPP Control Panel, then either use phpMyAdmin (Export → Quick → SQL) or dump everything at once:
cd C:\xampp\mysql\bin
mysqldump -u root --routines --events --databases shop blog > C:\temp\xampp-dbs.sql
Skip XAMPP’s system databases (mysql, information_schema, performance_schema, phpmyadmin, test).
3. Stop XAMPP
Stop Apache and MySQL in the Control Panel. If they run as Windows services, untick Service so they don’t grab ports 80, 443 and 3306 at startup. Forget one? LampRabit names the XAMPP program holding the port and offers to stop it.
4. Copy your projects
Click Open www in LampRabit and copy your project folders from htdocs. Each folder becomes a site: My Shop becomes my-shop.test. Leave XAMPP’s own folders (dashboard, img, webalizer, xampp) behind.
5. Import your databases
Start MariaDB in LampRabit and import the .sql file with phpMyAdmin, or from the MariaDB card’s Open command-line client:
SOURCE C:/temp/xampp-dbs.sql;
6. Update URLs and settings
- Database: host
127.0.0.1, port3306, userroot, empty password. Same as XAMPP. - URLs: change
http://localhost/shoptohttps://shop.testwherever a project stores its own address (LaravelAPP_URL, WordPresssiteurlandhome). For WordPress, use WP-CLI’ssearch-replaceso URLs inside content change too. - php.ini tweaks: put them in a
.user.inifile in the project instead of editing a globalphp.ini.
7. Open your sites
On the Sites page click Apply changes (approve the one administrator prompt for the hosts file) and Trust certificate, then open https://shop.test.
Common snags
- Port 80 is already in use: XAMPP’s
httpd.exeis still running, often as a service. Use the Stop button LampRabit offers. - Database connection error: check the database exists in LampRabit’s MariaDB and the host is
127.0.0.1. - A project needs older PHP: install it on Services, then choose it for that site.
Once everything works, uninstall XAMPP with C:\xampp\uninstall.exe. Keep your .sql export for a while, just in case.
Still deciding? Read the XAMPP vs LampRabit comparison.
Frequently asked questions
Will LampRabit change or remove my XAMPP installation?
No. XAMPP isn't touched until you choose to uninstall it at the end, so you can switch back at any time.
What database credentials does LampRabit use?
The same as XAMPP: host 127.0.0.1, port 3306, user root, no password. Most project configs need no change.
Do .htaccess files still work?
Yes. LampRabit's Apache honours .htaccess (AllowOverride All), so rewrite rules work as they did in XAMPP.



