Moving a WordPress site to ASEOHosting

Moving a WordPress site to ASEOHosting means copying your files and database to our cPanel/WHM platform, pointing DNS at your new dedicated IP, and confirming everything works before you cut over. Because our servers run LiteSpeed and CloudLinux with a dedicated Class C IP per site, most migrations are a straightforward file plus database transfer. A dedicated IP here is a footprint-control measure, not a ranking boost; your content and site quality still decide how you rank.

Before you start: prepare and back up

A clean migration begins with a complete backup and a plan to avoid downtime. Never delete anything from your old host until the new copy is confirmed live.

1. Take a full backup on the source host: the WordPress files (including wp-content) and a database export. cPanel users can grab a full backup from Files > Backup; otherwise use a plugin such as All-in-One WP Migration or Duplicator.
2. Note your PHP version, WordPress version, and any custom php.ini or .htaccess rules so you can match them here.
3. Record your current DNS TTL. Lowering it to 300 seconds a day before the move shortens propagation when you switch.

Set up the account and move the files

1. Create the hosting account. When your ASEOHosting plan is provisioned, you receive cPanel credentials and your dedicated IP. If you have not ordered yet, see WordPress SEO hosting or reach us via contact us.
2. Add the domain in cPanel (it becomes the primary domain, or add it under Domains).
3. Upload your files. Use File Manager or SFTP on port 22 to place the WordPress files into public_html. If you used a migration plugin, upload only the plugin's archive and its installer.
4. Create a database and user in MySQL Databases, then import your .sql export through phpMyAdmin. Grant the user ALL privileges on the new database.
5. Edit wp-config.php to match the new DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST (usually localhost).

Test before DNS, then cut over

Verify the site on the server before the world sees it. Edit your local machine's hosts file to point the domain at your new dedicated IP, then load the site in a private browser window. Check the homepage, an inner page, an image, and wp-login.php.

1. Once the test copy loads correctly, update the domain's A record to your new dedicated IP at your DNS provider or registrar.
2. If you also manage email, migrate mailboxes and update MX records to avoid lost mail.
3. Remove the temporary hosts file entry and watch propagation. With a low TTL this usually completes within an hour.
4. Install an SSL certificate for the domain so the site loads over https. See SSL certificates.

After the move

Flush any caching plugin, confirm permalinks resolve (re-save them under Settings > Permalinks to rebuild .htaccess rules), and harden the install by updating core, themes, and plugins. WordPress publishes a solid hardening guide worth following. Keep the old host active for a few days as a fallback, then decommission it once analytics and search traffic look normal. For network moves and IP planning, see our migration FAQ.