A website hosting migration involves moving a website or application to a different hosting environment. Before choosing a provider, establish what needs to move, which services it depends on, who will handle each part and how you will check that everything works.
Your hosting decision should reflect how the website or application operates. Alongside capacity and cost, consider compatibility, maintenance, access, backups and the support your team will need.
A focused review at the start helps turn an uncertain move into a defined project.
Start with the reason for moving
Be clear about what the move needs to achieve.
You might need better support, more predictable performance, a suitable environment for a new application or clearer responsibility for maintaining the service.
Describe the problem in practical terms. For example:
- Pages become slow during busy periods.
- Your developers cannot access the tools they need.
- Suppliers disagree about who should investigate faults.
- Your current environment cannot support an application update.
- You need different backup or recovery arrangements.
These issues may have different causes. Slow pages, for example, could involve application code, database queries, third-party services or infrastructure.
Understanding the problem helps you assess whether a hosting move is the right response and what a replacement environment must provide.
Define what is included in the migration
A public website may be one part of a wider service.
There could also be a database, member portal, search service, document storage, staging environment or scheduled background tasks. Some components may move together; others may remain with their existing providers.
Build a short inventory before requesting a proposal.
| Component | What to establish |
|---|---|
| Website or application | Software, versions, configuration and deployment process |
| Databases and files | Where data is stored, its size and how it changes |
| Connected services | Integrations, search, payments and external APIs |
| Background tasks | Scheduled imports, notifications, reports and other automated processes |
| Domains and DNS | Who controls the records and which changes are required |
| How application messages are sent and whether business email is affected | |
| Staging | How the replacement environment will be tested before launch |
Mark anything you cannot confirm as an open question. Your current provider or application developer may need to supply the answer.
Check that the new environment fits the application
Different applications have different hosting requirements.
A content-managed website, a membership platform and a bespoke application may each need particular software, databases, deployment tools or operating arrangements.
Provide the prospective host with the requirements your developer can confirm. These should cover supported software versions, storage, expected usage, access requirements and the process for deploying updates.
Discuss how demand varies, too. A website supporting an event launch may have a different usage pattern from an internal application used steadily throughout the working day.
A suitable proposal should explain how the environment meets those requirements and identify any changes needed before migration.
Agree who will be responsible for what
Hosting, application maintenance and domain management are separate responsibilities. They may be supplied by one company or shared between several.
Clarify those boundaries before the move.
| Responsibility | Question to resolve |
|---|---|
| Hosting infrastructure | Who maintains the server or hosting environment? |
| Application maintenance | Who updates and fixes the website or application? |
| Deployment | Who transfers files, data and configuration? |
| DNS changes | Who can make the required changes, and who authorises them? |
| Testing | Who checks technical operation and signs off business functions? |
| Backups and recovery | Who manages recovery copies and performs restores? |
| Incident handling | Who investigates first and coordinates other suppliers? |
For example, a hosting provider may keep the infrastructure available while an application developer remains responsible for faults in the software. Both parties need to understand how they will work together.
The customer also needs a clear route for reporting problems.
Treat domains, DNS and email as part of the plan
Changing hosting does not necessarily require transferring your domain registration. However, it may require changes to the DNS records that direct visitors and connected services to the correct destination.
Establish who controls those records and how changes will be requested, approved and checked.
Review the relevant records and dependencies before making changes. A domain may support the main website, several subdomains, business email and third-party verification records.
Application email also deserves a separate check. Contact forms, password resets, member notifications and transaction messages may depend on a mail service or configuration that needs to work from the new environment.
Write down the changes required rather than assuming everything associated with the domain should move.
Plan testing, cutover and rollback
Agree how the new environment will be tested before directing live traffic to it.
Opening the homepage is only one check. Depending on the application, testing may need to include:
- Signing in and resetting a password.
- Submitting forms and receiving notifications.
- Searching, uploading or downloading files.
- Completing transactions.
- Running scheduled tasks and integrations.
- Using administration tools.
Give each important test an owner and an expected result.
You should also establish how data will remain consistent during the move. If people can continue submitting forms, placing orders or updating records, agree how changes made during migration will be handled.
The cutover plan should describe the order of changes, the expected service impact and who will decide whether to proceed.
Include a rollback plan: the circumstances that would trigger it, who can authorise it and how data created after the move would be handled.
Understand what recovery would involve
Ask what is backed up, how frequently copies are taken, how long they are retained and how restoration works.
Relate the answers to the business:
- How much recent data could you afford to lose?
- How long could the service be unavailable?
- Which functions would need to return first?
- Who would check the restored service?
Distinguish documented recovery objectives from demonstrated results. If recovery testing forms part of the proposed service, establish what is tested and what evidence you will receive.
Migration planning should also confirm when the new backup arrangements begin and how long the previous environment and its recovery copies will remain available.
Prepare a brief before requesting a hosting proposal
A useful initial brief does not need to describe every technical detail. It should give the prospective provider enough context to identify requirements and unanswered questions.
Include:
- The website or application you are considering moving.
- The reason for the move and the outcome you need.
- Your current hosting provider and application developer.
- Any available documentation about software and connected services.
- Known requirements for access, support and recovery.
- Your preferred timing and any important business dates.
- The information you still need help obtaining.
This gives everyone a clearer basis for discussing scope, responsibilities and the work needed before migration.
Talk through your hosting move with Strategies
Strategies provides bespoke hosting and management for websites and applications.
If you are considering a move, we can help you work through the requirements of the service in question, clarify supplier responsibilities and identify migration dependencies.
We start with the information available about your application and current environment. Where further discovery or technical verification is needed, we can agree that scope before planning the next steps.
Contact Strategies to discuss your hosting requirements. Tell us what you are considering moving, why you want to move it and which questions you need help answering.