Disclosure: This article contains affiliate links. I may earn a commission if you buy through them. This is a researched guide, not a claim of hands-on testing.
A WPX site migration should move the working site while preserving the domain, email routing, and integrations you intend to keep. The free migration offer can reduce hands-on transfer work, but you still need to define the scope and verify the result.
If this operating setup fits your needs, check the current WPX Hosting offer while you compare the requirements below.
Check the migration policy first
WPX describes eligible standard migrations as free and identifies exceptions. Its guide lists paid services for changed domains, certain re-migrations, and express migration. It also distinguishes supported multisite moves from unsupported conversion of a normal installation into multisite.
Describe your actual setup before assuming it fits: one WordPress site or multisite, domain staying the same or changing, hosted email or external provider, and any nonstandard application components. Ask for the scope and any charge in writing.
Inventory everything the site depends on
Record active themes and plugins, PHP requirements, storage usage, forms, scheduled tasks, checkout systems, SMTP providers, and external APIs. Note paid software licenses and whether moving the site affects activation.
Save the DNS zone and identify the authoritative nameservers. Keep MX and sender-authentication records for external email. WPX’s migration guide says third-party mail records must be supplied correctly; the team cannot recreate information you never provide.
A website can look normal while hidden business functions break. A newsletter integration, booking form, or payment callback may use settings outside the visible pages. Include those in the migration brief.
Take an independent backup
Create a current backup of files and database before sharing access. Store a copy away from the old host. Export essential content or transaction records separately if they would be difficult to reconstruct.
Use an access method appropriate for the migration team and remove temporary access after completion. Do not send administrator credentials through a public conversation. Keep the old hosting subscription active throughout the verification period.
Freeze avoidable changes
Agree on a migration window and pause article edits, theme changes, and plugin installations. If the site receives orders or registrations, ask the migration team how it handles data created after the first copy.
WPX’s policy notes that additional changes requiring another migration can be chargeable when the problem was not caused by WPX. A clear freeze and final synchronization reduce both missing work and avoidable fees.
A blog can often pause publishing briefly. A store may need a more careful transaction cutover. Do not assume the same process fits both.
Preview before switching traffic
Request or use the supported preview method. Check a representative set of pages and critical functions. Preserve the same URL paths where possible. If changing the domain, prepare a separate URL and redirect plan before the move.
Look for hard-coded old URLs, missing media, mixed-content errors, broken navigation, and incorrectly configured email sending. View the site logged out so administrator permissions do not hide visitor-facing problems.
Switch only the needed DNS layer
Follow the migration team’s confirmed instructions for website routing. If changing nameservers, copy the complete zone first. If changing only a website A record, preserve unrelated mail records.
Registration does not need to move just because hosting changes. Leaving the domain at its current registrar can keep the job simpler. A registrar transfer adds a separate set of eligibility and account concerns.
Keep both hosts available while DNS caches update and while you verify the result. Propagation is not a fixed promise that every visitor changes at the same moment.
Run an acceptance checklist
- Homepage, article pages, archives, and mobile menu work.
- HTTPS opens cleanly without unexpected redirects.
- Forms send messages to the intended destination.
- External email receives and sends correctly.
- Analytics and search verification remain present.
- Affiliate redirects still point to the intended programs.
- Scheduled jobs and integrations operate.
- Backup points exist on the new host.
For ecommerce or membership functions, use suitable test modes or low-risk validation agreed with the team. A homepage screenshot is not sufficient evidence that checkout and account access work.
After the move
Remove temporary accounts, update stored documentation, and take a fresh backup. Record the new hosting login, billing date, DNS setup, and support channel. Monitor errors and mail for a period before cancelling the old service.
Review any old hosting add-ons and subscriptions individually. Cancelling the host should not accidentally cancel a domain registration or mailbox you still need. Save the final receipts and cancellation confirmation.
Frequently asked questions
Does the free migration include changing my domain?
The policy treats domain-name changes as a paid exception. Clarify the exact scope before requesting it.
Will my external email move automatically?
Identify the external provider and preserve its records. Website migration and mailbox migration are different tasks.
Can I keep publishing during migration?
Only with an agreed synchronization plan. Otherwise new edits can be missed and cause repeat work.
Define success before you begin
Write the acceptance checklist, preserve a rollback option, and keep the old host available until it passes. The job is complete when business functions work, not merely when files exist at the new provider.
Next step
Check WPX Hosting through my affiliate link against the requirements above before purchasing. Compare the current checkout and renewal terms, and keep a copy of the offer you accept.
Sources and review date
Official documentation checked October 5, 2026. Features, offers, and account eligibility can change. Editorial recommendations are based on the documented scope, not independent performance benchmarks.
- WPX migration scope
- Managed hosting scope
- WPX backup restoration
- WPX control panel guide
Build the business behind the tools
The tools in this guide are part of a bigger picture. At Ecommerce Paradise, I teach how to build and run a high-ticket ecommerce business. Start with a clear business model, then choose the tools that help you execute it.
If you are still figuring out the model, read my high-ticket dropshipping guide. You will understand the relationship between your store, suppliers, customers, and profit before spending money on software.
For product research, use my high-ticket niches list to explore categories and narrow down your ideas. Go deep before you go wide.
Next, work through my supplier sourcing guide so you know how to research manufacturers and approach them about becoming an authorized dealer.
My business formation checklist helps you organize the legal and financial setup. Use it to prepare your questions and confirm the requirements that apply to your business.
Get help putting the pieces together
If you want me to help you work through your next decisions, check out my private coaching. Bring your actual questions so we can focus on what is holding you up.
If you want a complete business build, take a look at the done-for-you store service. Review the scope and choose the support that fits your situation.
Trevor Fenner is the founder of Ecommerce Paradise. His main projects are Ecommerce Paradise, Supplier Paradise, and Review Paradise, which is currently in development. TrevorFenner.com publishes research-based reviews and practical guides to online business tools and remote-work services, with clear affiliate disclosures.