> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/integrations/property-management-systems/what-syncs-from-your-pms.md).

# What syncs from your PMS

What Guestway reads from each PMS, what it writes back, and how often it checks for changes.

{% hint style="info" %}
**Requirements**

* A connected PMS. See [Property management systems](https://docs.guestway.io/integrations/property-management-systems.md).
  {% endhint %}

In the tables:

* ✓ Guestway reads it from the PMS.
* ⇄ Guestway reads it, and writes changes made in Guestway back to the PMS.
* – Not synced.

## Properties and listings

| Data                     | Apaleo | Guesty | Hostaway | Mews | Smoobu |
| ------------------------ | :----: | :----: | :------: | :--: | :----: |
| Properties (complexes)   |    ✓   |    ✓   |     –    |   ✓  |    –   |
| Unit types (multi-units) |    ✓   |    ✓   |     –    |   ✓  |    –   |
| Listings                 |    ✓   |    ✓   |     ✓    |   ✓  |    ✓   |
| Cleaning status          |    ⇄   |    ⇄   |     ⇄    |   ⇄  |    –   |
| Listing photos           |    –   |    ✓   |     ✓    |   –  |    –   |
| Wi-Fi details            |    –   |    ✓   |     –    |   –  |    –   |
| Calendar blocks          |    ✓   |    ✓   |     ✓    |   ✓  |    ✓   |
| Custom fields            |    –   |    ⇄   |     ⇄    |   –  |    ✓   |

* With Apaleo, the cleaning status is the condition of the unit: **Clean**, **Dirty** or **Clean to be inspected**. A change in Guestway updates the unit in Apaleo, and a change in Apaleo reaches Guestway.

What a PMS does not send, for example the Wi-Fi details, you manage in Guestway on the listing. See [General](https://docs.guestway.io/properties/general.md).

## Reservations and guests

| Data                                                           | Apaleo | Guesty |    Hostaway   |      Mews     |     Smoobu    |
| -------------------------------------------------------------- | :----: | :----: | :-----------: | :-----------: | :-----------: |
| Reservations                                                   |    ✓   |    ✓   |       ✓       |       ✓       |       ✓       |
| Reservation notes                                              |    ⇄   |    ⇄   |       ⇄       |       ⇄       |       ⇄       |
| Guests                                                         |    ⇄   |    ✓   |       ✓       |       ⇄       |       ✓       |
| Company of the reservation                                     |    ✓   |    –   |       –       |       –       |       –       |
| Owner reservations                                             |    –   |    ✓   |       ✓       |       –       |       –       |
| Door codes                                                     |    –   |    ✓   |       –       |       –       |       –       |
| Check-in and check-out                                         |    ⇄   |    ⇄   | Guestway only |       ⇄       | Guestway only |
| Early check-in and late check-out times                        |    ⇄   |    ⇄   |       ⇄       | Guestway only | Guestway only |
| Unit assigned to a reservation                                 |    ⇄   |    ⇄   |       –       |       –       |       –       |
| Inquiries and booking requests (pre-approve, approve, decline) |    –   |    ⇄   |       –       |       –       |       –       |

* *Guestway only*: Guestway keeps the change, but does not send it to the PMS.
* With Mews, Guestway writes only the general notes. The channel manager notes and the special requests come from Mews and cannot be changed in Guestway.
* With Smoobu, Guestway writes the notes to the booking notes and the assistant notes in Smoobu. Guestway also fills custom placeholders on each Smoobu booking, for example `gw_codes` with the door codes, so that you can use them in Smoobu.
* With Apaleo and Mews, Guestway can also add guests to a reservation.
* With Apaleo, the company that a reservation is booked for shows on the **Guests** tab of the reservation. See [Reservation details panel](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/reservation-details-panel.md).
* With Guesty, Guestway assigns a unit only to a reservation that is booked on a multi-unit listing and is confirmed or checked in. The unit must belong to that multi-unit listing. Guestway does not move a reservation that already has a unit. See [Room assignment](https://docs.guestway.io/reservations-and-operations/room-assignment.md).

## Messages and reviews

| Data           | Apaleo | Guesty | Hostaway | Mews | Smoobu |
| -------------- | :----: | :----: | :------: | :--: | :----: |
| Guest messages |    –   |    ⇄   |     ⇄    |   –  |    ⇄   |
| Saved replies  |    –   |    ✓   |     ✓    |   –  |    –   |
| Reviews        |    –   |    ⇄   |     ✓    |   –  |    –   |

* Apaleo and Mews do not send guest messages. Messages from Booking.com reach Guestway by email instead, and Expedia connects directly. See [How to connect Booking.com](https://docs.guestway.io/integrations/online-travel-agencies-ota/booking.com.md) and [How to connect Expedia](https://docs.guestway.io/integrations/online-travel-agencies-ota/expedia.md).
* With Smoobu, a reply from Guestway goes out through Smoobu, by email or in the chat of the booking channel. Messages sent from Smoobu also show in the Guestway inbox, as messages of your team.
* With Guesty, you can reply to reviews from Guestway. With Hostaway, you can read the reviews, but not reply from Guestway.

## Bills and services

| Data                                           | Apaleo | Guesty | Hostaway | Mews | Smoobu |
| ---------------------------------------------- | :----: | :----: | :------: | :--: | :----: |
| Open balance of the guest bill                 |    ✓   |    ✓   |     ✓    |   ✓  |    –   |
| Charges added to the guest bill                |    ⇄   |    ⇄   |     –    |   ⇄  |    –   |
| Payments recorded on the guest bill            |    ⇄   |    ⇄   |     –    |   ⇄  |    –   |
| Upsells booked as a service on the reservation |    ⇄   |    –   |     –    |   ⇄  |    –   |

* With Apaleo, the services booked on a reservation in Apaleo also come into Guestway with the reservation, each with its date and amount. An upsell that a guest buys in Guestway is booked as a service on the Apaleo reservation, so its charge is on the folio.

For the details, see [Apaleo billing](https://docs.guestway.io/integrations/property-management-systems/apaleo/apaleo-billing.md) and [Mews billing](https://docs.guestway.io/integrations/property-management-systems/mews/mews-billing.md).

## Sync frequency

The PMS tells Guestway about most changes as they happen, so they arrive within moments. Guestway sets this up in the PMS when you connect. Guestway also checks the PMS regularly, to catch anything that was missed:

| PMS      | Reservations     | Guest messages                                             | Listings         |
| -------- | ---------------- | ---------------------------------------------------------- | ---------------- |
| Apaleo   | Every 15 minutes | –                                                          | Every hour       |
| Guesty   | Every 10 minutes | Every 15 minutes                                           | Every 24 hours   |
| Hostaway | Every 30 minutes | Every 30 seconds                                           | Every 5 minutes  |
| Mews     | Every 15 minutes | –                                                          | Every hour       |
| Smoobu   | Every 2 hours    | Every 5 to 90 minutes, more often for recent conversations | Every 30 minutes |

When you connect Apaleo, Guesty or Hostaway, Guestway imports the reservations of up to 5 years back.

## Related

* [Integrations](https://docs.guestway.io/integrations/integrations.md)
* [How to choose which listings and devices sync](https://docs.guestway.io/integrations/integrations/how-to-choose-which-listings-and-devices-sync.md)
* [How to connect Apaleo](https://docs.guestway.io/integrations/property-management-systems/apaleo.md), [Guesty](https://docs.guestway.io/integrations/property-management-systems/guesty.md), [Hostaway](https://docs.guestway.io/integrations/property-management-systems/hostaway.md), [Mews](https://docs.guestway.io/integrations/property-management-systems/mews.md), [Smoobu](https://docs.guestway.io/integrations/property-management-systems/smoobu.md)
* [Room assignment](https://docs.guestway.io/reservations-and-operations/room-assignment.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/integrations/property-management-systems/what-syncs-from-your-pms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
