Hotel CRM vs PMS: what each system knows about a guest

A hotel CRM is a system for guest relationships: contact history, preferences, consent, segments and campaign responses. A PMS is the system of record for the stay: reservation, room, folio, charges and check-in. The CRM should not replace the PMS; it should extend it, with one system owning each field.

A hotel owner buys a CRM because a vendor says it is where the guest really lives. Then marketing wants to send an offer, the front desk sees a different profile, and finance asks which bill is correct. This article separates the two systems by the facts each owns, shows how they should connect, and gives you a test for when a separate CRM is worth the cost.

What is a hotel CRM?#

A hotel CRM is a relationship system: it tracks how a hotel communicates with guests and prospects over time. It is not the system that checks a guest in, assigns a room or closes a bill.

It stores contact details, communication history, preferences, segments, consent status and campaign responses. It can group guests by source, purpose, repeat status or behavior, such as spa use or direct booking. It supports marketing actions like email, messaging, phone notes and reactivation campaigns, but only within lawful consent.

A CRM can sit alone or connect to the PMS, the booking engine, point of sale, loyalty and channel sources. Judge it by whether it changes a real decision: who to contact, what to offer, and when to stop. It should not become a shadow billing system, or a place where the front desk makes financial changes.

What does a PMS know about a guest?#

A PMS knows the operational and financial truth of a stay: who booked, which room, what was charged, when they checked in and out, and what compliance records were created.

It owns reservation, room assignment, arrival and departure, the folio, charges, payments, taxes and night audit. It records the guest identity fields needed for check-in and fiscal or security notifications, but not every marketing preference. It may hold notes, VIP flags, allergies or language preferences, but those fields can be shallow and poorly audited.

The PMS is the safest source for room nights, revenue, charges and corrections such as voids, reversals, folio splits and group billing. If a CRM changes a reservation date, room type or rate, the PMS must remain the system that protects inventory and billing. A PMS record is useful to marketing only when it is accurate, dated and linked to the same person across stays. For more on how the pieces fit together, see how the core hotel systems connect.

What does a hotel CRM add?#

A CRM adds the relationship layer around the stay: who contacted the hotel, what they asked, what they preferred, which messages worked, and which groups can be marketed to later.

It can merge contact records from the booking engine, PMS, point of sale, messaging, email, phone and loyalty, while keeping a link back to the stay. It can store preferences a PMS may not model well: pillow type, an anniversary, a dietary note, a preferred contact channel, a marketing language. It can maintain segments such as direct bookers, repeat guests, spa users, families, corporate accounts and lapsed guests, but segments must be refreshed and reviewable, or they rot.

It can log campaign responses: opened, clicked, replied, opted out, no longer interested. Those events need a source and a date, or they are noise. It can help sales and marketing plan outreach, but it must not promise an upgrade, discount or room that the PMS cannot deliver. It should show the full contact story without forcing staff to search multiple tools.

For what belongs in a guest profile at all, see what to record for repeat guests.

How should a CRM and PMS connect?#

They should connect by clear field ownership and dated events, not by copying every guest record into both systems.

One-way sync can be enough: the PMS sends stay and billing facts to the CRM, and the CRM sends marketing consent, preferences and campaign notes back to the PMS or a shared data layer. Two-way sync is useful when each field has one owner and conflicts are logged, not silently overwritten.

Reservation, room, folio, rate, taxes and check-in status should flow from the PMS to the CRM, never the reverse. Marketing consent, campaign response, communication preference and segment membership can originate in the CRM, but the PMS needs the current value for service: a receptionist should see that a guest prefers no marketing calls before picking up the phone.

The connection should include event history: created, updated, deleted, consent withdrawn, merged, split, each with the user or integration that did it. It should handle duplicate profiles with a merge rule and an audit trail, because one person can arrive from several channels. For example, a guest may book directly once, arrive through an agency the next time, and email the hotel in between; without a merge rule, that is three people in the CRM.

Which system should own consent and retention?#

One system must be the legal source for consent and retention, and the other should read or mirror that decision with a dated record.

In Türkiye, personal-data rules, including KVKK (the personal data protection law), require a clear basis for processing, notice to the guest, access, correction, deletion or destruction controls, and limits on staff access. Marketing consent should record the channel, purpose, date, source, wording or evidence, any withdrawal, and who acted on it. A reservation contact detail is not automatically consent to marketing; the lawful basis and the notice must be checked for each use.

Retention periods should be set by purpose: billing and fiscal records, security notifications, marketing consent, service preferences and complaint handling may each have different rules. The CRM should not keep marketing profiles longer than the stated purpose, and the PMS should not keep unnecessary personal data after the stay. Confirm dates, penalties, scope and your own case with an accountant or legal adviser. For the wider picture, see KVKK notices, consent, staff access and retention.

When is a separate CRM worth the cost?#

A separate CRM is worth it when the hotel has enough contactable guests and staff time to run repeatable campaigns, and when the PMS cannot manage consent, segmentation and communication history cleanly.

Start with a test: can the hotel identify a clear group, send a lawful message, track replies, and let staff see the result? If the PMS already stores notes, preferences and simple lists well enough, and marketing is rare, a separate CRM may be extra work. If direct bookings, repeat guests, corporate accounts, spa, food and beverage or event sales need campaign history, a CRM can justify its cost through better targeting.

If staff must copy data between tools, or marketing sends messages without knowing check-in status, a CRM may reduce errors. But if the hotel cannot assign an owner to keep consent and segments clean, a CRM will create more risk than value. The test is not whether the CRM has many features, but whether it creates a decision the hotel can act on. When the problem is reporting rather than relationships, the question is different: see when PMS reports are not enough.

What questions should you ask a CRM or PMS vendor?#

Ask for the field map, not the feature list: who owns each guest field, how it moves, how consent is audited and how mistakes are undone.

A vendor who cannot answer the consent and merge questions in plain words is telling you something. Write the answers into the contract discussion, not into a demo note.

What to do next#

Draw a one-page field map. List every guest field your hotel uses, name the owning system for each, note the consent source and the retention owner, then compare that map with what your CRM and PMS vendors can actually show. Every field with two owners, or none, is a future dispute between marketing, the front desk and finance.