Originally Posted by
Expatriate
(Local) Self-hosted could be the reason for problems with existing and new reservations at specific properties.
After some system program code update, wouldn't it make sense to repopulate the reservations (database vs program code) ?
Rather new to Hyatt, but in general when something (eg. reservation) disappears or doesn't appear to begin with, initial thought is the "system" doesn't know and so the property might not have your new reservation and existing reservation might not receive credit for nights/points.
I think the general practice these days is you plan the migration for $X date. All reservations on or after $X are populated in the new system.
On $X, you flip all the interfaces across to the new PMS. You let the existing in house reservations run in the former system and as they check out you gradually burn down the pile until everybody is being handled in the new system. Average length of stay at a typical hotel is 1.9 nights.
Yes that requires some extra work to manually post financial transactions in the old system - and you run into some quirkiness with things like the App - but you eliminate the data migration risk. You also can easily rollback should you run into issues.