HospisHospis
Back

PMS migration stalled mid-rollout

The old system is done, the new one scares everyone, and the season starts in eight weeks

Typical for: properties running a PMS from the 2000s · operations whose vendor is ending support or maintenance · houses that inherited a system after a takeover

Documented by Hospis

Updated: 13 October 2026

How you recognize it

  • The team knows the old system so well that it works around the faults instead of reporting them
  • The vendor has announced the end of support, updates or interfaces
  • The migration has twice been decided for “next off-season”
  • Nobody knows which data has to move: guests, bookings, rates, contracts
  • The choice of the new system rests on demos rather than requirements
  • The migration is supposed to happen “on the side”, with nobody given time for it

Matching Hospi

Josef Walch

Josef Walch

Digitalisation · AI in operations · Systems · Lech am Arlberg
Works with protel · Mews · Mews POS · Smart Host
AdviseImplement

Introduced Mews and Mews POS at Rote Wand and knows requirements lists, data migration and training from hands-on delivery.

Mapped to root cause
Requirements listData preparationTiming & planTeam & training
View profilePersonally vetted · independent match

Software that solved this problem

Tools appear here next to the problems they solved, marked as partners, with honest limits and the person who runs the rollout. No ranking.

B
PMSPartnerExample

Beispiel PMS

Implementation Hospi: Senior implementation consultant

The core system that finally puts arrivals, housekeeping and billing on one beat.

View partner profile

Which path fits your situation?

01

Diagnosis

390 € fixed price

A vetted Hospi analyses your situation in a structured way, in conversation and with a written result. Every statement clearly labelled: FACT, BENCHMARK, HYPOTHESIS or CONCLUSION. You get a concrete path, not a sales meeting.

  • A legitimate outcome is also: no engagement needed.
  • If an engagement follows, the diagnosis fee is fully credited.
02

Urgent support

Acute situation? Your case is reviewed with priority, with a response within 48 hours.

Cause fields and how to tell them apart

A PMS migration does not fail because of the software. It fails because of missing preparation, the wrong timing, and a team that was never brought along.

These fields are complete, and many properties get there on their own. That is what this page is for. The cost simply does not appear on an invoice: internal hours, a few attempts, and a season that keeps running in the meantime.

01

There is no requirements list

How you spot it

The new system is picked on the basis of a demo, a price or a recommendation. What the property actually needs (half board, groups, multiple languages, interfaces) is written down nowhere. The gaps only surface after go-live.

The way out

Before any demo, write a list: what the system must do, what would be nice, what does not matter. Derived from your own operation, together with the team. Every demo is checked against the list, not against a gut feeling.

02

The data is not prepared

How you spot it

Guest records with duplicates, rates full of exceptions, bookings for the next twelve months, tour operator contracts: all of it sits inside the old system, in no shape to be moved. What travels and what stays was never decided.

The way out

Clean the data before the switch: merge duplicates, simplify rates, drop legacy baggage. Decide what gets migrated and what gets archived. A clean base makes the move half as hard.

03

The timing is wrong

How you spot it

The migration is scheduled when pressure peaks, which means shortly before or during the season. There is no window for parallel operation, training or fixing mistakes.

The way out

Migrate in the quietest phase, on a fixed schedule: data move, parallel operation, training, cut-over date. Agree a fallback option. If the window is too short, postpone it. Do not compress it.

04

The team is a spectator

How you spot it

Management picks the new system and shows it to the team on a single training day. Reception, who uses it every day, was never asked. Resistance is the logical result.

The way out

Involve the users early: requirements, demos, test phase. One person from the team as the internal point of contact who knows the new system before everyone else. The migration succeeds when the team wants it.

Frequently asked

Cloud or on-premise?
The trend is towards the cloud: less maintenance, access from anywhere, updates included. It is not yet everywhere, though: in the ÖHV technology survey 2025 among 249 member properties, 28% worked cloud-based, 42% server-based and 25% hybrid. What decides it is the requirements list, not the technology.
How long does a migration take?
From decision to stable operation: months, not weeks. Anyone attempting it in four weeks loses data or their nerves, usually both.
Can we do this without outside help?
The preparation, yes. For the data move and the interface checks it pays to buy experience the property only needs once every ten years.

Describe your situation

The problem context is automatically included, you do not need to repeat anything.

Problem
PMS migration stalled mid-rollout

We use your details only to answer your request. Details are in our privacy policy.

Related situations

PMS, POS and CRM don’t speak to each other

Guest data lives in silos, so personalisation is impossible.

View solution

Long check-in queues during peak arrivals

First impression suffers, and review scores follow.

View solution

Direct-booking share stuck below 25%

The website converts, but guests keep returning through OTAs.

View solution
See all problems