WordPress Migration with blogVault – Safe, Easy and Stress-Free
Migrate WordPress Using Backup Service blogVault
Over the years, I have moved many WordPress sites. And, over those years, I have tried many different methods to move those sites; manual migrations, cpanel transfer methods, various plugins and hired third parties. They all were challenging.
Migrating WordPress websites is a pain.
Every time I moved a WordPress site, it seemed like something went wrong. The database was too big, the wp-config.php file was not correct, the plugin was incompatible with the newest version of WordPress – it was always something. Then I found blogVault.
blogVault is an online WordPress backup service. I first discovered blogVault while looking for a better way to manage my WordPress backups.
Like migration, I had tried several different methods for backups (plugins, cpanel, direct database exports, others) but never felt satisfied that I had found a stable, reliable backup method.
After using blogVault for backups, I tried using the blogVault site migration feature to move a WordPress site. I was sold. The site transfer through blogVault was so simple and easy that I was laughing when it was done. Instead of the inevitable frustration of moving a WordPress site, blogVault did it without a hitch in less than 10 minutes. Wow!
Since that initial blogVault migration, I have used it to move all of my personal and clients WordPress sites.
So, What Is blogVault?
blogVault is a cloud-based backup service. They use Amazon S3 servers as well as their storage servers (located in Germany) to archive multiple redundant encrypted copies (9 copies in total) of your WordPress site and data. Each site is automatically backed-up daily and can be spontaneously backed up at any time.
Multiple copies of each site are archived over time, allowing for multiple restore points. In addition to automated backups, blogVault’s restore features are excellent. They offer dry-run test restores to a live working copy of your website to allow you to test your backup prior to overwriting your old site.
How Does blogVault WordPress Migration Work?
Once you have a blogVault account set up, blogVault will copy your WordPress site(s) and store it (them) on blogVault’s server network. To migrate one of your sites using blogVault, just set up a new account and database on the destination server and supply blogVault with the credentials. blogVault will then migrate your current (or any of the existing archived copies) of your WordPress site to the new destination server.
The service works very well, setting all the appropriate wp-config.php variables and even will do a site-wide search and replace of link URLs for site migrations to new domains. The process is super easy and seems fool-proof in my experience. Read on for a step-by-step overview of migrating your WordPress site using blogVault.
How To Migrate A Wordpres Site with blogVault – Overview
- Level: Basic to Intermediate
- Time: Minutes to Hours
- Costs: 1) Cost of new server account 2) Cost of blogVault subscription ($9/mo and up – first week free)
Project Big Picture
- Setup new server account for website destination.
- Create new database and database user for WordPress on new server account.
- Setup account on blogVault.
- Backup website to be migrated on blogVault.
- Select blogVault Migrate-Site function for website to be moved.
- Input FTP, destination folder and database information.
- Wait while blogVault migrates your website to the new server account.
How To Migrate A WordPress Site Using blogVault – What You Will Need
|Item||What I used||Cost|
|New Server Account||WiredTree Managed VPS Servers (highly recommmended!)||$49/mo and up|
|blogVault Account||blogVault Plan
||$9/mo and up (1st wk free)|
How To Migrate A WordPress Site With blogVault – Step by Step:
1. Set up a new account on your destination server.
- Many Linux servers use cpanel / WHM control panels (including my current VPS servers at WiredTree), so the following demonstrates how to set up a new account on your new server using cpanel.
- Sign into your cpanel WHM and create a new account (
Account Functions > Create a New Account). Input the domain name, password, email, and remaining fields and click “Create“.
- Verify and locate the new account in cpanel WHM (
Account Information > List Accounts). Once you have located the new account, click on the cpanel icon to navigate to the cpanel control panel of the new account.
2. Set up a new database and database user for the new destination account using cpanel.
- Once you have navigated to the new account cpanel control panel, scroll down and click on MySQL Database Wizard.
- Create a new database by choosing a unique name for the database. This name will be a suffix that cpanel adds to the account username. Once you have added a unique name, click Next Step.
- Create a database user for the newly created database by entering a unique name. Similar to the database name, the new database user’s name will be suffixed to the cpanel usersname of the cpanel account.
- Finally, set privileges for the new database user by selecting “All“.
- A confirmation screen should then display the new database and associated user. Record the database username and database name for the migration.
Of note, blogVault initially recommended installing a fresh copy of WordPress on the destination server prior to performing the migration. This no longer seems to be necessary.The half a dozen or so recent migrations that I have performed, I did so without installing WordPress on the new destination server account without a problem. All of these migrations completed without an issue and new instances of the sites worked perfectly.
3. Set up a blogVault account, then backup your WordPress website on your blogVault account.
- Prior to using blogVault to migrate a WordPress site, you will need a blogVault account and need to have at least one backup of your site completed. Use the Backup Now function if you would like to update your backup prior to migrating it to the new server.
4. Select the version of your WordPress website to move, then use blogVault’s Migration-Site function to move your WordPress.
- Prior to running the Migrate-Site function on blogVault, you may select one of the archived copies of your site by clicking on History to review and select an older version of the site to migrate.
- To migrate an archived version of the site, click on History to see the archived version of the site. The archive page will display changes between versions including plugin changes. Once you have selected the version of the site you would like to migrate, select Migrate-Site next to the version of the site you plan to move.
- If you would simply like to migrate the most recent version of you website, simply select Migrate-Site on the main dashboard page to the right of the site you would like to migrate.
5. Test backup prior to migration (optional).
- Prior to beginning the blogVault migration process, you can click on Test-Restore to create a live test instance of the version of the website you plan to migrate to the new server. This function will install a temporary install of the selected version of your site on blogVault’s servers, allow you to test it prior to migration.
6. Begin the blogVault Migrate-Site function.
- Gather the FTP and database credentials for the new destination server. You will need these to allow blogVault access to the new server and it’s database for the migration.
- Enter the FTP url (can be the server numeric IP address (example: 22.214.171.124) or ftp domain (example: ftp.yourdomain.com). Then enter the FTP username (should be the same as the account username generated by cpanel when you set up the new server account) and the FTP password (should be the same as the account password you used when setting up the new account with cpanel).
- blogVault will access the new account on the destination server and if successful, display the installed folders and files on the new account. Click on the desired destination folder for your WordPress site. Typically this is the public_html/ folder. Then click on Continue.
- Next, enter the destination site URL (the future address of the migrated site). The URL will be the same if you plan to use the same domain after the move, but are just changing servers. If you are moving the site and plan to use a new domain name for the site, enter the new domain name here. If you do change the domain name, blogVault will rewrite your hyperlinks to the new domain name.
- Then enter the database details. Database host is typically localhost and can be left as is. The database username and password will need to be in the same format as created by cpanel with the cpanelusername_youruniquename.
- There are advanced options available that allow for file only or database only transfers and options for servers requiring access via name servers. Click on Advanced Options to access these options.
- Once you have complete the form, click Continue to start the migration process.
7. Wait while blogVault completes the migration process.
- If everything is correct, blogVault will begin the migration process and provide you with a verification screen stating, “Scheduling” telling you your migration has been added to blogVault’s queue.
- Shortly after starting the migration process blogVault will walk through a series of migration steps with displayed verification messages including; Scheduling. > Verifying. > Scanning site. > Fetching files. > Installing files. > Creating database. > Completed.
- After the final Completed message is displayed, your website should be accessible and fully functional on the new destination server. Don’t forget to change the domain name servers (DNS) to the new server to direct your site traffic to the new account.Propagation of the domain name server change will take some time to be complete (up to 24 hours, but usually much quicker), so it is a good idea to leave the old copy of the website up for a few days.It is also a good idea to keep the old website on the old server until you are sure the new site is complete and functional. Although, with blogVault you should have many functional copies you could restore if needed.Remember to remove the old copy of the site once you are satisfied with the migration to avoid duplicate content penalties with google. You could also password protect the old site or add a robots.txt file to the old site to block search engine bots.
blogVault’s the bomb.
Migrating WordPress websites can be a huge pain in the ass. I had always dreaded it. Then I used blogVault. Not only is it the best backup option I have found, but by far, the best tool for migrating WordPress sites. Even if you would rather not use the service long term, try it to move one of your site, I think you will be impressed. Enjoy!