Files & data
Inventory the website files, databases and persistent uploads. Keep a usable copy before the migration begins.
WEBSITE MIGRATION / A PLANNED MOVE
Website migration,
planned before cutover.
Map your files, databases, email and DNS before the move. Agree the transfer, test the destination and prepare a rollback plan before switching the live site.
Preflight reviewTest before cutover
A PLANNED TRANSFER
Prepare. Test. Then switch.
Current hostingWebsite files
Database & configuration
Database & configuration
New environmentCompatibility review
Isolated testing
Isolated testing
- Preserve a current copyBEFORE TRANSFER
- Validate the websiteBEFORE CUTOVER
- Review DNS & emailBEFORE SWITCHING
An illustrative workflow. Compatibility, timing, access and rollback responsibilities are agreed for each migration.
A MOVE WITH CLEAR DEPENDENCIES
Your website is more than its homepage.
Include the application, stored data and connected services in the migration inventory, as well as the pages visitors see.
Runtime & integrations
Check PHP or application versions, background jobs, extensions, redirects and third-party connections in the destination environment.
DNS, email & verification
Identify DNS ownership, mail routing, certificate requirements and the tests that must pass before the live site is switched.
MIGRATION PREFLIGHT
Check what needs to move.
Select your website type and destination. The checklist helps prepare a scope review; it does not transfer a website or verify live access.
0 of 3 planning items confirmed.
Complete the planning checklist, or request help with any items you cannot confirm.
Your preflight requirements
- Website
- WordPress website
- Destination
- Web hosting
- A complete copy of the WordPress files and database.
- A list of themes, plugins, PHP requirements and scheduled jobs.
- A plan to test URLs, forms and any store transactions before DNS changes.
Describe the requirements in your enquiry. Access credentials should be shared only through an agreed secure process.
THE MIGRATION PROCESS
From the first backup to the final checks.
Agree the scope and verification steps before scheduling a live change.
Keep the original service available. Retain the source and an independent backup until the migration has been verified and any agreed rollback window has passed.
Review & prepare
Confirm the site inventory, destination compatibility, data scope, access route and responsibilities.
Copy & validate
Move an agreed copy to the destination. Test content, forms, links, application functions and required integrations.
Plan the final change
Decide how to handle new orders, uploads or content changes. Confirm DNS, certificates, mail routing and the cutover window.
Verify & hand over
Check the live result, document any remaining tasks and agree when the previous hosting can be retired.
Platform reference: WordPress migration handbook. Exact migration steps depend on your software and hosting setup.
SET EXPECTATIONS BEFORE THE MOVE
What belongs in a migration scope?
Review as part of the move
- The websites, databases and data size included.
- Runtime compatibility and any required changes.
- Testing, DNS ownership and the cutover decision.
- Mailboxes, scheduled jobs and integrations that need attention.
- Backup, rollback and source-retirement responsibilities.
Confirm separately
- Website redesign or development of new features.
- Repair of unsupported themes, plugins or custom code.
- Paid software licences and third-party subscriptions.
- Mailbox transfers and domain registrations or transfers.
- Ongoing management after the agreed handover.
Migration does not automatically mean zero downtime. The final plan should state the expected interruption, dependencies and limitations for your website.
MIGRATION QUESTIONS
Before your website moves.
Can you migrate any website?
A review is needed first. Software compatibility, access, data size and third-party services can affect the approach. Unsupported runtimes or customised applications may require additional work or a different destination.
Will my email move with the website?
Not automatically. Website hosting, DNS and email may be operated separately. Include your mailbox provider, mail routing and any mailbox-transfer needs in the scope so email dependencies are considered before DNS changes.
Can I keep my domain with the current registrar?
A website move does not necessarily require a domain transfer. The plan should identify which DNS records need to change and who can authorise those changes, while preserving records used by other services.
Will the move have zero downtime?
That cannot be assumed. DNS caching, data changes and application dependencies can affect the cutover. Agree the maintenance window, final data synchronisation and rollback criteria before switching the live service.
Should I cancel my old hosting immediately?
Keep the previous service and an independent backup until the new environment has been checked and the agreed rollback period has passed. Confirm cancellation dates separately to avoid losing data you still need.
CHOOSE THE DESTINATION, TOO
Connect your migration to the right service.
Prepare your migration brief.
Bring the website platform, current environment and data that needs to move. Use those details to agree the transfer and verification steps.
