<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Hostlic Blog]]></title><description><![CDATA[Hostlic Blog]]></description><link>https://hostlicuk.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 01 Nov 2026 13:08:57 GMT</lastBuildDate><atom:link href="https://hostlicuk.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Moving a WordPress Site to a New Host Without Downtime: A Practical Checklist]]></title><description><![CDATA[Back up, copy, test on the new server, then switch DNS. A step-by-step order that keeps your site online.]]></description><link>https://hostlicuk.hashnode.dev/moving-a-wordpress-site-to-a-new-host-without-downtime-a-practical-checklist</link><guid isPermaLink="true">https://hostlicuk.hashnode.dev/moving-a-wordpress-site-to-a-new-host-without-downtime-a-practical-checklist</guid><category><![CDATA[WordPress]]></category><category><![CDATA[Web Hosting]]></category><category><![CDATA[Devops]]></category><dc:creator><![CDATA[Hostlic Webhosting]]></dc:creator><pubDate>Tue, 27 Oct 2026 09:15:16 GMT</pubDate><content:encoded><![CDATA[<p>Moving a WordPress site between hosts sounds risky, but most problems come from doing the steps in the wrong order. If you copy and test everything on the new server before you touch DNS, visitors never see a broken site. Here is the order we recommend.</p>
<h2>1. Lower your DNS TTL a day early</h2>
<p>Find the A record for your domain and drop its TTL to 300 seconds (five minutes) about 24 hours before the move. When you switch servers later, resolvers will pick up the change quickly instead of caching the old IP for hours.</p>
<h2>2. Take a full backup</h2>
<p>You need two things: the files (everything under your WordPress root, especially <code>wp-content</code>) and the database. Export the database with <code>mysqldump</code> or your control panel's database tool, and download a copy of both to your own machine. Never migrate without a backup you can restore.</p>
<h2>3. Copy files and import the database on the new host</h2>
<p>Upload the files to the new server, create an empty database and user, and import your dump. Then update <code>DB_NAME</code>, <code>DB_USER</code>, <code>DB_PASSWORD</code> and <code>DB_HOST</code> in <code>wp-config.php</code> to match the new database.</p>
<h2>4. Test before you switch DNS</h2>
<p>Edit the <code>hosts</code> file on your own computer so your domain points to the new server's IP. Browse the site, log in to the dashboard, submit a form and check a few posts and images. Only you see the new server, while everyone else still reaches the old one.</p>
<h2>5. Issue SSL and check email</h2>
<p>Install a certificate on the new host (most hosts include free SSL). If your email lives with your hosting, recreate the mailboxes and plan the MX record change too, or email can go missing during the move.</p>
<h2>6. Switch DNS and keep the old host for a week</h2>
<p>Point the A record at the new IP. Thanks to the low TTL, most traffic moves within minutes. Keep the old account running for a few days so nothing is lost while the last resolvers catch up, then cancel it.</p>
<h2>7. Freeze changes during the window</h2>
<p>If the site takes orders or comments, avoid content changes between the backup and the DNS switch, or repeat the database export just before switching.</p>
<p>If you'd rather not do this by hand, <a href="https://hostlic.co.uk/shared-hosting.html">Hostlic web hosting</a> includes free website migration for new customers.</p>
]]></content:encoded></item></channel></rss>