•

Moving a membership site to new hosting without losing members or orders

Moving a brochure site is mostly copying files. Moving a site with WooCommerce Subscriptions, a membership plugin, an events calendar or a CRM is different, because it’s a working system that doesn’t stop while you copy it. The risk isn’t that the move fails outright. It’s that it looks fine, and a week later you find renewals that didn’t run, members who can’t log in, or emails that went out twice.

This guide is for owners planning that kind of move, or halfway through one. For a simpler site, see moving WordPress to a new host.

Is this what you’re seeing?

  • You need to move a WordPress membership site to new hosting, and it takes payments, renewals or bookings every day.
  • You want to move from AWS Lightsail to SiteGround (or a similar managed host), and there’s no control panel on the old server.
  • The site is too complicated, or too big, for a normal migration plugin. The plugin times out or the archive never finishes.
  • You’re worried about migrating WooCommerce Subscriptions without losing customer data or missing renewals.
  • The hosting account is far bigger than the site seems to be, and nobody knows which files matter.
  • Since a test move, automatic emails or renewals have stopped, or something you automated stopped after moving hosting.

What usually causes it

When a membership site loses something in a move, it’s usually one of these.

Changes made on the old site after the copy

The database is copied at one moment. Anything that happens on the old site after that, such as an order, a new member, a renewal, a booking or a form entry, isn’t on the new site. When DNS switches, those records stay behind on the old server. How to tell: compare the newest order number, the newest member and the newest booking on both sites. If the old site has later ones, they were made in the gap.

Scheduled jobs running in two places, or nowhere

Subscription renewals, membership expiries, event reminders and CRM email sequences are all scheduled jobs. WooCommerce and many other plugins queue them in Action Scheduler, and they run when WordPress’s cron runs. During a move there can be two copies of the site, both trying to run the same jobs. After a move, the jobs can stop if the old server ran them with a real server cron job that nobody set up on the new one. How to tell: go to WooCommerce → Status → Scheduled Actions and look at the Pending and Past-due lists. A growing pile of past-due actions means jobs aren’t running.

A migration plugin that can’t cope with the size

Migration plugins pack the whole site into an archive. On a large hosting account that can include years of old backup archives, caches and temporary files, so the archive is huge, the plugin times out, or the import stops partway and leaves a half-copied site. How to tell: the plugin keeps failing at the same point, the archive is much bigger than your media library, or the new host’s disk fills up.

WooCommerce Subscriptions protecting itself

WooCommerce Subscriptions watches the site’s address. If it thinks it’s running on a copy of the site, for example on a temporary test address, it switches off automatic renewal payments and shows a notice about a duplicate site. That’s a sensible protection, but it means renewals can quietly stop if the wrong choice is made, or start charging from a test copy if the other wrong choice is made. How to tell: a notice in wp-admin about the site having moved or being a duplicate, and renewals switching to manual.

A new server that’s set up differently

The new host may run a different PHP version, use a different web server, have lower memory limits, or not have services the old server had, such as Redis for caching or its own email sending. Settings in wp-config.php or cache files can still expect them. How to tell: errors, slowness or missing emails that only happen on the new host, with the same files and database.

What you can safely try

Take a backup first, of both files and database, and keep a copy somewhere that isn’t either host. None of these steps changes the live site.

  1. Write down the numbers before you start: the newest order number, how many active subscriptions and members you have, the newest booking and the newest CRM contact. You’ll check the same numbers on the new site.
  2. List everything the site does by itself: renewals, expiry emails, event reminders, newsletters, scheduled posts and backups. The Scheduled Actions screen in WooCommerce → Status is a good starting point.
  3. Ask your current host how much disk space the account uses, and where. Old backup archives and cache folders don’t need to move. Don’t delete them from the old server yet: just leave them out of the copy.
  4. If you manage your DNS, lower the “TTL” (time to live) on the site’s records to around five minutes, a day or two before the move. That makes the final switch take effect faster, and it’s easy to put back.
  5. Test the new copy before changing DNS, using the new host’s preview or temporary address. Log in as a test member and click through the important pages. Don’t place real orders or let renewals run on the test copy.
  6. Pick a quiet time for the switch, and plan a short window where you don’t take new orders or sign-ups, so nothing is created on the old site after the final copy.
  7. Keep the old hosting for at least a couple of weeks after the switch. If anything turns out to be missing, it’s still there.

