At your old host, access phpMyAdmin, you're going to prepare for the backup procedure.

Since a download and an eventual upload is required, you may want to reduce the size of the backed-up sql file. This step is not overly necessary and can be skipped if you prefer.

Select the database to be backed-up and click the Structure tab so as all the tables are listed in the main window. In order to reduce the eventual file size certain tables can be emptied, that is, all the records deleted, not the table itself. The tables that can be emptied are:

A tool that you will definitely need is a File Transfer Protocol ("FTP") client program. These programs are more or less explorer type programs in which files can be uploaded and downloaded from the server.

There are a number of freely available FTP client programs and here are a few:

• Smart FTP (31 Aug, 2008, no longer free)
• Filezilla
• Core FTP
• Cyberduck (for Mac)
• Google Search Results

In order to utilise an FTP client you must first set-up FTP accounts at your host. I'm assuming that this particular process doesn't require detailed explanation as most likely you would have been using an FTP client at your old host. Suffice to say, that at my host, when creating the addon domain names corresponding FTP accounts were created as well. If this is not the case with your host, simply follow the prompts to create an FTP account(s). Even if automatic and default FTP accounts were created I'd recommend purposely creating an FTP account that purposely points to a specified folder. That folder's sole purpose being to receive uploaded files. Once uploaded, they can be moved to where ever you want.

As seems to be the case these days most hosts are offering one free domain for your use. Obviously, if you are transferring from another host you already have a domain name registered and you will eventually be changing the nameservers at your domain registrar to point to your new domain. Don't do it now, that is the last step.

In regards to the 'free domain name' accept the offer and use that domain name purely for administrative purposes. I recommend not using the free domain name for public purposes. It's not a good idea for your host to also be your domain registrar (they will be for the free domain name), it only leads to problems down the track should there be any issues with your host. Effectively, your host could hold you to ransom as they hold the key, the domain name registration.

You should now have an SQL file, which is your backup database file, safely stored away in your computer. The next step is to transfer the contents of that file into a new database at your new host.

Firstly, access you new host, navigate to the cpanel pages, then to the database section and follow the prompts to create a new MySql database. Obviously, remember the database name and user name for later reference.

Once created, access phpMyAdmin and navigate to your newly created database. In the example that follows I created a new database named, "newdrupaldb". You will notice that there are no tables created as yet, that is what the following process will do. Click on the Import tab and you should see a screen similar to the following. Click on image for a detailed view

At your old host, access phpMyAdmin, you're going to backup your database(s) which will ultimately be downloaded to your computer.

Click the Export tab and a screen similar to the following should be displayed (click for larger image).

Firstly, it goes without saying that you need access to your old host in order to carry out any of the following procedures. If you haven't got access to your old host, then in a nutshell, you're stuffed.

The following pages will show the processes and procedures required in order to transfer a Drupal system from one server to another. The concepts though can be applied to any database driven application.

So you've been with a host for a number of months or years and now it's time to change for whatever reason.

The following is a guide as to the smoothest process possible. There are many steps involved and over the next few weeks I'll add various pages and update where necessary. I'll attempt to include as many screen shots as possible and in that regard I'll be basing everything on using cpanel and MySql. For those not using these tools I'm hoping it should be clear enough in order to translate the information to your tools of choice. The concepts will be the same regardless.

Well this is how I did it. Firstly, you should have a valid reason for wanting to change as the process of transferring files and setting up with a new host can be a daunting process. In my case I wasn't happy with my current host's performance. In short, my web site(s) pages were taking far too long to load and outages were becoming all to common. Who was the host I hear you ask? Servage.net. I've been with Servage since January 2007, so that's 16 months and still have about 5 or 6 months before renewal is due.

Even with 5 or 6 months remaining I couldn't continue with the level of performance I was getting. It was excruciating and something had to give; and it did. I bit the bullet and researched other hosting companies.

My first port of call were the various 'find a web host' type forums and I defy anybody to select a good host based solely on so-called independent reviews found in the threads of these forums. What one can establish is that it's a cut-throat business, margins are low and they're all out there willing to empty our pockets. I suppose that's called the marketplace.

I made a decision early on that cost was not going to be the sole determining factor but cost is a factor none-the-less. My whole research was based around shared hosting as dedicated servers were well and truly not within my budget, so in this regard, cost was an issue.

Short listing

Not much content published over the last week or so and the reason being is that I've changed hosting companies. Previously I was with Servage.net but it became apparent that I had to upgrade to a quicker system. I'm now hosted by Drupal Value Hosting.

It's no easy process changing hosting companies and I see it as two distinct phases:

1. Choosing a new host; and
2. Process of changing over.

For both of these topics I'm going to write up some short articles explaining the processes I adopted.

This site should now run consistently quicker than before and hopefully with not as many outages.