The short answer
Before moving WordPress, agree what the migration service covers, which business functions you will test, and how the final copy will capture new orders or enquiries. A homepage that loads is not a completed handoff. For a Liquid Web move, ask support to confirm the destination product and migration scope in writing; keep an application owner available for work outside server support. If your current hosting works, first identify the problem a move would solve.
Write a migration brief that exposes the dependencies
Create a short brief with four headings: what moves, what stays, what changes continuously, and who can approve the switch. List the WordPress site, database, media, subdomains and scheduled tasks. Record external dependencies such as payment services, inventory systems, email and a CDN. Put access details in a secure credential manager rather than a spreadsheet sent to everyone involved.
Liquid Web's preparation guide asks customers to identify external DNS, remote databases and API connections, including services that may need the destination IP allowlisted. It also advises testing the destination before changing DNS. [1] A successful file transfer cannot verify those outside connections.
Use a concrete brief: 'Move the existing site without changing its URLs; keep email at the present provider; preserve existing orders; verify member login and booking notifications.' Add a named owner beside each requirement. This gives the hosting team a specific job and helps you spot missing work before launch.
Separate migration assistance from application repairs
Liquid Web's Linux support scope includes assistance with supported backup products and specified server services. It excludes custom-code migration, plugin or theme development, database optimisation beyond connectivity checks, and troubleshooting services hosted outside Liquid Web. [2] Confirm how those boundaries apply to your chosen plan and migration request before purchasing assistance.
For a WordPress store, someone still needs to understand checkout extensions and any custom integration. Write three responsibility rows: provider handles the agreed server and transfer work; application owner handles code and plugin behaviour; business owner confirms that orders, enquiries and customer access are correct. Resolve any blank row before scheduling the switch.
Do not use the word managed as a promise that every broken plugin will be repaired. If custom code is essential and no one can maintain it, obtain suitable application support or defer the move. This guide does not establish a migration price or confirm that a particular transfer is included free.
Use the initial copy as a test environment
Liquid Web documents an initial sync, validation, customer testing and a final sync before the public switch. Its process copies the existing site, so existing faults can come with it. [3] Record known problems first and avoid adding an unrelated redesign to the same project.
Have the technical owner arrange private access to the destination using the migration team's preview instructions. Clearly label which browser or machine is showing the old server and which is showing the new one. Keep a dated backup of files and database, record where recovery would happen, and confirm who could restore it. Do not leave downloadable backup archives in the public website directory.
An isolated preview can still contact real outside systems. Before testing, disable unintended customer mail, scheduled charges and live payment actions on the copy. Use supported test modes and test accounts. Record configuration differences so you know what remains to verify after switching to production.
Test business functions with an acceptance worksheet
Liquid Web's testing guide calls for checking pages, links, WordPress administration and uploads, and relevant ecommerce or membership functions. [4] Turn that into a worksheet with five columns: task, expected result, destination checked, evidence, and owner. The examples below are suggested tests; they are not results from a migration we performed.
Compare a real content page and a known record between environments. Then check an operation that writes data. A page can look correct while a form, media upload or API request fails. When a test fails, record the URL, steps, time and error message so the migration team or developer can reproduce it.
For mobile visitors, complete the relevant task on a phone, including validation messages and confirmation screens. Treat missing orders, failed login and lost enquiries as launch blockers. Cosmetic differences can be documented separately if the business owner accepts them.
- Enquiry: submit a marked test message; locate its stored record and verify receipt by the intended team.
- Administration: log in with a test administrator and upload a non-sensitive image; confirm it renders on a test page.
- Store or membership: inspect a known historical record, then complete an authorised test workflow without charging a real customer.
- Navigation: check key old URLs, redirects, HTTPS and a deliberately missing page.
Define the data boundary, then switch and recheck
Liquid Web says the final sync follows customer approval and may require temporarily stopping source services to prevent new writes. It distinguishes DNS it manages from external DNS that the customer must update. [3] Agree that responsibility and the exact change window with the team.
Record the last order or registration included, the final backup, and how any later records will be reconciled. Keep mailbox migration separate from website notifications: identify what is moving and test send and receive behaviour where applicable. Preserve unrelated DNS entries when pointing web traffic at the destination.
Write rollback conditions before launch, such as repeated checkout failure or missing current records, and name who can invoke recovery. Reverting DNS does not merge two databases; plan how to protect data created after the switch. Retain the old service until acceptance is complete, repeat critical checks on the public domain, and remove temporary access after the handoff.
Before you decide
- Get the exact migration scope and unsupported application work confirmed.
- Record external dependencies, a recovery copy and the person responsible for each.
- Test writes, notifications and customer access as well as visual pages.
- Agree the final data boundary, DNS owner, rollback conditions and post-launch checks.
Sources & limits
This is a documentation-based guide, not a hands-on product test. Provider terms and exact configurations can change. Confirm the details that apply to your purchase.