Moving from Server A to B


Since WesiteBaker is completely database-supported, the transfer of a WB installation between very different systems is not only possible, but also relatively simple.

  1. Export: Export the tables of the database on the old server and save them locally
  2. Backup: Back up all WB files from old server locally
  3. Upload: Uploading the locally backed up files to the new server
  4. Import: Import the local backup of the database tables into the new database
  5. Edit: Enter the access data for the new database in config.php

That's it.



The old description, a little more detailed, but not more accurate.

Author: Mathetos (from the WB forum), Klaus Weitzel (kweitzel)


Because Wesite Baker is completely database and PHP driven transferring your WB installation between very different systems is not only possible, but relatively easy. For this "How To" we will use generic terms to describe the two servers. Server "A" is your initial installation, or the "old" installation. You are wanting to transfer that installation to server "B", the "new" installation. Before we begin it's important that you have each of the following tools available and ready for your use.

  • FTP Client
  • Access to both Databases, particularly their respective Admin panels.
  • Notepad (or even better: Notepad2 from

STEP 1: Install WB on Server "B"

Install a new WB on server "B" as instructed described in the Documentation. Make sure that you have your database set up correctly and that the WB installation on server "B" has permission to access its respective database.

For future reference, we will assume that the root directory of both installations ("A" and "B") are located in a folder called "wb".

STEP 2: Backup the "config.php" file

Copy the "config.php" from server "B", located in the root "wb" directory, and paste a copy of it somewhere safe.

This file holds all the inportant information about how your server "B" installation is built, so we will need it after we transfer the server "A" files.

STEP 3: Transfer the WB files of server "A" to the server "B" root directory

Transfer the entire "wb" installation directory from server "A" to server "B" via FTP. You will be asked whether you want to overwrite these files. Hopefully, your FTP client gives you the option of clicking "Yes to all", otherwise you'll have to click "yes" to all 1,000 odd files one by one!

STEP 4: Overwrite the "config.php" on server "B" with your backup

Take the "config.php" that you previously copied to a secure location. Copy it to the root "wb" directory of server "B" (click "Yes" when asked to overwrite).

STEP 5: Exporting the server "A" database

Now you need to make a direct copy of the database from server "A". There are two methods for doing this.

  1. Use your database's "Export Database" feature. Go to the PhpMyAdmin panel on server "A". Select the table that WB uses, click "Export" and "Go". This will give you either a .zip or a .tar or an .xml file that you should download and put somewhere safely.
  2. Open PHPMyAdmin on server "A", and select the database which WB uses. Click the "EXPORT" Tab. Select all the tables used by your installation and choose "SQL" as the type. Then click "go" (towards the bottom right). You are then presented with a textarea with a lot of SQL Code. Select all of it and copy it. Paste it into Notepad.

STEP 6: Import that database into your server "B" database.

Depending on which option you used in step 5, use the corresponding step below:

  1. On server "B" go to the Admin Panel of your PHPMyAdmin interface. Use the "Import" function. Select the Exported database from server "A" and click "Go".
  2. On server "B" go to the Admin Panel of your PHPMyAdmin interface. Choose "rund SQL", paste the code from Notepad into this area and execute it.

STEP 7: Test your server "B" installation

Test the server "B" installation by viewing the both the frontend and backend. If all is well, then you're done. If you run into problems then post them at the WB forum.

You might get into trouble accessing the site if you do not reset the permissions and ownership if necessary