Hosting, server & email

Hosting & Server Migration

A hosting move needs more than copied files. We identify the application, database, media, scheduled tasks and connected services, prepare the target and agree how to verify the move. The cutover plan sets out who approves the switch, what to check and when to use the rollback path.

Discuss this service All services

When this service is useful

When this is the right fit.

Your current host no longer supports the application or the required operating model.
A website or group of services must move while preserving established public routes.
A previous migration left missing files, broken jobs or uncertainty about which environment is authoritative.

Typical problems

Problems we can help solve.

A hosting move involves more than files, with runtime, database, DNS and scheduled dependencies at risk.
The full source and target inventory is incomplete.
DNS, scheduled tasks, certificates, mail or external callbacks are easy to overlook.
There is no tested cutover sequence, acceptance checklist or rollback decision.

What the work can include

Work shaped around your needs.

The final proposal is based on evidence and access, so the work remains relevant to the real environment rather than a generic package.

A source and target inventory with runtime, storage and integration dependencies.
A backup whose contents or restore path can be checked before transfer.
Target preparation and a repeatable transfer for the agreed application, media and database.
Pre-cutover checks of representative pages, forms, account paths and scheduled responsibilities.
A DNS and cutover sequence with an agreed change window and rollback decision.
Post-cutover verification and a handover identifying retained backups and support boundaries.

Delivery and verification

Clear steps. Checked at every stage.

Mesh Creation keeps scope, approval, verification and the recovery path visible throughout delivery.

Inventory the workload and define acceptance before moving it.
Compare target behaviour and representative data, then verify public routes after the authorised cutover.
Execute an authorised cutover, verify services and retain the agreed rollback path.

Scope boundaries

Agree the scope before work starts.

Access, dependencies, environments, acceptance, handover and ongoing responsibility are made explicit. Assumptions are recorded rather than hidden inside delivery.

What shapes the proposal

Data and media volume, current access and differences between source and target runtimes.
How new orders, edits or enquiries will be reconciled during the transfer window.
DNS ownership, certificates, scheduled jobs and external callback dependencies.
Whether mailboxes or unrelated applications are part of the agreed move; they are not assumed.

Provider outages, account approval and third-party propagation timing cannot be guaranteed.
Unsupported software remediation and unrelated application redevelopment are separate from the migration unless stated.

Frequently asked questions

Useful questions before starting.

Can you guarantee zero downtime?

No blanket guarantee is appropriate. The system, data-write pattern and provider controls determine the safest approach. We agree a cutover window and continuity plan, then verify the result.

Will my existing URLs stay the same?

A hosting-only move can normally retain public URLs. If the application or URL structure is also changing, we inventory and map those routes and verify agreed redirects separately.

Does a website migration include email?

Only when explicitly included. We identify mail and DNS dependencies so a website move does not unintentionally disturb them. Mailbox transfer and delivery configuration have a separate scope.

What happens if the new environment fails a check?

The plan identifies a retained baseline and rollback conditions before activation. The old environment is kept for the agreed recovery window, with any data created during cutover handled according to the migration plan.

Relevant work and guidance

Explore the next decision.

Plan search-sensitive URL changes
Additional route and content checks when the move also changes the website.
Backups and recovery planning
Define what can be restored and how the recovery route is verified.

Start a conversation

Share the context for your project.

Share the website address, current and proposed hosting platforms, the reason for moving and any fixed deadline. Access and credentials are arranged privately after the scope review.

Discuss this service

Start with the real constraint

What needs to work better?

Share the product, platform or workflow that needs to be built, modernised or made easier to operate.

Discuss a project View selected work