When to stop and get help

  • The migration plugin keeps failing, or the site is several gigabytes or more.
  • WooCommerce Subscriptions is showing a duplicate site notice and you’re not sure which option to choose.
  • The old server has no control panel and needs SSH, as many cloud servers such as Lightsail do.
  • You’re being told to run a search and replace on the database, or to import over an existing site.
  • Orders, members or bookings were made on the old site after the copy, and you need them on the new one.
  • Renewals take money automatically, so a missed or doubled renewal costs you or your members.

A real example

A membership and events site needed to move from an AWS Lightsail server to SiteGround. It ran WooCommerce, WooCommerce Subscriptions, Elementor, The Events Calendar, Paid Memberships Pro and FluentCRM, along with other functionality. The hosting held about 14GB of files, including media and old backups, and the database was several hundred megabytes.

Copying the whole server would have brought old backup archives, caches and temporary files along with it. So before moving anything, I went through the server to work out what the working site actually needed: WordPress itself, plugins and themes, uploaded media and the database tables, and what could be left behind, such as the backup archives, temporary files and caches. I paid most attention to the data that matters most on a site like this: WooCommerce orders, membership and events data, CRM records and the scheduled background actions.

I moved it by hand over SSH, with a database export and file transfers, rather than relying entirely on a migration plugin. Then I compared records between the old and new databases, including order counts, CRM records and scheduled actions, to catch anything that hadn’t come across properly. I tested the homepage and internal pages on the new host.

That’s the work up to the DNS change: the copy, the comparison and the testing. Switching DNS is a separate step. On a site like this it should only happen once the new copy checks out, and the same comparison needs repeating afterwards, to catch anything created on the old site in between. Most of the job was understanding which parts of a busy, actively used site were essential, rather than treating it like a static website.

Getting it fixed

I’ll look at the old server and the new hosting, tell you what needs to move and what can stay behind, and plan the switch around your quietest time. A move like this is WordPress support at £75 per hour, with an estimate before I start, and I’ll stop and tell you before going over it. If a move has already gone wrong and something’s broken, a WordPress repair is a fixed £119, which covers finding the problem and up to 90 minutes of fixing it.

Questions

Can someone move my WordPress site from AWS Lightsail to SiteGround?

Yes. Lightsail WordPress servers are often Bitnami installations with no control panel, so the files and database usually come out over SSH. SiteGround has its own migration tool, which suits many sites. For a large or busy one, I’d rather move it by hand so I control exactly what goes and can check it afterwards.

Can WooCommerce Subscriptions be migrated without losing customer data?

Yes. Subscriptions, customers and their renewal history are all in the WordPress database, which moves as a whole. Card details aren’t stored on your site: the payment provider holds them, and your site keeps a reference to them. What needs care is the timing, so renewals don’t run twice or stop, and the duplicate site check described above. If renewals have already stopped, see WooCommerce Subscriptions not renewing.

My site is too complicated for a normal migration plugin. What are the options?

Move the files and the database separately. The database is exported and imported on the new host, and the files are transferred directly between servers, leaving out backups and caches. It takes more care than a plugin, but you can see and check every step.

Will members need new passwords?

No. Their passwords are stored in the database and move with it. Some may need to log in again after the switch, which is normal.

How long will the site be offline?

The aim is for the old site to keep serving visitors until DNS points at the new one, so most visitors won’t see an outage. On a site that takes orders, you do need a short window where nothing new is created, so the final copy is complete. How long depends on the size of the database, and I’ll tell you before we start.

Do the old backups on the server need to move too?

Not to the new web space. Keep a copy somewhere safe, away from both hosts, and leave them out of the migration. Old backups and caches are often why a hosting account is so much bigger than the site. If the database itself is the large part, see why a WordPress database gets so big.

Written by Peter Claridge, who fixes WordPress sites for businesses across the UK from Reading. Last checked on WordPress 7.1, November 2026.