Standard website & server migration

Move your website.
Keep your business running.

The same working application. A new host. A tested move.

We copy your website or server, reproduce the working environment, test the destination and coordinate the final sync and traffic switch. You receive a documented handover after the agreed checks.

You choose the destination. We check that it can do the job. The scope, price, maintenance window and rollback plan are agreed before cutover.

First review on us →Chat with us →

For new clients: one free review covering one application on one server or hosting instance. Review terms →

Test before switching

Check the application on the new host while the original keeps serving.

Destination issues reported

Know what is missing, incompatible or underperforming before accepting the move.

A controlled cutover

Final sync, traffic switch and a defined route back.

More than copying files

The website loads. But does everything still work?

A migration can look finished while mail fails, scheduled jobs stop, uploads land in the wrong directory or new orders remain on the old server. The new plan can also have limits that were never part of your old setup.

Hidden dependencies

Runtime versions, extensions, database permissions, filesystem paths and service settings determine whether the same application behaves the same way.

Writes during the move

Orders, messages and uploads keep arriving after the first copy. They need a final sync and an agreed point at which writes move to the new server.

A destination that needs work

Storage, networking, resource limits or missing services may need attention. Those findings belong in your handover, before you approve cutover.

Why use us instead of the new host's migration team?

A free move gets you onto their platform. You also need to know whether the platform fits.

Your new host's migration team works for the new host. Its free migration is generally a best-effort transfer within a defined scope; independent assessment of the destination may fall outside that service.

Expecting that team to independently assess its own platform is like hiring the same lawyer to represent both sides of a divorce. We work for you and report the destination's issues and deficiencies before you approve the move.

We report what we find

You receive the test findings, their impact and any outstanding items, so you can resolve them or choose a different destination.

The destination is your choice

The migration is scoped around your application and business requirements. Hosting, migration work and any additional services are separated so you can evaluate the full cost.

Completion has agreed criteria

We agree which functions, services and data must be checked. A successful file transfer is one step; acceptance comes after the agreed checks and your approval.

Website migration · hosting transfer · server-to-server migration

Move the working stack, not just the homepage.

Standard migration preserves the application and its existing behaviour. We assess the source and target versions, reproduce the required services, transfer the data and adjust configuration where needed. A rewrite is not part of a standard move.

Website & hosting transfer

Website files, database, permissions, runtime settings and domain configuration. Test forms, login, uploads, transactions and other agreed business functions.

VPS & dedicated server migration

Map services and dependencies, prepare the replacement environment, transfer application data and verify system jobs, service startup and external connections.

Provider & control-panel moves

Assess changes between hosting platforms or panels. Identify settings that transfer automatically and those needing manual configuration.

The migration checklist is agreed before the move.

Application & dataFiles, databases, ownership, permissions, runtime versions, required extensions, partition or filesystem paths and port settings.

Mail & DNSAgree whether mailboxes, IMAP sync, DNS zones, MX records and mail authentication are included, remain in place or are handled separately.

Certificates & accessTLS certificates, service credentials, firewall rules, external API allowlists and licence transfer requirements.

Jobs & integrationsCron, queue workers, scheduled tasks, outgoing mail, payment callbacks and other application integrations in the agreed scope.

Destination findingsRecord missing capabilities, resource limits, compatibility differences and test failures. Identify what must be resolved before cutover and what remains outstanding at handover.

Changing hosts should preserve your existing website addresses.

For a hosting-only move, retain the domain, URL paths and intended redirects. Check representative pages, response codes, canonical links, robots directives and sitemap access. Keep the test copy out of search indexes.

If a domain or URL structure must change, agree the old-to-new URL mapping before cutover. Redirect implementation and search monitoring are identified explicitly in the scope; a hosting transfer is not a ranking guarantee.

Moving from your current provider

Whether the source is AWS, Microsoft Azure, Google Cloud, DigitalOcean, OVHcloud, Hetzner, another VPS provider or a shared hosting account, the review starts with the services you actually use and the access available.

For websites hosted with providers such as SiteGround, Hostinger, Bluehost, GoDaddy, DreamHost or a managed WordPress platform, we check export access, database access, mail arrangements and platform-specific dependencies. Provider names identify migration enquiries we can assess; they do not imply partnerships or universal compatibility.

Want to stop overpaying for cloud hosting? Compare the destination's recurring hosting, storage, traffic, backup and management costs with your current bill. Include transfer charges and replacement services in the decision, rather than choosing on a promotional headline alone.

Review first

Copy. Test. Sync. Switch.

The free review establishes the likely route. Engineering and cutover follow the agreed scope.

Clone

Capture the files, configuration and consistent data needed for the target. Coordinate capture load and database locking beforehand.

Test

Check agreed functions, services and representative performance. Report destination issues and resolve cutover blockers.

Final sync

Bring across changes since the first copy. Agree maintenance mode or a pause in writes where needed.

Cutover

Switch traffic after approval. Account for DNS caching and prevent conflicting writes to old and new databases.

Verify & hand over

Confirm the live checks, hand over findings and retain the agreed rollback route, including how new writes are handled.

Standard migration

From $99–$199

Depending on dependencies and target. The review establishes the scope and total price before work begins.

Outside standard migration

Hosting, licences, additional services and any work outside standard migration are identified and priced separately.

A handover you can use

Source and target details, transfer and final-sync records, agreed test results, destination issues and resolutions, outstanding items, and cutover and rollback instructions.

Questions before a standard migration

Why use an independent team instead of the new host's free migration?

The new host's team works for that host. A free, best-effort transfer may not include independent destination assessment. We work for you: agreed checks produce documented findings and unresolved issues, including deficiencies on the new host, before you approve cutover.

Does my application have to be rewritten?

No. Standard migration preserves the application. Minor configuration changes may be needed for filesystem paths, partitions, ports or service connections. If the target cannot support the existing environment, we identify that before proceeding and discuss a suitable destination or separately scoped work.

Is the move zero downtime?

We agree the cutover method and likely interruption from the actual workload. Frequently updated databases may require a write pause for the final sync. DNS caching and traffic reaching both servers must be accounted for; a file copy alone cannot guarantee zero downtime.

Are email, DNS and SSL included?

The proposal states which are included, which stay in place and which need separate work. Mailbox transfer, DNS zone changes, certificate reissue, cron jobs and external allowlists are checked explicitly so there are no assumed inclusions.

Can you move us away from AWS, Azure or Google Cloud?

Yes. We assess the application, data and any provider-specific services for the destination you choose. The cost comparison includes hosting, storage, traffic, backups, management and migration charges.

Can we roll back after cutover?

Yes, within the agreed rollback arrangement. The plan defines the triggers, source-server availability and how data written after cutover is brought back consistently before traffic returns.

How much does a standard migration cost?

Starting prices are $99–$199 depending on dependencies and target. The scope and total price are agreed before work begins.

Start with what you already have

Choose your next host with the facts in front of you.

Send us your current provider, application and runtime details, approximate data size and proposed destination. We will explain the migration scope, the checks and the likely cutover window.