PMS Migration: How To Get Connectivity Right

Shiji's Director of Software Development outlines a step-by-step framework for PMS migration connectivity, covering integration prioritization, UAT setup, and a go-live checklist using a 100-room hotel as a worked example.

PMS Migration: How To Get Connectivity Right

Photo by Shiji

In this episode of our PMS Migration series, Vitaly Gamarnik, Director of Software Development at Shiji Group, shares practical advice on preparing integrations, prioritizing Day 1 requirements and testing connectivity, using a 100-room hotel as an example. 

Takeaways

Build your connectivity inventory early.

Prioritize integrations by Day 1 business impact.

Test 20–30 real hotel workflows before go-live.

Validate mappings, data flows and vendor dependencies.

Don’t recreate your old tech stack. Use migration to simplify and connect it.

1. Start with workflows, not just systems 

Most hotels know which technology providers they work with. They can easily identify their channel manager, booking engine, door lock system or payment gateway. However, knowing a system’s name is only the starting point. 

Hotels should first understand how their departments work together. Bringing together front office, reservations, revenue management, housekeeping, F&B and finance teams helps identify existing workflows, dependencies and opportunities for improvement. 

Next, hotels should build a detailed connectivity inventory covering:

  • Vendor, product and version: Different versions of the same system may require different integration methods. 

  • Connection type: Establish whether the system is cloud-based or on-premise and whether additional infrastructure is required.

  • Data flows: Identify what information is exchanged and in which direction, including room status, postings, rates and inventory. 

  • Vendor ownership: Collect technical contacts, contract and support information, and check whether a sandbox environment is available.

Imagine our 100-room hotel uses a channel manager, booking engine, POS, payment gateway, revenue management system and guest engagement platform. Before migration, the team needs to document each system’s vendor, product version, connection type and data flows, as well as identify who is responsible for managing each integration.

Start building your connectivity inventory during the sales and scoping phase, not after implementation kickoff. This will help identify integration requirements early and prevent unexpected challenges later.

Vitaly Gamarnik, Director of Software Development

2. Prioritize integrations based on business impact 

Not every integration needs to be connected on Day 1. The key is understanding which systems are essential to hotel operations and which can follow later. 

For this 100-room hotel, the channel manager, booking engine, payment gateway and revenue management system would likely be among the first priorities, alongside door locks and any mandatory fiscal interfaces. Guest messaging or parking integrations, for example, might be scheduled for a later phase, depending on operational needs. 

To make these decisions easier, divide integrations into three categories.

Day 1: Protect revenue and essential operations. 

Prioritize systems that generate revenue, support legal compliance or directly affect the guest experience: 

  • Distribution and reservations, including channel managers, CRS, GDS and booking engines. 

  • Revenue management systems. 

  • Payment gateways and mandatory fiscal interfaces.

  • Door locks, phones and call accounting.

Phase 2: Enhance guest experience and efficiency

Depending on the hotel’s operations, loyalty and CRM platforms, guest messaging, housekeeping applications, upselling tools and parking systems may be connected later. However, hotels with heavily used loyalty programs may consider them essential from Day 1. 

Retire: Identify systems you no longer need. 

A useful rule of thumb: If an integration fails on go-live morning, will the hotel lose revenue, break a legal requirement or negatively affect the guest experience? If yes, it should be a Day 1 priority.

Vitaly Gamarnik, Director of Software Development

One often-overlooked opportunity is identifying legacy solutions that the new platform can replace. 

The Shiji Platform, for example, brings together capabilities such as spa, activities and golf through Meridian Experiences, alongside meeting and event management solutions. These can provide a more integrated experience through a shared guest profile and financial account. 

Instead of automatically reconnecting every existing system, hotels should ask whether the new platform can provide a better solution. 

3. Test connectivity before go-live 

The goal is to find problems before your guests do, without unplugging your live operation every day. Testing happens in layers.

Vitaly Gamarnik, Director of Software Development

I recommend a layered approach: 

Start with a UAT environment. Set up a customer User Acceptance Testing (UAT) environment that mirrors the expected production configuration. This allows hotels to connect multiple systems and simulate real operational scenarios without repeatedly disconnecting live systems. 

Test sandbox to sandbox whenever possible. If a third-party vendor provides a sandbox, use it to validate connectivity. Where no sandbox exists, production-to-production testing may be necessary under controlled conditions. Real guest data, including personally identifiable information (PII), should never be transferred into test environments. 

Arrange a controlled production switch test. Approximately one to two weeks before go-live, certain on-premise integrations, such as door locks or call accounting, can be temporarily switched from the legacy PMS to the new one for a controlled testing window of around an hour before being switched back. 

Prepare for vendors that cannot switch systems. Some large cloud distribution partners may not allow production switching. In these cases, configuration should be validated in advance, and vendors can confirm through their system logs that messages are being received correctly. 

