Changing WordPress Hosts in the UK: Include PHP Compatibility in the Brief
Moving a UK WordPress website to a new host? Include PHP dependencies, staging checks, enquiry handling and a release decision in the migration brief.
In this article
Illustrative editorial workspace; not a client website, incident or delivered system.
A hosting migration can quietly become a PHP upgrade as well. The destination plan may run a different runtime, provide a different set of extensions or handle scheduled work differently. If the migration quote only says “copy the website,” the business may discover those differences after the DNS change.
For a UK business, include PHP compatibility assessment in the migration brief before agreeing the release. The aim is a website that staff can operate on the new environment, with a clear record of what was checked and who owns each task.
Compare the environments before copying the files
Ask for an inventory of the source and destination runtime, required PHP extensions, resource limits, caching and scheduled jobs. Identify integrations that depend on the existing environment or on a specific outbound connection. Record the choices the new hosting plan allows the account owner to make.
Then identify the actual scope of the move: live site, staging, media, email, subdomains and any separate applications. A WordPress migration does not automatically include email hosting or every other service attached to the domain. A written boundary prevents a support disagreement from becoming a business interruption.
Keep application changes distinguishable from hosting changes
If the move includes a theme update, plugin replacement and PHP change, record each one. Combining them in a single unexplained release makes an unexpected failure harder to diagnose. A staging check should establish which changes are necessary for the destination and which are optional improvements.
The WordPress migration handbook distinguishes moving environments from changing site URLs. Your brief should do the same. Keep the current public URLs where appropriate, plan any intentional changes and make sure the developer knows whether the domain or only the hosting account is moving.
Create an acceptance list for the new environment
Choose representative pages, editing tasks, search, forms and integrations. Include custom upload or import functions if staff use them. Ask the developer to report the outcome of each agreed check rather than giving one broad “migration complete” statement.
Enquiry delivery deserves a named owner. Specify which inbox, CRM or other destination receives submissions and who will approve a clearly labelled test. If a change involves email settings, hosting support and the website developer may both need to participate. Do not assume that a page looking correct proves the whole enquiry journey works.
Plan the final data sync and release appointment
A staging copy becomes older as the live website receives enquiries and staff edits. Decide whether the final move uses a short content freeze, a final sync or another approved approach. State which data must be preserved and how the team will handle changes during the release window.
For a UK business using a remote developer, specify the appointment in a named time zone and identify the reviewer who can sign off the result. The release should also have a decision point for recovery. “Move it this evening” is not enough information when the host, developer and business staff have different schedules.
Request evidence before retiring the previous environment
Ask for the live runtime, destination confirmation, tested functions and any unresolved errors. Establish how the previous environment will be retained or retired, including responsibility for any sensitive copies of the website. Avoid leaving an unowned old installation online indefinitely.
Keep the migration record with the ongoing maintenance information. Include the new provider’s support route, backup arrangement and who can approve future runtime changes. The handover is much more useful when the next person can tell which platform is live and why the current settings were chosen.
Brief a developer on the whole move
Send the website URL, the current and proposed hosts, desired date and a description of custom functions. Mention whether you also want redesign work so it can be priced and approved separately. I can assess a remote WordPress migration and compatibility scope from India around those requirements.
If the main uncertainty is the runtime, begin with a PHP upgrade assessment. If your host has already applied a security patch and the site only needs validation, a security update review may be the more focused engagement. The right scope follows the actual environment, not a generic migration package name.
Related planning: PHP Upgrades for Dubai Business Websites: Plan English and Arabic Checks · WordPress PHP Updates for Australian Agencies: Plan Around Client Hours.
References reviewed 23 October 2026: Official technical guidance.
Written by
Jagjeet Singh
Full stack development, WordPress engineering and practical web products. I work with businesses, teams and agencies in India and worldwide.
Explore my work
