A WordPress migration is mostly a controlled copy: files, database, configuration, DNS, and SSL. The mistake is treating it as a single upload. A clean migration keeps the old site available until the new copy has been tested.
1. Take a Full Backup
Before touching anything, take a full backup from the current host. You need two things:
- The WordPress files, including
wp-content/uploads, themes, and plugins. - The database, usually exported as an SQL file.
Keep the backup somewhere separate from the old hosting account. If the old host has a one-click backup tool, use it, but still make sure you can download the files and database.
2. Create the Website in Enhance
Add the domain to your TekLan shared hosting account in Enhance. Do not change DNS yet. Create the site, note the document root, and set the PHP version you want to test with. If the old site is very out of date, start with the PHP version it already supports, then upgrade after the move.
3. Copy Files and Database
Upload the WordPress files into the new document root. Then create a new database and database user in Enhance. Import the SQL database and update wp-config.php with the new database name, user, password, and host.
4. Test Before DNS Changes
Use a temporary hosts-file entry or staging URL if available. Check the homepage, admin login, contact forms, checkout, media library, and a few old posts or pages. Do not rely on the homepage alone; many migrations only reveal problems on deeper pages.
5. Fix URLs if Needed
If the domain is changing, update old URLs in the database using a tool that understands serialised WordPress data. Better Search Replace is a common option. Run a dry run first and keep the original database export until the new site is confirmed working.
6. Switch DNS
When the new copy is ready, update the domain's A record or nameservers. If email is handled elsewhere, preserve the existing MX, SPF, DKIM, and DMARC records.
7. Enable SSL and Final Checks
Once DNS points at TekLan, issue or confirm the SSL certificate and force HTTPS. Then check:
- Admin login works.
- Images load over HTTPS.
- Permalinks work.
- Forms send email.
- Scheduled tasks work.
- Caching is cleared and rebuilt.
If you want help moving a WordPress site, open a support ticket with the old host details and the domain you want to move.
Which TekLan Plan Fits a WordPress Migration?
Most brochure sites, blogs, and small business WordPress sites are a good fit for shared web hosting. Start there if the site has normal traffic, a modest plugin list, and no unusual server requirements.
Use application hosting when the site needs more predictable resources, SSH access, heavier WooCommerce usage, or tighter control over PHP and cron. Use VPS hosting only when you need full operating system control, custom services, or a non-standard stack.
Migration Information to Send Support
- The domain name and whether email is hosted with the current website.
- The current PHP version and WordPress version.
- Approximate file size and database size.
- Whether the site uses WooCommerce, memberships, bookings, or payment callbacks.
- Any plugins that handle cache, security, redirects, SMTP, or image optimisation.
For more background, read how to point a domain without breaking email and how backups work before changing DNS.