Finally, go-live morning should include a short checklist covering essential workflows: a test reservation, a working key card, a successful posting and a room status update. 

4. Common PMS migration challenges and how to avoid them 

Even with careful preparation, connectivity projects can encounter challenges. Here are several common issues: 

Underestimating integration scope. Missing information about system versions, connection types or infrastructure can create delays. Build the connectivity inventory early and involve vendors during scoping. 

Assuming the new setup works like the old one. Even familiar third-party systems may behave differently with a new PMS configuration. Test every production connection, regardless of how long you’ve worked with the vendor. 

Mapping and data mismatches. Differences in room types, rate codes, transaction codes and market segments can disrupt integrations. Review mappings with each vendor before cut-over. 

Vendor dependencies and timing. Third-party providers have their own schedules, certification requirements and potential costs. Contact them early, clarify responsibilities and agree on cut-over dates. 

People and change management. A new PMS means a new way of working. Involve every department from the beginning and provide training on updated workflows. Successful implementation requires both the platform and the hotel to adapt. 

New or custom integrations. First-time connections can introduce unexpected issues. Give them particular attention during UAT and test with vendor sandboxes whenever available.

5. Five tips for a successful PMS migration 

Let’s bring everything together using our example of a 100-room hotel preparing to migrate to a new PMS. Here are five practical recommendations: 

  1. Think beyond data migration. Consider the entire technology ecosystem, from the channel manager and booking engine to door locks and payment systems, and how these support daily hotel operations. 

  2. Know your integrations. Document every system’s vendor, product version, connection type and data flows. Don’t stop at simply listing the systems your hotel uses.

  3. Prioritize by business impact. Identify which integrations the 100-room hotel needs on Day 1, which can follow in Phase 2 and which legacy systems the new platform could replace. 

  4. Test real-life scenarios. List the 20–30 activities the hotel performs every day, from check-in and key card creation to restaurant postings and night audit, and validate them in UAT before go-live.

  5. Bring your people along. Involve front office, finance, revenue management and other departments from the beginning. A successful migration depends not only on technology but also on how well teams adapt to new workflows. 

Your connectivity action plan: what to do and when 

Use this timeline to turn the advice above into next steps. Each action has a suggested owner, so nothing falls between departments and vendors.

PMS Connectivity Action Plan

When 

Focus 

Key actions 

Owner 

8–12 weeks before 

Plan & scope 

Map every PMS integration, including vendor, version and data flow. Assign an owner and identify systems that could be retired. 

Project Manager + IT 

6–8 weeks before 

Confirm & prioritize 

Classify integrations as Day 1, Phase 2 or Retire. Confirm vendor requirements, responsibilities and cut-over dates. 

Project Sponsor + IT 

4–6 weeks before 

Build & test 

Set up UAT, connect available vendor sandboxes and validate room, rate, transaction and market mappings. 

IT + Key Departments 

2–4 weeks before 

Train & prepare 

Test 20–30 daily hotel workflows, train teams and update SOPs for any new processes. 

Department Heads + IT 

1–2 weeks before 

Final checks 

Test production connections where possible, confirm message receipt with vendors and resolve critical Day 1 issues. 

IT + Vendors 

Go-live + first 72h 

Launch & stabilize 

Test reservations, keys, postings and room status. Monitor integrations closely and resolve issues quickly. 

Front Office + IT 

Your first step this week: list every system your hotel connects to the PMS and note who owns each one. 

Think beyond the migration: Build the hotel you want tomorrow 

Connectivity is not simply about making two systems communicate. It is about ensuring information flows correctly across the hotel, supporting employees and delivering a seamless guest experience. 

Migrating to a new PMS is an opportunity to do more than replicate an existing technology setup. It is a chance to rethink workflows, eliminate unnecessary workarounds and embrace a more integrated platform. 

The goal is not to recreate yesterday’s technology ecosystem in a new system. It’s to build the connected hotel operation you want tomorrow. 

About Shiji Group

Shiji is a global technology company dedicated to providing innovative solutions for the hospitality industry, ensuring seamless operations for hoteliers day and night.

Built on the Shiji Platform, the only truly global hotel technology platform, Shiji’s cloud-based portfolio includes Property Management System, Point-of-Sale, guest engagement, distribution, payments, and data intelligence solutions for over 91,000 hotels worldwide, including the largest chains.

For more information, visit www.shijigroup.com.

View story source
Technology Operations & Strategy PMS Migration API Integration Hotel Tech Stack User Acceptance Testing

Vitaly Gamarnik is Director of Software Development at Shiji Group, bringing more than 25 years of experience in hospitality technology and software development. He has spent much of his career building and evolving hotel technology solutions, with deep expertise in PMS connectivity, integrations and complex technology ecosystems.

Building the future of hospitality technology, together.