How to Transfer a WordPress Site to BlueHost
Website migrations are complicated, and these complexities are not always made easier by using a WordPress blog or site.
To ensure a successful migration, many steps must be completed in the correct order.
If done incorrectly, you may experience website downtime. Please read this entire guide before beginning your website migration.
Step One: Create Your New BlueHost Account
I recommend BlueHost because of its dependability and cost-effectiveness.
Furthermore, in my experience, their customer support has been excellent, which is especially useful when doing something like migrating your website.
Use this link to get a BlueHost package at a discounted rate of $2.75 per month.
Bluehost provides a variety of packages.
Most people will be fine with the Starter plan (if they are only hosting one site), but if they are hosting multiple sites, they should upgrade to the Plus plan.
Step 2: Add FTP Access to Your Existing Hosting Account
Navigate to FTP Accounts in your existing hosting account’s cPanel, which is usually under the “Files” heading.
Fill in the user name and password to create a new FTP account. Often, a file path under “Directory” will be created automatically. Remove this file path entirely so that your new FTP account has ROOT access.
Check that the quota is set to “Unlimited” and then click “Create FTP Account.”
Make a note of your new FTP account password. The new account should be visible at the bottom of this page.
Next to the new account, click “Configure FTP Client,” and then record the User Name, Host Name, and port number.
Step 3: Get Filezilla.
Filezilla is the most widely used free FTP client. This software is available for download here. After downloading the installation file, click “run” to begin the installation process.
Step 4: Establish a Connection to Your Server
Once Filezilla is installed on your computer, launch it and select “Site Manager” from the “File” menu.
You’ll be configuring the connection to your existing server here.
Enter the above-mentioned hostname and port, followed by your username and password.
To begin the connection, click “Connect.”
If you’re having trouble connecting, try adding @yourdomainname.com to the User Name. If that doesn’t work, you may need to contact your hosting provider for assistance.
Step 5: Save Your Files
Create a new file folder on your local machine to which you will be able to transfer all of your website files and remember their location.
When you’re in Filezilla and connected to your server, use the top right window to navigate to the file folder containing your website files.
This is usually found in the public HTML file.
The files in the public HTML folder will appear in the bottom right window if you click on them.
Your website files may be located in a folder other than the public Html folder.
Locate and open the appropriate folder.
Navigate to the empty folder you created on your machine in the top left window.
Click the + icon to the left of the folder name to open it.
The empty folder will appear in the bottom left window.
Click the first folder in the RIGHT bottom window, then scroll down to the very last file, press and hold the SHIFT button, and click the last file.
The names of all files and folders should be highlighted.
Drag and drop all of the highlighted files and folders into the bottom LEFT window by holding down the CTRL key while clicking on any file/folder and dragging them over.
In the bottom window, the download will begin. This is going to take some time.WordPress contains an ENORMOUS number of files. Don’t worry, you’re just copying the files, not deleting them!
Go get yourself a cup of coffee. Alternatively, you can proceed to the next step while the download is still running.
Step 6: Save Your Database
Navigate to phpMyAdmin under Database in your existing server’s cPanel.
Click on your website’s database on the left.
Note: If you have multiple databases and are unsure which one to use, look at your website’s wp-config file and make a note of the database name.
That’s the one you’re after.
With this database file open on the left, go to the top menu of phpMyAdmin and select “Export.”Keep the export mode set to “Quick” and the format set to “SQL.”Click the “Go” button.
This will save the SQL file to your computer. It’s a relatively quick process.
Step 7: Construct a New Database
Navigate to MySQL Databases in the cPanel of your new Bluehost hosting account.
Create a new database first. Give it any name you want next to the prefix you want, then click “Create Database.”
Next, scroll to the bottom of this screen to add a “User” to this database.
Add a new user name and password under “Create User,” then click “Create User.”
Select the user you created and the new database you created under “Add User to the Database,” then click “Add.”
Remember to write down the user and database names (including prefixes!).
Step 8: Submit Your Database
In the same way that you did before, log in to your new Bluehost server’s phpMyAdmin.
On the left, select the new database you just created.
Navigate to the top menu and select “Import.”
You can browse your computer and select the SQL file you just downloaded.
Select “Go” at the bottom of the screen.
This will upload your database, and your new DB will appear on the left-hand side of the screen for a brief period of time.
Step 9: Sign up for a Bluehost FTP account.
Create a new FTP account in Bluehost using the same method described above, remembering to write down your credentials.
Step 10: Connect to the BlueHost Server
Assuming your download is finished (DO NOT DISCONNECT IF IT IS NOT!
Wait until the transfer is complete! ), then, in Filezilla’s File and Site Manager, select “New Site.”
Connect to your Bluehost server using your new Bluehost FTP credentials and the method described above.
In your left-hand window, the local file containing your WordPress files and folders should already be visible.
Navigate to public Html or the file where you want to store your WordPress site in the right-hand top window, your server.
Using the method described above, move all files and folders from the bottom left-hand window to the right-hand window.
Once again,
Using the method described above, move all files and folders from the bottom left-hand window to the right-hand window.
Again, this will take some time. Take the dog for a walk.
Step 11: Make changes to the WP-config file.
Once all of the files have been uploaded, go to the file manager in your Bluehost cPanel. Then go to the folder where you uploaded all of your WordPress files. In the editor, open the wp-config.php file.
Change the DB NAME to your new database name, the DB USER to your new database user name, and the DB PASSWORD to your newly created password.
The DB HOST variable is normally set to ‘localhost,’ and you will not need to change it. If you have a VPS, the hostname may be different.
Step 12: Is there an SSL certificate?
If your current website has an SSL certificate, you will need to install one on your new hosting account for the same domain before you point your site over.
Contact Bluehost to ensure that the SSL is installed and ready to use.
Step 13: Configure Your Domain
After you’ve transferred your files and database, you can point your domain to Bluehost.
This can be accomplished by either changing the nameservers or creating DNS records.
Navigate to the domain registry where you registered your domain.
Choose your domain to manage DNS and navigate to the nameserver section.
Replace the nameservers with:
ns1.bluehost.com
ns2.bluehost.com
It may take up to 24 hours to propagate to all servers, but your site should be operational within 1–2 hours.
Continue to check your domain to ensure that everything is in order.
If you encounter a database error, double-check your config file for the correct credentials.
Please keep in mind that changing the nameservers will also change the email address to Bluehost.
Create new email accounts in your Bluehost account.
Please keep in mind that domains registered through GoDaddy frequently experience issues with nameserver changes, particularly when using SSL.
Rather than changing the nameservers, create DNS entries instead.