Skip to main content

IoT Locks – Important Notes When Migrating from Another PMS to AirHost

J
Written by Joelly See Toh

Scope

This guide explains the important considerations when migrating from another PMS to AirHost while continuing to use your existing smart lock service.

Supported Smart Lock Services (Examples)

  • Keycafe

  • RemoteLock

  • Connected Platform

  • Keyvox

  • KeyWE

  • Linkey

  • ASSA ABLOY

  • apt11

  • SwitchBot


How Smart Lock Integration Works

AirHost does not store guests' PIN codes directly. Instead, AirHost creates an access credential for each reservation within the smart lock service and manages the associated information (such as the Credential ID and PIN code).

As a result:

  • AirHost can manage only the credentials created by AirHost.

  • Credentials created by another PMS cannot be viewed, updated, or deleted from AirHost.


Important Notes When Migrating

Do Not Use the Same Smart Lock Account with Multiple PMSs Simultaneously

Using the same smart lock account with both the old PMS and AirHost simultaneously may result in duplicate authentication information and PIN codes, potentially causing problems with key retrieval and PIN code usage.

When both systems write credentials to the same smart lock account, each PMS creates its own credentials independently, which may lead to duplicate access records.

AirHost can only manage, update, or delete credentials that it created. Credentials created by the previous PMS remain active until they expire.

This may result in issues such as:

  • Multiple PIN codes being issued for the same reservation

  • Multiple credentials being created for the same lock

Keycafe

If old credentials remain active, guests may experience issues such as:

  • The key has already been checked out

  • The guest is unable to retrieve the key

RemoteLock

Old PIN codes continue occupying PIN slots, which may result in:

  • Duplicate PIN codes

  • Reaching the maximum number of available PIN codes

Other Smart Lock Providers

Old credentials or PIN codes remain valid until they expire and may continue consuming available credential or PIN capacity.


Preparation Before Migration

Before switching to AirHost, please complete the following:

  • Enable the IoT (Smart Lock) option for each property.

  • Connect your existing smart lock account to AirHost.

  • Perform a device synchronization.

  • Do not assign devices to rooms until the migration day.

For Keycafe Users

Temporarily disable Two-Factor Authentication (2FA) before connecting your Keycafe account.

After the integration is complete, you may re-enable 2FA.


Recommended Migration Procedure

① Before Migration (While Using the Previous PMS)

  • Continue issuing keys and PIN codes through the previous PMS.

  • In AirHost, only connect the smart lock account and synchronize devices.

  • Do not assign devices to rooms.

  • Do not import active reservations into AirHost.

Assigning devices to rooms before migration will cause AirHost to start issuing credentials, potentially creating conflicts with the previous PMS.

② During the Migration Period (Guests Currently Staying or Reservations with Existing PIN Codes)

We recommend allowing credentials already issued by the previous PMS to remain active until they naturally expire.

If you need to change a PIN code or access period, please make the change directly through the smart lock provider's management portal.

③ On the Migration Day

Perform the migration in the following order:

  1. Disconnect the smart lock integration from the previous PMS.

  2. Assign devices to rooms in AirHost.

  3. Begin managing new reservations through AirHost.

From this point onward, AirHost will automatically issue new access credentials.


Reissuing PIN Codes

When a PIN code is reissued in AirHost, AirHost deletes the previous credential only if it was originally created by AirHost, then generates a new PIN code.

However, AirHost cannot delete credentials created by the previous PMS.

Therefore, if you reissue a PIN code in AirHost for a reservation whose PIN was originally created by the previous PMS, both of the following may remain valid simultaneously:

  • The new PIN code issued by AirHost

  • The original PIN code issued by the previous PMS


How to Handle Reservations with Existing PIN Codes

For reservations whose PIN codes were issued by the previous PMS, do not reissue the PIN code from AirHost.

If management of the reservation must be transferred to AirHost, follow these steps:

  1. Delete the existing credential using either the smart lock provider's management portal or the previous PMS.

  2. Generate a new PIN code from AirHost.

Following this procedure prevents multiple valid PIN codes from existing for the same reservation.

Did this answer your question?