Website migration

Move your website to a new platform with a planned content and URL migration

Taking an existing site to a different platform — its addresses, its content, its forms and everything quietly attached to it.

Discuss your migration

Example small business website built by ARDENUX — a clean, mobile-friendly homepage

Website packages from$2,500 USD

Simple websitesfrom 3 business days

A migration is a move rather than a redesign. The site keeps doing what it does; what changes is where it lives and what it is built on.

Most of the difficulty is not in the pages. It is in the things attached to them — the addresses people already use, the forms that send somewhere, the tracking that has been running for years.

Reasons a move is worth the disruption

A migration costs time and carries risk, so it needs a reason beyond the platform feeling dated.

Nobody can edit the site
Every change goes through whoever built it, so most changes never happen.
The platform costs more than it returns
Licences, plugins and hosting that grew without anyone reviewing them.
It cannot do what you now need
A structure, a language or a function the current system has no route to.
Nobody supports it any more
The product, the theme or the person who maintained it is gone.

What the inventory has to cover

Not only the pages. The list below is where migrations usually lose something.

Every public address, including old ones that still receive visits.
Documents and downloads, which often live outside the page list.
Every form, and the address each one currently sends to.
Booking widgets, maps, chat boxes and anything else embedded from elsewhere.
Analytics and tracking, and who reads the reports.
Where the domain, the DNS and the email are administered, and who has access.

Deciding what happens to each address

Every address on the old site ends up in one of four columns, agreed before anything is built.

Stays the same

The page exists on the new site at the address it already had. The simplest and the preferred outcome.

Moves and redirects

The content survives at a different address, and the old one points at it permanently.

Merges into another page

Several thin pages become one useful one, and all of them redirect to it.

Is retired deliberately

An expired offer or an old event. Retired on purpose, with a decision recorded, rather than by accident.

How the switch itself is run

The switch is a planned event with a rehearsal, not a moment of hoping.

The new site runs somewhere private first
Complete, with the real content, reachable by you and closed to search engines.
You walk through it against the inventory
Page by page and form by form, so anything missing is found before the switch and not after it.
The switch is scheduled for a quiet period
Chosen from your own traffic and your own enquiries, not from a generic recommendation.
The domain is pointed at the new site
A short interruption around this point is normal, and it is planned for rather than promised away.
The redirect list is tested live
Every old address is requested against the running site and has to land where the map says.

The first weeks after the move

A migration is not finished on switch day. A few things are only visible afterwards.

Addresses nobody knew about
The server log shows what is being requested and failing, including pages the inventory missed.
Enquiries actually arriving
Confirmed by someone receiving one, not by the form appearing to submit.
Search engines recrawling
The new addresses are found over time. Movement in the meantime is expected rather than alarming.
The old site kept for a while
Not switched off the same day, so anything overlooked can still be recovered from it.

What does not come across

Some things belong to the old platform rather than to your site, and they end at the boundary. Plugin behaviour, theme options, page-builder layouts and anything a proprietary editor produced have no equivalent elsewhere and are rebuilt rather than moved.

A migration also cannot be promised as lossless. Where a system stored something in a form only it can read, the honest answer is to say so during the inventory, decide together whether it is worth reproducing, and record that decision — rather than discover the gap after the domain has already been switched.

Website demos

See how a finished business website can feel

Short previews of real website sections, mobile contact flows, performance-focused layouts, and ready-to-publish page structure.

Website preview