Who Answers for the Guest’s History

On the day a new system goes live, the project is declared a success. The new property management system is running, reservations are reconciled, and the budget is held. A few weeks later, a guest who has returned to the hotel every few years for three decades is asked at the desk whether this is their first visit. No report connects the two events.

The system upgrade did what it was asked to do. Recognizing returning guests was not on the list.

A system replacement is planned around schedule, cost, and keeping the operation running through the switchover. Those are the measures a project is held to, and a project can meet each of them while the hotel loses its ability to recognize some of the guests it depends on. The launch looks like the finish line. For the guest relationship, it is where the trouble starts.

Early in a migration, someone decides how much history moves into the new system. It is treated as a question of scale — which profiles to transfer, how many years’ worth of stays, what goes to an archive instead. One PMS migration guide published on Hospitality Net offers keeping profiles with a stay in the past three years as a practical benchmark. The same guide also calls for the front office to approve the profile rules and for keeping the history needed to recognize returning guests. When that step gets skipped, and the window is applied without exceptions, a guest who returns every four years for an anniversary falls outside it. The cutoff date is a guest list. Without that review, no one treats it as one.

The older record doesn’t transfer. It contains a lot of history. Recognition begins at the door, but it comes together at the desk, and if the desk sees only the new system, that history never reaches the guest.

The agent studies the screen upon the guest’s arrival — nothing on the screen indicates to the agent that history is missing. For the guest, the change is not small. It is profound. The note that used to mention a preferred room no longer appears. The agent asks for details the hotel has kept for years. Asking them breaks no standard. In that moment, however, the guest learns the hotel no longer knows them and draws their own conclusion about what thirty years of returning were worth.

A second break happens without any upgrade, one booking at a time. A long-standing guest books through an agency the hotel has not dealt with before, or through an online travel site. The booking comes through with the channel’s masked email or incomplete details in place of the guest’s. Matching tools catch some of these. The ones they miss can become new profiles, and a guest the hotel has known for years arrives as a new guest. Revinate’s 2026 benchmark reported that about one in nine profiles in the North American hotel databases it studied had been identified as duplicates. Without someone reviewing what the tools don’t pick up, each stay adds to one profile and not the other, and the two grow further apart. In a hotel group, the same guest can arrive at a sister property as a stranger.

The hotel ends up paying a commission on that stay and still receives a guest it does not recognize.

The damage is not recorded as a loss. Repeat-guest numbers soften, and it is easy to put that down to the market. A guest who was never recognized does not get counted as a lost guest. That guest shows up as a new arrival who did not return. By the time anyone unearths it, the guest might already have settled into another hotel.

Both breaks come from the same place. Hotels treat guest history as valuable, yet it is often unclear who is responsible for keeping it accurate and complete. A new system has someone overseeing it until the project is deemed complete. A booking channel has someone monitoring the rate. But keeping a guest’s record together, as it passes from one system and one channel to the next, can end up being no one’s job in particular. Guests keep arriving. A doorman who has welcomed a guest for years recognizes them at the curb, while the agent at the desk greets them as a first-time guest — because the profile on the screen shows no history. What the doorman knows never reached the desk. That is where service continuity breaks, before the guest says a word.

How much guest history transfers to a new system is not only a technical decision. It deserves the same attention from ownership as the rate strategy or a renovation budget.

Before the upgrade, someone who has known the hotel’s returning guests for years, often a concierge or long-serving colleague, can help pick a set of them to check in the test system against the old records, and again after launch. That set should include repeat guests whose last visit falls outside the migration window, and guests who book through different channels. Then ask whether the desk would still recognize them. When a new booking channel opens, someone who knows the guests can look at its first reservations and see whether they match the right profiles. One person should own guest history through every change, the same way someone already owns the rate.

An owner can start with two questions to the general manager: after our last system change, how many years of guest history could the desk still see? And who is responsible for it now?

Without those questions, the next system upgrade will be reported as a success, and the hotel will learn, one returning guest at a time, how many it forgot.