Service · Websites and web apps

CMS migration

Nobody changes content system for pleasure. You arrive there because the vendor stopped issuing fixes, because the smallest edit needs a developer, or because the original supplier vanished taking the explanations with them. Take an independent hotel group inheriting a bespoke system nobody understands any more. The risk in a migration is not technical, it is commercial: a transfer carried out without an address map wipes out years of hard-won visibility in a single evening.

Address map
one redirect for every page
Transfer
content, images and documents
Monitoring
for weeks after the switch
Rehearsal
the migration played through first

Where this service reaches

A migration is judged on what the visitor never notices: links that still work, pages found where they were, forms that still arrive.

Put your scope to an engineer

Inventory of what exists

A full census of pages, images, downloadable documents, forms and live links. Plenty of sites hold pages nobody inside the company remembers, which nonetheless receive visits.

Choosing the new foundation

We compare the options against what your teams genuinely publish, the links required and the upkeep cost over three years, rather than against current popularity.

Carrying content over

Automated transfer where the structure allows, manual handling for high-value pages. Outdated content is dropped deliberately rather than by accident.

Redirect map

Every old address gets a match as a permanent redirect, including PDF files and images linked from other sites. This is the centrepiece of the project and the part most often rushed.

Structured data and measurement

Tags, sitemap, structured data, analytics accounts and conversion goals moved across before the switch, so comparing before and after stays possible.

Rehearsing the switch

We play the migration through on a test environment, including the final round of edits, so that the day itself holds no surprises.

Monitoring afterwards

For several weeks we watch errors, dropped pages, positions and forms. Migration trouble rarely surfaces on the first day.

The way an engagement runs

Duration follows the volume of content and how tidy the old system is. A site with consistent addresses transfers far quicker than one reworked four times by four different suppliers.

01

Opening audit

A record of pages, traffic per page, inbound links and the technical quirks of the system in place.

02

Preparation

New foundation, templates, the address matching table and the scripts that carry content across.

03

Rehearsal and acceptance

A trial migration, page-by-page checks on the most visited content, trials of forms and links.

04

Switch and follow-up

Moving to production at a quiet hour, redirects switched on, search engines notified, then close monitoring.

Addresses are the invisible capital of a website. Every link pointing at you from a directory, a press article, a partner or an old email carries accumulated visibility. A migration that changes the address structure without a matching table turns all of it into error pages, and the drop in traffic only becomes visible three weeks later, by which time rebuilding the old structure is far harder.

Questions and answers

A wobble of a few days is normal while engines take in the new addresses. A lasting drop nearly always points to missing redirects, truncated content or a slower site. That is why we record positions before the switch and watch them afterwards: with no starting point, nobody can settle the argument.

It depends on the source system. Widely used platforms expose their data and transfer largely by script. Bespoke systems often need a purpose-built extraction, sometimes straight from the database. We assess that share at the start, because it weighs heavily on the budget.

Tempting, and often regrettable. If the site changes its look, its structure and its foundation at once, you will not know what to blame for a drop in performance. Migrating first, measuring, then evolving the look gives safer results, except where the old site is fit only for the bin anyway.

Minutes, because the new site is ready and approved before the switch. We schedule the operation for a quiet hour and keep the old environment intact for several weeks, so we can step back if something serious appears.

We keep it readable through the monitoring period, then you cancel it once the migration is confirmed. Before that we take a complete archive of files and database for you to keep: it is the last trace of a system nobody will be able to start up again.

Let us plan your CMS migration

Give us the current system, the volume of pages and what is pushing you to change. We reply with an approach and the risks worth watching.

When we are around
Weekdays, 8:00 to 18:00 CET; answers land inside one working day
Talking it through
A call on Teams or Google Meet, whenever writing is not enough

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.