# Guesty stays the PMS. The rest runs natively.

Canonical: https://vr-goals.com/guides/how-guesty-data-flows-into-vr-goals

Author: Steven Brown, CEO & Founder. Published August 28, 2026. Review by November 28, 2026. Reviewer Assign a named VR Goals integration reviewer.

Guesty remains the live PMS source of truth for reservations, properties, owners, guests, folios, and related PMS records. VR Goals reads the facts it needs, normalizes them into one business map, and uses them across native operations, finance, CRM, messaging, contracts, and Align.

This replaces the old “connect Guesty, QuickBooks, and operations data” explanation. VR Goals does not maintain a live QuickBooks connection. It imports QuickBooks history during onboarding, then uses native accounting.

## Keep the PMS authoritative

The PMS owns the records it was built to manage. VR Goals should not create a second reservation truth. Each imported fact keeps its source identifier, organization, time, and data-health status.

- Property and listing identifiers
- Reservation and stay dates
- Guest and owner links
- Booking status
- Charges, fees, taxes, payouts, and folio context
- Arrival, departure, and occupancy facts
- PMS messages and events supported by the live connection

## Normalize the business entities

Different apps may refer to the same property, owner, guest, reservation, job, or market in different ways. VR Goals maps those references to canonical entities. Normalization lets a fact move across teams without losing its property, owner, market, or accountable-seat context.

- Company and legal entity
- Market and property
- Owner and agreement
- Guest and reservation
- Turnover, inspection, maintenance, and job cost
- Bank account, ledger entry, owner balance, and payout
- Lead, proposal, signed property, and onboarding case
- Pillar, seat, goal, measure, signal, and action

## Run native operating workflows

PMS facts can start work inside VR Goals. A reservation can create turnover work inside the operating window. A signed property can start onboarding. A checkout can create accounting activity. A guest message can create a service exception. The source event remains linked to the native record, so a number is not copied into a task with no path back to the reservation or property.

## Feed measures into Align

Native and PMS records produce measures. Align attaches each measure to a goal, source, data-health status, market slice, and accountable seat.

- Managed and signed properties
- Revenue pacing
- On-time turnover completion
- Missed cleans and inspections
- Guest response and rating signals
- Owner statement status
- Trust exceptions and close progress

## Turn drift into routed action

When a measure moves beyond its expected range, VR Goals can create a signal with the affected property, market, owner, guest, or financial context. The signal routes to the seat closest to the result. The current apps run today. The multi-agent business team and deeper automated action layer remain in early access and should be labeled that way.

## QuickBooks history imports at onboarding. Then the ledger is native.

There is no live QuickBooks connection. The migration is import, map, reconcile, then run accounting in VR Goals.

1. Import historical QuickBooks data during onboarding.
2. Map accounts, entities, balances, and required history.
3. Reconcile the opening position.
4. Move ongoing accounting into the native VR Goals ledger.
5. Keep bookkeepers and financial review; replace the software connection, not financial control.

## What a public integration page must state.

Guesty is the current live PMS connection. Public copy should not present another PMS as live without release evidence.

- Live, early access, planned, or unsupported status
- Data read and written
- Sync or event frequency
- Required permissions
- Known limits
- Implementation responsibility
- Last factual review date

## Do not buy VR Goals to keep QuickBooks as the live ledger.

VR Goals is not the right fit if you need QuickBooks to remain the ongoing ledger with a live two-way sync, require a PMS that is not approved as live, or want a reporting copy without moving operational work into the shared model.

## Next step

Review the Guesty connection and native-app rollout against the operator’s required records, migration timing, and control needs.

- Request access: https://vr-goals.com/#access
- Guesty: https://vr-goals.com/guesty

- Guesty: https://vr-goals.com/guesty
- Implementation: https://vr-goals.com/implementation
- Security: https://vr-goals.com/security
- Pricing: https://vr-goals.com/pricing
- Finance: https://vr-goals.com/apps/finance
- Align: https://vr-goals.com/align