Thinking about moving your sites to a new host? If both hosts have Cpanel, there are a few ways to do this.
First, the “full backup” method, explained here. This one is simplest, but doesn’t always work. The new host may not give you the access level you need to install the backup on that end.
The [...]
Thinking about moving your sites to a new host? If both hosts have Cpanel, there are a few ways to do this.
First, the “full backup” method, explained here. This one is simplest, but doesn’t always work. The new host may not give you the access level you need to install the backup on that end.
The second method is almost as easy.  From your cpanel backup:
- Download a home backup. It’ll save itself with a really long name involving backup, the domain name, the date, etc. You want to change that file’s name to username.tar.gz. By username, I mean what you use to log into your cpanel.
- Download any databases you have.
- Upload all this to the new host.
- If you had no databases, you’re done. Just point your nameservers over.
- If you had databases, there are a few more steps. The first is: go into MySQL Databases, and create the users and passwords for each database. Remember, if your username changed from one host to the next, you’ll have to change this in your config files (along with anything else you changed).
- Assign the databases to the users so they can actually connect (I’ve left this one out before!).
- For some reason, when I upload a database file just the way it comes out of the old Cpanel - database.gz - it creates a second, bogus database called databasegzkey. You can just delete that. (It may be that unzipping the databases on your hard drive first makes this not happen, but I don’t know. I stick with what I know works. And even if you don’t delete the bogus database, it won’t matter. It’s just taking up one of your available database slots.)