Website Migration to Hostinger Web Server
To provide a standardized process for migrating client websites—primarily WordPress—to DentalMarketing.com's Hostinger server, ensuring minimal downtime and data integrity.
1. Pre-Migration Checklist
- 🔲 Confirm site platform (WordPress vs non-WordPress).
- 🔲 Obtain necessary credentials:
- WordPress admin access (if applicable)
- Hosting account access (if migration is from another provider)
- FTP/SFTP or cPanel access (as a fallback)
- Domain registrar access to edit DNS settings
- WordPress admin access (if applicable)
- 🔲 Backup the existing live site before making changes.
2. Identify the Platform
WordPress:
- Visit the site and check for WordPress login URL:
- Try example.com/wp-admin.
- If redirected or blocked, right-click a site image (e.g., logo), open in new tab, and check if URL includes /wp-content/.
- Try example.com/wp-admin.
Non-WordPress:
- If /wp-admin doesn’t work and file paths don’t include /wp-content/, it’s likely a custom HTML/PHP, Drupal, or another CMS.
3. Export the Site (WordPress)
- Install All-in-One WP Migration Plugin:
- Log in to the client's WordPress backend.
- Go to Plugins > Add New > Search: All-in-One WP Migration.
- Install and activate it.
- Log in to the client's WordPress backend.
- Export Full Site:
- Go to All-in-One WP Migration > Export.
- Choose Export to File.
- Download the .wpress file.
- Go to All-in-One WP Migration > Export.
4. Set Up Site on Hostinger
- Create New Website:
- Log in to Hostinger.
- Click Add Website > Select WordPress.
- Set up a clean WordPress install.
- Log in to Hostinger.
- Access Admin Panel:
- (Important) Update DNS before accessing /wp-admin on Hostinger.
- Point the domain’s A Record to: 191.101.12.84.
- Set the www CNAME to point to the root domain.
- Point the domain’s A Record to: 191.101.12.84.
- Optional (advanced): Modify your local hosts file to map the domain to Hostinger’s IP for pre-launch testing without global DNS propagation.
- (Important) Update DNS before accessing /wp-admin on Hostinger.
5. Import the Site (WordPress)
- Log in to new WordPress install on Hostinger.
- Install the All-in-One WP Migration plugin.
- Upload the exported .wpress file.
- If file size exceeds limit, install the “All-in-One WP Migration Unlimited Extension” (internal team use).
- If file size exceeds limit, install the “All-in-One WP Migration Unlimited Extension” (internal team use).
- After import, confirm all pages, media, and plugins are working correctly.
6. Alternate Method (No Plugin Export Available)
If All-in-One export isn't available:
- Manually Upload Files:
- Create a custom PHP website on Hostinger.
- Upload client’s WordPress files (typically public_html folder).
- Create a custom PHP website on Hostinger.
- Create New Database:
- In Hostinger, go to Databases > MySQL.
- Create a new database, user, and password.
- In Hostinger, go to Databases > MySQL.
- Update wp-config.php:
Replace:
DB_NAME
DB_USER
DB_PASSWORD
DB_HOST (usually `127.0.0.1` or localhost)
- Ensure credentials match newly created Hostinger database.
- Import Database:
- Go to phpMyAdmin in Hostinger.
- Import .sql file.
- Go to phpMyAdmin in Hostinger.
Tip: You can also replace only critical folders (/wp-content/uploads, /themes, /plugins) into a fresh install if a full migration isn’t possible.
7. Post-Migration Tasks
- 🔲 Verify site loads properly using both root and www versions.
- 🔲 Confirm all internal links and media are functional.
- 🔲 Check plugin and theme compatibility on new server.
- 🔲 Confirm SSL certificate is active or set up SSL in Hostinger.
- 🔲 Submit updated sitemap to Google Search Console (if applicable).
- 🔲 Monitor site for at least 24 hours post-migration.
8. Notes & Best Practices
- Always change the database password when setting up on Hostinger.
- Avoid using the same config or credentials as on the client’s previous server.
- Document all changes made during the process.
- Communicate DNS changes and expected propagation time (~1–24 hours) to the client.