Migrating WooCommerce to GlassHosting

Print
  • 0

Migrating WooCommerce to GlassHosting

What this guide covers

Move an existing WooCommerce store onto GlassHosting managed web hosting with a clear prep list, DNS cutover, post-cutover verification (checkout, orders, email), and a rollback path. GlassHosting keeps the platform healthy; you own catalog, plugins, and go-live timing.

Prepare before you copy anything

  1. Inventory WordPress version, PHP version needs, active theme, and must-have plugins (especially payment, shipping, and tax).
  2. Take a full backup at the old host: database plus files (wp-content at minimum). Confirm the backup restores on a throwaway/staging copy if you can.
  3. Lower DNS TTL on the store domain (and www) well ahead of cutover—24–48 hours is typical—so the switch propagates faster.
  4. Provision the GlassHosting plan and note document root, PHP version, and how you will upload files (SFTP or supported migration tool).
  5. Schedule a short maintenance window. Tell staff when checkout will be briefly unavailable.

Move files and database

  1. Copy files to the new hosting account with a proven migration plugin or a disciplined manual dump/upload.
  2. Import the database. Prefer tools that understand PHP serialized data—naive search-replace can corrupt options and widget data.
  3. Update site URL / home URL for the new environment if you are testing on a temporary hostname first; keep production domain settings ready for cutover.
  4. Re-check payment gateway API keys, webhook endpoints, and any hardcoded old-host paths after the move.

DNS cutover

  1. Point apex and www A/AAAA (or CNAME where appropriate) to the GlassHosting targets provided for your service.
  2. Issue or renew TLS so HTTPS works on the live hostname before you announce go-live.
  3. Keep the old host available but prefer read-only / maintenance mode so new orders do not land on the old database after DNS flips.

Verify checkout, orders, and email

  • Cart and checkout: add a product, reach payment, complete a low-value live or sandbox order as your gateway allows.
  • Orders: confirm the order appears in WooCommerce admin and that stock/status updates look correct.
  • Email: confirm order confirmation and admin notifications arrive (check spam). If mail fails, ticket support with message IDs—not passwords—and review SPF/DKIM for your from-domain.
  • Cache: ensure page caches exclude cart, checkout, and my-account.
  • Webhooks: payment and shipping webhooks must hit the new URL, not the old host.

Rollback

If checkout or mail is broken after cutover and you cannot fix it quickly: restore DNS to the old host (TTL still low helps), keep GlassHosting as a staging copy, and open a ticket with timestamps. Do not delete the old host until verification passes and you have a fresh GlassHosting backup.

Definition of done

HTTPS padlock on checkout, a successful test order, order emails received, webhooks updating the new site, and a documented backup on GlassHosting. If any checkbox fails, roll back or hold marketing traffic until it passes.

When to involve GlassHosting support

Open a ticket from billing.glasshosting.com when the platform looks wrong: site unreachable after a change you did not make, SSL issuance stuck, mail authentication needing platform confirmation, or restore access you cannot complete from the client area. Include the domain, approximate timestamps, and what you already tried—never paste passwords, payment keys, or full wp-config.php secrets.

For store-logic questions (plugin conflicts, theme bugs, gateway sandbox vs live), say whether staging reproduces the issue. Skim related WooCommerce knowledgebase articles first; many “outages” are cache exclusions, webhook URLs, or DNS still pointing at the old host.

Security hygiene for stores

Use unique passwords for billing, WordPress admin, SFTP/SSH, and hosting control panels. Enable two-factor authentication wherever the account system offers it. Limit admin users, rotate credentials if they appear in a screenshot or shared doc, and keep payment gateway keys out of tickets and chat.

During incidents, distrust unsolicited DMs offering “free fixes” that ask for logins. GlassHosting support works through the client area ticket system.

Related links: billing.glasshosting.com · glasshosting.com · Managed WooCommerce hosting guide.


Was this answer helpful?

« Back