Switching Hotel PMS: A Migration Checklist for Malaysian Hotels

Changing your hotel property management system is not simply an IT project. It affects every arrival, room assignment, payment, OTA booking and report your team handles.

A safe migration gives the hotel one controlled path from the old system to the new one. The goal is not to copy every old setting. It is to preserve the information the hotel needs, rebuild workflows properly and make sure staff can operate before the first live shift.

When should a hotel consider changing its PMS?

A migration may be worth planning when the current system regularly creates problems such as:

• Staff entering the same booking or payment more than once
• OTA reservations arriving late or requiring manual entry
• Reports that do not agree across departments
• Housekeeping relying on calls, paper or chat messages for room status
• Separate systems for the front desk, restaurant, payments and e-invoicing
• Support that is unavailable during the hotel's operating hours
• A system that cannot support another property, outlet or room type

One inconvenient feature is not always a reason to move. Begin by documenting the operational problems, their frequency and their effect on guests or staff. That gives the new provider a clear standard to meet.

1. Appoint one migration owner

Choose one person inside the hotel who can make decisions and coordinate the departments involved. This may be the general manager, rooms division manager or an experienced front-office lead.

The migration owner should maintain:

• The master task list
• The agreed go-live date
• A list of decisions and responsible people
• Open questions for the old and new providers
• The test results and final approval

Without a clear owner, configuration questions often sit unanswered until training or go-live.

2. Map the hotel's current workflow

Before configuring the new hotel PMS, follow a booking through the whole property. Record what happens when the booking is created, modified, checked in, charged and checked out.

Include every booking source and department:

• Walk-ins, telephone bookings and corporate accounts
• Agoda, Booking.com, Traveloka and other OTAs
• Direct website reservations
• Housekeeping and maintenance
• Restaurant, minibar and room-service charges
• Deposits, refunds and different payment methods
• Tourism Tax, SST and LHDN e-Invoice steps
• Night audit and management reports

This exercise exposes unofficial workarounds that may not appear in a normal software demonstration.

3. Decide which data must move

Do not assume every item in the old PMS can or should be imported. Agree on the migration scope in writing.

At minimum, review:

• Future and in-house reservations
• Guest profiles and contact details
• Company and travel-agent profiles
• Room types, rooms and occupancy rules
• Rate plans, packages and restrictions
• Deposits, balances and open folios
• Tax and service-charge settings
• Historical reservations and financial reports
• User accounts and permissions

Keep an export of historical information even when it will not appear inside the new PMS. Confirm the format, where it will be stored and who can access it after the old contract ends.

4. Clean the data before importing it

Migration is a useful time to remove obvious duplicates and outdated settings. Clean guest profiles, inactive rate plans, old company accounts and room types that are no longer sold.

Do not make broad deletions without retaining the original export. The safest sequence is:

1. Export and preserve the source data.
2. Create a working copy.
3. Clean the working copy using agreed rules.
4. Validate totals and sample records.
5. Import only after approval.

The team should be able to explain why the imported record count differs from the original.

5. Rebuild integrations and room mapping

A working PMS does not mean the full hotel system is ready. Each connection needs its own setup and test.

Check the:

• Channel manager and every connected OTA
• Website booking engine
• Payment gateway, terminal and settlement process
• Restaurant POS and room-charge posting
• Accounting export or integration
• Door locks and key-card process
• MyKad or passport reader
• Guest messaging and reputation tools
• LHDN e-Invoice workflow

Room and rate-plan mapping deserves special attention. A Deluxe King Room Only rate in the PMS must connect to the matching product on each OTA. Do not copy mappings blindly from a spreadsheet without testing the result.

6. Train staff by job, not by feature

Front-desk staff do not need to memorise the entire system. They need to complete the tasks that occur during their shift.

Create short role-based sessions for:

• Reservations and front office
• Housekeeping and maintenance
• Night audit and finance
• Restaurant and other outlets
• Revenue and distribution
• Managers and system administrators

Use the hotel's real room types, rates and policies during training. Each employee should practise common tasks and at least one exception, such as moving a room, splitting a folio or correcting a payment.

7. Run realistic tests before go-live

A login test is not enough. Complete an end-to-end rehearsal using test records.

Test at least:

1. A walk-in reservation and check-in
2. A new OTA booking, modification and cancellation
3. A direct booking with a deposit
4. A room move after check-in
5. A restaurant charge posted to the guest folio
6. A split payment and refund
7. A no-show and cancellation fee
8. Checkout and invoice generation
9. Night audit and business-date rollover
10. Occupancy, revenue and payment reports

Record the expected result, actual result and person who approved each test. Resolve critical errors before accepting live bookings.

8. Plan the cutover and fallback

Choose a go-live period with manageable occupancy if possible. Confirm when staff must stop changing information in the old system and when the final reservation and balance checks will happen.

On cutover day:

• Compare arrivals, departures and in-house guests in both systems
• Confirm every future reservation and deposit total
• Keep the old system available in read-only form where possible
• Place trained support contacts on one shared list
• Assign extra staff for the first busy shifts
• Record issues in one log instead of separate chat messages

Also agree on a fallback process. Staff should know how to record arrivals, payments and room status if a connection needs to be paused or corrected.

Hotel PMS migration checklist at a glance

• Migration owner appointed
• Workflow and integration map completed
• Data scope approved
• Original exports stored safely
• Imported data validated
• Rooms and rates mapped to every channel
• Payment and POS connections tested
• Staff trained using real scenarios
• End-to-end test results signed off
• Go-live and fallback plans shared
• First night audit checked by a manager
• Post-launch review scheduled

Make the move operational, not just technical

The safest PMS migration is the one your front desk can explain. Every reservation must have a clear source, every charge must reach the right folio and every employee must know what to do when the normal flow changes.

If your hotel is planning a switch, book an eZee demonstration using your own room types and workflows. The onboarding team can then scope the data, integrations, testing and training needed for your property.