BackupBuddy vs. blogVault – Moving to a new domain

WordPress users are sometimes posed with the challenge of moving their sites to a new domain. Developers juggle between staging and live deployments for the sites they build. Users may want to get a new URL for their site. Irrespective of the reason, the process of migration is tedious and error-prone. In such a case having a plugin that can aid you in making migration, a smooth experience is undoubtedly a blessing. Let us look at how the two popular plugins BackupBuddy and blogVault fare when it comes to moving your site to a new domain.

BackupBuddy

BackupBuddy provides two ways in which you can migrate your site to a new domain – manual method and magic migration. For the manual method, you need to upload your backup zip file manually to the new location. With magic migration, you only need to add the new location as a remote destination.

Both methods use the importbuddy.php script (also used for site restore) for migration which you must execute from your browser. The script takes you through 6 steps that are easy enough to understand and navigate through. Once completed, your site is successfully migrated to the new domain.

BackupBuddy rewrites all references to the old URL during migration. The plugin also adds a redirect at the end of a migration that’ll redirect you to the new domain when you attempt to open the older one.

One limitation of the script is that it won’t run if you already have WordPress installed on the new domain. While this isn’t an issue if the destination is a brand new domain, redeployment needs a complete cleanup of the site before migration. BackupBuddy is also known to have issues while handling large sites.

blogVault

blogVault has a relatively simpler migration process. Once you click Migrate Site, all you’ve got to do is enter the FTP credentials corresponding to the new domain and let blogVault do the rest. blogVault moves all your data including files and database and also rewrites the URLs.

blogVault doesn’t add any redirects at the end of migration. You must do this manually whenever you are ready to go live with the new domain. In other words, after your DNS server has been updated to the new location. You can watch the video on how to migrate to a new domain using blogVault for ,ore details. You can also refer to blogVault’s Migration FAQ.

Conclusion

blogVault’s migration is far simpler than BackupBuddy. It requires less intervention from the user and takes care of the migration automatically. It also works perfectly well with large sites.