Migrating WooCommerce to GlassHosting

Migration outline

1. Inventory plugins, theme, and PHP version needs
2. Take a full backup at the old host
3. Provision GlassHosting web hosting / managed plan
4. Move files + database with a proven migration plugin or disciplined manual dump
5. Update DNS TTL low beforehand, then cut over
6. Reissue SSL, retest checkout and email
7. Keep old host read-only briefly as rollback

Gotchas

Serialized PHP data in the database can break naive search-replace. Use tools that understand serialization. Recheck payment gateway API keys after domain changes.

Measure before you guess

Open the resource graphs on panel.glasshosting.com during a normal play window and during a busy one. Write down approximate CPU and memory percentages alongside how the game felt. That habit turns vague “it lags” reports into actionable upgrades or config tweaks.

If graphs look calm while players stutter, ask whether the issue is client FPS, wifi, or a single loaded farm chunk. If graphs are pegged, stop adding content packs until you either tune view distance/entities or upgrade the GlassHosting plan from the client area.

When to involve GlassHosting support

Open a ticket from billing.glasshosting.com when the platform itself looks wrong: panel cannot start the process, allocations seem missing, or multiple unrelated networks cannot reach the service. Include service name, timestamps, and console excerpts without secrets.

For game-logic questions (plugin conflicts, datapack design), include what you already tried. Skim related knowledgebase articles first—many “outages” are EULA flags, edition mismatches, or whitelist misses.

Store-specific reminders

Always smoke-test cart, checkout, and email after changes. Keep staging separate from production payments. Page caches must exclude personalized shop endpoints. Document DNS and SSL ownership so renewals are not tribal knowledge.

When migrating to GlassHosting, lower DNS TTLs ahead of time, schedule a maintenance window, and keep the old host available briefly for rollback. Ticket support if TLS or mail authentication needs platform confirmation.

Security hygiene worth keeping

Use unique passwords for billing, panel, SFTP, and in-game admin features. Enable two-factor authentication wherever the account system offers it. Op sparingly, whitelist private realms, and rotate credentials if they ever appear in a public screenshot.

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

Quality bar

Definition of done for any change: server starts clean, two players join, critical plugins load, and a fresh backup exists. If any checkbox fails, roll back before opening the gates wider.

Scaling path

Start with honest capacity, watch graphs for a week, then upgrade from billing.glasshosting.com if peak usage is sustained—not because of a single spike during worldgen. Downgrading later is easier when you did not promise fifty plugins on a tiny plan.

Related links: panel.glasshosting.com · billing.glasshosting.com · glasshosting.com.