About One in Nine Profiles Were Duplicates. Who Owns Guest History?

About one in nine profiles in the North American hotel databases studied for Revinate’s 2026 benchmark had been flagged as duplicates. A new property management system (PMS) replacing an old one can break guest history even when it runs, reservations reconcile and the budget holds.

Weeks later, a guest who has returned every few years for three decades hears the desk ask whether this is a first visit. No report connects that outcome to the successful launch.

The gap between launch success and guest recognition

Project teams manage the change against schedule, cost and uninterrupted operations. Leaders can declare success on all three even though recognizing returning guests was not on the list.

Hotels scope guest history by deciding which profiles transfer, how many years of stays move and what goes to an archive. One PMS migration guide published on Hospitality Net offers a benchmark: retain profiles with a stay in the past three years. It calls for front-office approval of rules preserving “the history needed to recognize returning guests.”

If teams apply the three-year window without review or exceptions, a guest who returns every four years for an anniversary falls outside the cutoff. The date then becomes an unexamined guest list. The older record does not transfer, and no screen alert tells the agent that history is missing.

Recognition begins at the curb, but the hotel experience comes together at the desk, where a doorman may know the guest while the agent sees only the new system. A preferred-room note has disappeared, and the agent asks for information the hotel has kept for years, leaving the guest to judge what three decades of loyalty were worth.

The booking-channel leak

The second break requires no upgrade. A long-standing guest may book through an agency the hotel has not used before or through an online travel site. The booking arrives with a masked email or incomplete details instead of the guest’s identity; matching tools catch some records, but each miss can create a new profile.

Later stays add to one record rather than the other, leaving the profiles increasingly separate. Within a hotel group, the same guest can arrive at a sister property as a stranger. The operator still pays the commission on that stay. The hotel has bought the booking, but not the recognition that can support another stay.

The loss rarely appears as a reported loss. Repeat-guest numbers can soften, and operators may attribute the decline to the market. A guest who was never recognized does not count as a lost guest; the arrival appears as a new booking instead. By the time the record problem surfaces, that guest may already have settled into another hotel.

Both breaks share an accountability gap. Hotels treat guest history as valuable, but no role owns it as it crosses systems and booking channels. The technology project has an owner until completion, and the channel has someone watching rate; keeping the guest record whole often belongs to neither.

What should owners do before the next upgrade?

Start by naming one person to own guest history through every system and channel change, much as another owner already controls rate. That person should test records before cutover and after launch, not merely confirm that reservations and budgets balance.

Before migration, a concierge or long-serving colleague who knows returning guests can select a test group and check it in the new system against old records. Repeat the test after launch. The group should include guests whose last visit falls outside the migration window and guests who arrive through different booking channels.

For a new channel, have someone familiar with known guests review its first reservations and confirm that they match the right profiles. The practical test is whether the desk would still recognize these people from the information on screen.

Ownership should receive the same attention as rate strategy or a renovation budget. Before approving the next upgrade, an owner should put two questions to the general manager:

• After our last system change, how many years of guest history could the desk still see?
• Who is responsible for it now?

Without those answers, another system can meet its schedule, budget and operational targets while quietly converting loyal guests into first-time arrivals. The meaningful launch test is not whether the PMS stays online, but whether the desk still knows the guests the hotel has served for decades.