You run a small business site on GoDaddy shared hosting. The contract ends soon and you want a host that gives you direct SSH access and predictable pricing. Moving off GoDaddy feels risky because you are not sure what you can take with you and what you must rebuild.
What GoDaddy Lets You Export
GoDaddy gives you the basics you need to rebuild a typical site.
- Files: The file manager or any FTP client can download the entire
public_htmlfolder. - Database: If you use MySQL, phpMyAdmin lets you export a full SQL dump.
- WordPress content: The built-in WordPress exporter (
Tools → Export) creates an XML file that contains posts, pages, comments and custom fields. - DNS records: You can view existing A, CNAME and MX records in the dashboard and copy them manually.
These exports are file-based. They do not include server-side configuration such as custom php.ini tweaks or nginx overrides.
What You Cannot Take Directly
Some pieces of your existing setup stay behind GoDaddy.
- SSL certificates: GoDaddy's certificates are tied to its load balancers. You must obtain a new certificate after the DNS switch.
- Email mailboxes: The mail stores live inside GoDaddy's email system. You can export messages via IMAP, but you cannot move the mailbox itself with a single click.
- Server-level limits: CPU and memory caps set by GoDaddy disappear. TrueCore applies its own kernel-enforced limits, which you can see in the panel.
Knowing these gaps helps you avoid surprise downtime.
Plan The Transfer Step by Step
Below is a checklist that keeps the move under control. Adjust the timing to your own site size.
1. Download Files and Database
Open an FTP client, connect to ftp.yourdomain.com, and pull the whole public_html directory to a local folder. Then log into phpMyAdmin, select your database, and click Export → Quick → SQL. Save both artifacts.
# Example: pull files with lftp
lftp -e "mirror -c /public_html ./sitefiles; quit" -u user,password ftp.yourdomain.com2. Export WordPress Content (If Applicable)
In the old WordPress admin, go to Tools → Export, choose "All content", and download the XML file. This file will let you keep posts, pages and comments without fiddling with the SQL dump.
3. Capture Email State
Use an IMAP client (e.g., Thunderbird) to download all messages locally. Create a new mailbox on TrueCore once the migration is complete, then drag the saved messages into the new account. This manual step ensures no mail is lost.
4. Recreate SSL on TrueCore
TrueCore provisions a free SSL certificate automatically when your domain points to our DNS. After you change the nameservers, give the system a few minutes to issue the certificate. No manual CSR or private-key handling is required.
5. Set Up the New Site on TrueCore
Sign up for the plan that fits your traffic — your site space, SSH access and mailboxes are provisioned automatically. Add your SSH key in the portal, then upload the files you saved earlier with SFTP or rsync:
# Your domain still points at GoDaddy at this stage, so connect to the node directly
rsync -avz --progress ./sitefiles/ user@ember.truecorehosting.com:/sites/yourdomain.com/If you run WordPress, follow our one-click installer, then import the XML file via Tools → Import. For other CMSes, place the files in the web root and adjust configuration files to point at the new PostgreSQL or SQLite database.
6. Test With a Hosts Override
Before switching DNS, edit your local hosts file:
159.195.31.27 yourdomain.comVisit the site in a browser. Check that pages load, forms submit, and images display. Verify that email login works against the new mailbox.
7. Change Nameservers
When you are satisfied, log into your domain registrar and replace the current nameservers with:
ember.truecorehosting.comlitespeed.truecorehosting.comspark.truecorehosting.com
Propagation usually finishes within a few hours. Keep the GoDaddy account active until you confirm that traffic reaches TrueCore consistently.
8. Clean Up
After DNS has fully propagated and the SSL certificate is active, delete the old GoDaddy site to stop any accidental charges. Remove the temporary hosts entry on your computer.
Common Surprises and How to Avoid Them
- Broken mixed-content links: Old sites may still reference
http://resources. Run a search-replace on the uploaded files or use a plugin to force HTTPS. - Missing MX records: If you forget to copy MX entries, mail will stop flowing. Double-check them in the DNS dashboard before the nameserver swap.
- PHP version drift: GoDaddy often runs an older PHP version. TrueCore uses PHP 8.3 by default; ensure your code is compatible or adjust the required version in
composer.json.
By planning each piece—files, database, email, SSL—you can move off GoDaddy with minimal downtime and a clear understanding of what you are rebuilding. TrueCore's transparent pricing and straight-forward control panel make the post-migration life easier.