Migrate WordPress
Move a WordPress or WooCommerce site from another host with an AI assistant, test the copy, then switch the domain.
Before you start
- You have what every migration needs: see Cut over and roll back.
- You know the site's WordPress version, and whether it runs WooCommerce or WooCommerce Subscriptions.
- The site is not a multisite with domain mapping, which cannot be moved this way.
What is particular to WordPress
- The site is created with a fresh WordPress, and the copy keeps the new site's
wp-config.php. Your table prefix, keys, salts and custom constants are carried over, so logins to the site survive. - Caching drop-ins are not copied.
object-cache.phpis kept only when the old site uses the Redis Object Cache plugin. - The hold deactivates SMTP plugins after each import. On a WooCommerce site it also stops renewals and scheduled sales from running on the copy.
- The assistant tests the home page, the login page, search, a post and a page. For a shop it adds the shop, a product, the cart, the account and the checkout.
What you decide
- Every change to the production environment.
- Which way to test before DNS moves.
- When to switch the domain.
Never complete a live payment on the copy. Set the gateway to its test mode for a test order, then back.
Start the move
Give the assistant your own values. It follows the migrate-wordpress playbook.
Use the Corefinity MCP prompt "migrate-wordpress" with domain: shop.example.com,
cluster: Northwind UK 1, old_host: ssh [email protected], version: 6.8.
Follow it step by step and tell me before anything that changes my account.Without cluster, the assistant uses a CoreCluster of yours with space, or creates a CoreStack site. Add site to move into a site that exists.
Related
Was this helpful?