Service · Websites and web applications

CMS migration

A CMS migration is a lot like moving house. The effort is not in the new place but in everything that has piled up in the old one: pages nobody remembers yet still get visits, PDFs linked from other websites, forms writing to forgotten mailboxes, integrations someone set up and never documented. When the current version no longer gets security updates, as with an old TYPO3 release or Joomla 3, moving is not optional. Imagine a hotel in the Zillertal with a site in German, English, Dutch and Italian running on a bespoke system nobody understands any more. Every lost address means less visibility and direct bookings drifting away to the booking portals.

Inventory
every URL, every file, every form
Redirects
301 for every address with visits or links
Languages
each language pair checked separately
Switchover
in a set window with a fallback plan

Everything this covers

A migration has succeeded when visitors notice nothing except a faster site. These work steps make sure of that.

Settle the details with an engineer

Complete inventory

A crawl of the existing site, cross-checked with Search Console and analytics, listing every page, file, form, redirect and external integration together with its traffic.

Decisions on content

Together we decide for each section: keep, merge, revise or delete. Deleted content that has visits or inbound links gets a sensible redirect.

Automated transfer

Text, images, metadata and language links are moved by script rather than copied by hand. That preserves relationships, and the import can be repeated as often as needed before launch.

Redirect map

Every old URL is mapped to a new one and set up as a 301 redirect. We test the map automatically against the list from the inventory.

Multiple languages

Language versions with correct hreflang tags, a consistent URL structure and a check that every page points to its proper counterpart in the other languages.

Reconnect integrations

Booking engine, newsletter, forms, analytics with consent and all interfaces are set up in the new system and verified with real test transactions.

Our working method

The old site stays online unchanged until the switch. The switch itself takes minutes; preparing for it takes a few weeks.

01

Inventory and plan

Crawl, traffic analysis and a list of all integrations. From these come the content decisions, target structure and a timetable that works around your peak season.

02

Set up the new system

The target CMS is configured, the existing design carried over or a new one implemented, import scripts written and first trial imports run.

03

Check and approve

Old and new pages compared, all redirects and language links tested, and sign-off by your team on a staging environment.

04

Switch and monitor

Final import, domain switched in a quiet window, error pages and Search Console watched over the following weeks, with the old environment kept for a while as a fallback.

Every language multiplies the risk of a migration. A site in four languages does not just have four times the pages; it has four times the URLs, the hreflang links and the chances of one version being tied to the wrong one. A single hreflang mistake can lead Google to show a guest from Rotterdam the Italian page. On multilingual sites we therefore check each language pair individually, before and after the switch.

Frequently asked questions

Yes. The new site is built and approved on a staging environment while the old one keeps running unchanged. The switch itself takes a few minutes and happens in a low-traffic window. For a hotel we schedule it outside the main booking period.

They are carried over if the old system allows an export. For security reasons passwords cannot always be transferred; in that case users get a link to set a new one when they first log in.

Minor fluctuations over a few days are normal. A lasting drop is usually caused by missing redirects or cut content, which is exactly what the redirect map prevents. We measure visibility before and after the switch to catch problems early.

That depends on who maintains the site, how many languages and integrations there are and what skills you have in-house. Common targets are WordPress, a current TYPO3 release or a headless CMS. We make a recommendation after the inventory.

Effort depends on page count, languages and how easily the old system can be read out automatically. After the inventory you receive a phased quote, and additional work is billed at €110 per hour plus VAT.

Let us plan your CMS migration

Tell us the current system, the rough number of pages, the languages and why you want to switch. We will reply with an approach and the risks we would keep an eye on.

Availability
Monday to Friday, 8:00-17:00 Austrian time (CET/CEST), reply within one working day
Meetings
By video on Microsoft Teams or Google Meet

We only use cookies that are technically required: to run the website and to remember the location you picked. There are no advertising or tracking cookies. Details are in the privacy notice.