DIY Website Migration Checklist for Small Business Owners
A step‑by‑step guide to moving your website without tech support.
Why Migrate?
A website migration can address several practical risks that affect daily operations.
| Reason | Business impact |
|---|---|
| Avoid downtime | Customers cannot book appointments, place orders, or view product information when the site is offline. |
| Improve performance | Faster page loads help visitors complete actions more easily, which can boost conversions for clinics, restaurants, shops, and service firms. |
| Strengthen security | Newer hosting environments receive regular security patches, reducing exposure to common threats. |
| Meet compliance needs | Modern hosts often include tools for data‑privacy consent and secure data handling, helping you satisfy regulations such as GDPR or CCPA. |
If any of these areas feel weak on your current site, a structured migration can be a worthwhile investment.
Pre‑Migration Planning
A written plan keeps the project on track and makes it easier for anyone on the team to follow.
1. Choose the target platform
| Business type | Typical platform choice | Why it fits |
|---|---|---|
| Clinic | WordPress + medical‑booking plugin | Flexible content management and easy integration with appointment tools. |
| Restaurant | Shopify or Squarespace | Built‑in e‑commerce and menu‑display features. |
| Retail shop | Shopify or WooCommerce on WordPress | Strong product catalog and inventory support. |
| Service firm (e.g., coaching centre) | WordPress or Squarespace | Simple pages, calendar integration, and low‑maintenance design. |
2. Inventory all site assets
Create a spreadsheet (Google Sheets, Excel, or Airtable) with columns for:
| Column | Example entry |
|---|---|
| Page URL | /about-us/ |
| Content type | Blog post, PDF, image |
| Owner / reviewer | Jane (marketing) |
| Migration status | Pending / Completed |
Store the sheet in a shared cloud folder, set the permission to “Anyone with the link can edit,” and add a brief note at the top explaining how team members should update the Migration status column.
3. List plugins, widgets, and custom code
Record the name, purpose, and any licensing information. For custom JavaScript or CSS, note the file path and where it is used on the site.
4. Capture SEO settings
Export the current sitemap (most CMSs have a “/sitemap.xml” endpoint) and note:
- Canonical URLs
- Meta titles & descriptions (you can pull these with a free SEO crawler such as Screaming Frog’s free version)
- Existing 301 redirects (if any)
5. Back up the current site
Use the host’s backup tool or a reputable plugin (e.g., UpdraftPlus for WordPress) to create a full file and database backup. Save the backup in two locations:
- Cloud storage (Google Drive, Dropbox, or OneDrive)
- An external hard drive or USB stick
Choosing a Host, Platform, and Migration Method
Hosting models – side‑by‑side
| Model | Typical resources | Management level | When it makes sense |
|---|---|---|---|
| Shared | Multiple sites on one server; CPU & RAM are shared | Provider handles server updates, security patches, and backups | Small sites with low traffic; limited budget |
| VPS (Virtual Private Server) | Dedicated virtual slice of a server; more CPU/RAM | You manage the OS and software stack (or hire someone) | Growing traffic, need for custom server config |
| Managed WordPress | Optimised for WordPress; includes staging, automatic updates | Provider handles core updates, security, and backups; you focus on content | Non‑technical owners who want WordPress without server headaches |
Tip: Check each host’s SLA (service‑level agreement) for uptime guarantees and backup frequency before you commit.
Platform options – quick comparison
| Platform | Primary use case | Built‑in e‑commerce | Design flexibility | Typical cost structure |
|---|---|---|---|---|
| WordPress | Content‑heavy sites, blogs, custom apps | Via plugins (WooCommerce, Easy Digital Downloads) | High – thousands of themes & plugins | Free core; hosting costs apply |
| Shopify | Pure e‑commerce | Core feature | Moderate – theme store plus custom code via Liquid | Monthly subscription + transaction fees |
| Squarespace | Simple brochure sites & light e‑commerce | Built‑in but limited SKU count | Moderate – drag‑and‑drop editor | Monthly subscription (all‑in‑one) |
Cost‑benefit snapshot: website builder vs. traditional host
| Factor | Website builder (e.g., Shopify, Squarespace) | Traditional host + CMS (e.g., WordPress on shared/VPS) |
|---|---|---|
| Up‑front cost | Usually a monthly subscription; no separate domain fee if bundled | May need separate domain purchase and hosting fees |
| Ongoing cost | Predictable subscription; optional app fees | Hosting fee + possible premium plugins or developer time |
| Design control | Template‑based; limited custom code unless on higher plans | Full control via themes, child themes, and custom development |
| Maintenance | Provider handles updates & security | Owner or developer must manage updates, backups, security patches |
| Scalability | Easy to upgrade plans; some limits on product count or traffic | Scale by moving to VPS or dedicated server; more flexibility but requires technical steps |
Redirect implementation – manual vs. automated
| Approach | How it works | Pros | Cons |
|---|---|---|---|
| Manual 301 redirects | Add each rule individually in .htaccess (Apache) or nginx.conf (Nginx) | Full control; no extra cost | Time‑consuming for large sites; easy to miss URLs |
| Automated migration tools (e.g., All-in-One WP Migration, CMS2CMS) | Scan old site, generate a bulk redirect file, and import it | Faster for sites with many pages; reduces human error | May require a paid license; still need to verify the generated list |
When choosing a method, consider the size of your site and your comfort with server files. For a site with fewer than 100 pages, manual redirects are manageable; larger sites usually benefit from an automated tool.
Content Migration Steps
1. Export content from the old system
| Platform | Export method |
|---|---|
| WordPress | Tools → Export → “All content” (produces an XML file) |
| Shopify | Products → Export (CSV) and download the theme files via Online Store → Themes → Actions → Download theme file |
| Squarespace | Settings → Advanced → Import / Export (XML; note that some page types may not export) |
2. Import into the new platform
| New platform | Import steps |
|---|---|
| WordPress | Tools → Import → WordPress; upload the XML file. |
| Shopify | Products → Import (upload CSV); install a theme that matches the design. |
| Squarespace | Settings → Advanced → Import; manually rebuild any unsupported sections. |
3. Transfer media files
- Connect to the old server via FTP or the host’s file manager.
- Download the entire
uploads(WordPress) orassetsfolder. - Upload the folder to the new server’s media directory (
wp‑content/uploadsfor WordPress, the media library in Shopify/Squarespace).
4. Update media URLs
If the new platform stores absolute URLs, run a search‑replace on the database:
- WordPress – use the “Better Search Replace” plugin (search for
oldsite.comand replace withnewsite.com). - Shopify/Squarespace – most media URLs are relative, but verify any hard‑coded links manually.
5. Spot‑check pages
Create a short checklist for each business type and verify that key actions work:
| Business | Key page / action | What to test |
|---|---|---|
| Clinic | Appointment booking form | Submit a test request and confirm the confirmation email. |
| Restaurant | Menu PDF link | Click the link and ensure the PDF opens without errors. |
| Retail shop | Product image carousel | Navigate through images; check that “Add to cart” works. |
| Service firm | Calendar booking widget | Book a dummy session and verify the calendar entry. |
If anything is missing, retrieve it from the backup created in the pre‑migration stage.
SEO & Redirects
1. Build a 301 redirect map
- Export the old sitemap.
- Use a spreadsheet to list Old URL → New URL.
- For URLs that stay the same, you can still add a self‑redirect to be explicit.
2. Deploy redirects
| Server type | Where to add redirects |
|---|---|
| Apache (shared hosting) | Edit the .htaccess file in the site root. Example line: Redirect 301 /old-page/ https://newsite.com/new-page/ |
| Nginx (VPS or managed) | Add rewrite directives inside the server block and reload Nginx. |
| Managed WordPress hosts | Use the host’s “Redirects” UI (often found in the control panel). |
| Shopify | Use the “URL redirects” section under Online Store → Navigation. |
| Squarespace | Add redirects in Settings → Advanced → URL Mappings. |
3. Update internal links
Run the same search‑replace tool used for media URLs to replace old URLs inside content, navigation menus, and footers.
4. Submit the new sitemap
- Google Search Console – Sitemaps → Add a new sitemap →
https://newsite.com/sitemap.xml - Bing Webmaster Tools – same process
5. Monitor traffic after launch
Set up a basic monitoring view in Google Analytics (or the platform’s native analytics) and look for any abrupt drop in sessions during the first 48 hours. A noticeable dip may indicate missing redirects or blocked pages, so compare the live site’s URL list against your redirect map.
Testing & Quality Assurance
Run the checklist on at least two devices (desktop and a mobile phone). Record findings in a simple table and assign an owner for each issue.
| Test | Tool / Method | Expected outcome |
|---|---|---|
| Browser compatibility | Open the site in Chrome, Firefox, Safari, Edge | No layout breaks; all scripts run without errors |
| Responsive design | Resize browser window; test on a real phone or tablet | Buttons remain tappable; text stays readable |
| Page speed | Google PageSpeed Insights (free) | No critical warnings; recommendations are noted for future optimisation |
| Forms & checkout | Submit a test contact form; place a dummy order using a sandbox payment gateway | Confirmation email received; order status shows “test” |
| SSL & mixed content | Click the lock icon in the browser; run an SSL Labs test (free) | Certificate is valid for the domain; no “mixed‑content” warnings |
Document any issues in a table like the one above, add a Responsible column (e.g., “Owner”, “Developer”), and resolve them before the DNS switch.
Launch & Post‑Launch Checklist
1. Switch DNS
- Update the A record to point to the new host’s IP address.
- If you use a CDN (e.g., Cloudflare), change the “origin” server IP in the CDN settings as well.
2. Keep the old site accessible for 24–48 hours
Set the previous server to “maintenance mode” (most CMSs have a plugin or setting) so visitors see a friendly notice while you retain a fallback copy.
3. Monitor uptime
Create a free account with a service like UptimeRobot, add your domain, and set the check interval to 5 minutes. You’ll receive an email or SMS if the site goes down.
4. Communicate the change
- Email – Brief note: “Our website has been refreshed for faster loading and easier booking.”
- Social – Post a screenshot of the new homepage with a short caption.
5. Verify email flow
Send a test email from your business address to an external account and confirm that it arrives without bounce‑backs. This also confirms that MX records are still correct.
Common Pitfalls and How to Avoid Them
| Pitfall | Impact | Preventive action |
|---|---|---|
| Missing email forwarding | Customers’ messages bounce, potentially losing sales. | Before changing DNS, copy the existing MX records to the new DNS zone and test with a test email. |
| Losing custom code | Features such as a custom appointment timer stop working. | Save every custom .php, .js, or .css file in a separate “custom‑code” folder and note where it is referenced. |
| Overlooking mobile responsiveness | Mobile visitors abandon the site, hurting bookings or sales. | Test on at least two real devices (iPhone and Android tablet) before launch. |
| Skipping the final backup | No way to revert if the new site crashes. | Keep the full backup of the old site for at least one week after launch, stored offline or in a different cloud account. |
How HeyGrowin can help
HeyGrowin builds custom websites and provides tools—AI chatbots, CRM, booking systems, and inventory management—that can be bundled into your new site. Our team can also assist with migration planning, data import, and post‑launch monitoring so you can focus on serving customers. Learn more at https://heygrow.in.
Frequently asked questions
Do I need a developer to migrate my site?
Not necessarily. Most small‑business owners can handle the migration with the checklist above, but a developer can help with complex custom code or large data sets.
How long does a migration usually take?
It depends on site size; a simple site can be done in a few days, while a larger e‑commerce store may take a week or more.
Will my search rankings drop after migration?
If redirects are set up correctly and the new site is indexed, rankings should remain stable. Monitor traffic closely after launch.
