A website migration can go wrong in ways that cost cannabis businesses real money. A missing product category, broken age gate, failed checkout, or lost form submission can mean missed orders and frustrated customers. Knowing how to migrate a cannabis website means treating the move as a business operation, not just a file transfer.
The goal is simple: move your website, database, email settings, and key integrations to a cannabis-friendly hosting environment while keeping visitors, search engines, and customers on the right path. With a clear plan and proper testing, most WordPress and WooCommerce migrations can be completed with little to no visible interruption.
Start with a migration inventory
Before copying anything, document what your current website actually uses. Many small business sites have more moving parts than expected, especially stores that have added plugins, forms, payment tools, inventory systems, and marketing services over time.
Record your current host login, domain registrar login, WordPress administrator login, database credentials, and email account settings. If someone else built the site, make sure you have full ownership access before scheduling the move. A migration becomes much harder when the developer, former employee, or agency controls the account that holds your domain or backups.
For an ecommerce cannabis site, identify every function that affects a sale. This includes your product catalog, customer accounts, coupons, tax settings, shipping rules, checkout flow, payment processor connection, age-verification tool, and transactional emails. If you use a third-party menu, dispensary platform, appointment tool, or delivery service, write down where its embed code and API keys are stored.
A quick inventory should also include:
- Active WordPress theme and plugins
- Existing SSL certificate and redirects
- DNS records for the website and email
- Analytics, advertising pixels, and search-console verification
- Forms, newsletter integrations, and automated customer emails
This work may feel administrative, but it prevents the common problem of discovering a missing feature after the new site is already live.
Choose hosting that accepts your business model
General hosting providers do not always welcome cannabis, CBD, seed, or mushroom businesses. Some will host informational content but object to a store, product descriptions, or a connected payment workflow. Read the provider’s acceptable-use policy before moving, and be direct about what your business sells and how your website operates.
The right host should support the platform you use today and give you room to grow. For most operators, that means current PHP support, cPanel access, daily or automated backups, SSD storage, SSL capability, security controls, and support that can help when a plugin or database issue appears. WooCommerce stores also benefit from WordPress-focused performance settings and enough resources to handle traffic spikes during promotions.
Server location can matter, but it is not the only performance factor. A US-based audience generally benefits from US server infrastructure, while caching, image optimization, plugin quality, and the size of your product database all affect page speed. The lowest monthly price is not automatically the lowest-cost choice if slow support or limited backups leave your store unavailable during a busy weekend.
Create independent backups before the move
Do not rely on a single backup created by either your old or new host. Download an independent copy of your website files and database before the migration begins. For WordPress, your files include themes, plugins, uploads, and configuration files. The database contains pages, posts, customer records, orders, settings, and much of the information that makes the site function.
If you run WooCommerce, make a note of the exact time the backup was created. Any orders placed after that point will not be included in the original database copy. This is why store migrations need a planned cutover window, ideally during a lower-traffic period.
Also save copies of your DNS zone and email settings. Website email and domain email are often connected but separate services. A poorly handled DNS change can leave the website working while staff cannot receive order notifications or customer inquiries.
Build and test the new site before changing DNS
The safest approach is to install the website on the new server first, then test it using a temporary address, staging environment, or local hosts-file preview. Do not point your domain to the new server until the site has been checked by someone who understands the business side as well as the technical side.
Start with the basics. Confirm that the homepage loads, navigation works, images display, pages are not missing, and the admin area is accessible. Then test the functions that affect compliance, customer confidence, and revenue.
For a cannabis-related store, review product availability messaging, age gates, location restrictions, medical disclaimers, and terms pages. Rules vary by state and by product category, so a migration is a good time to confirm that your website reflects your current operations. Hosting cannot make a business compliant, but your site should not accidentally lose the controls and disclosures you have already put in place.
Next, test the purchase path. Add a product to the cart, apply a coupon, select shipping or pickup options, and complete a test transaction using your processor’s approved test mode where available. Confirm that order emails reach both the customer and your team. If live-card testing is necessary, use a small test order and refund it immediately after confirmation.
Check contact forms, newsletter signups, account creation, password resets, search, mobile navigation, and any embedded menu or booking tools. A site can look correct on desktop while failing on a phone, where many customers will actually browse and buy.
How to migrate a cannabis website with minimal downtime
Once the staging copy passes testing, plan the final synchronization. Put a short maintenance notice on the old site if needed, or schedule the move during your slowest sales hours. The objective is to capture any changes made since your original backup, particularly new orders, customer accounts, form entries, or inventory updates.
For a content-only site, the final sync is usually straightforward. For a WooCommerce store, pause order-taking briefly if possible, take a fresh database backup, import the latest data to the new server, and run one more checkout test. This small interruption is often safer than allowing orders to land in two different databases during the switch.
Then update the domain’s DNS records to point to the new hosting account. DNS propagation can take time, although many visitors will see the new server quickly. Keep the old hosting account active for several days rather than canceling it immediately. That gives you a fallback if a record, file, or configuration detail was missed.
Do not forget email-related DNS records such as MX, SPF, DKIM, and DMARC. If your email is hosted through Google Workspace, Microsoft 365, or another provider, those records must remain intact. Incorrect email authentication records can cause receipts and customer replies to land in spam.
Protect rankings, URLs, and existing traffic
A migration should preserve your existing URL structure whenever possible. Changing hosting does not require changing page addresses, product slugs, categories, or permalink settings. Keeping URLs stable reduces the risk of broken bookmarks, paid campaign errors, and search visibility losses.
If you must change a URL, create a permanent 301 redirect from the old page to the most relevant new page. Avoid sending every old page to the homepage. Search engines and visitors both need a clear destination that matches what they expected to find.
After launch, verify that your SSL certificate is active and that both the non-www and www versions of your domain resolve consistently. Check a sample of important pages, product pages, category pages, and blog posts for mixed-content warnings, redirect loops, and 404 errors. Review analytics and order activity closely for the first few days.
Keep a rollback plan, even after testing
No migration plan is complete without a way back. Keep the old site and its database backup available until the new installation has processed normal traffic successfully. If a major checkout, database, or email issue appears, you need to know who will make the call, how DNS will be restored, and which backup represents the last known good version.
For business owners who do not want to manage server files, database imports, and DNS records alone, hands-on migration support is worth considering. Weed Hosts works with cannabis-related businesses that need a hosting provider willing to support the industry, with technical help available when the details become more than a simple WordPress transfer.
A careful migration gives your business a cleaner foundation for the next product launch, promotion, or growth phase. Take the extra time to test the customer journey before visitors arrive. Your customers should notice better performance, not the move behind it.