Taking Over Vacation Rentals While Guests Are Still Staying

What needs to be settled before the handover?

At the agreed handover time, the incoming team needs more than keys and an occupancy calendar. It must know which guests are already staying, which commitments remain in place, and which decisions still belong to the outgoing operator or property owner. An unresolved repair can be handed over. Who takes the next action cannot remain unclear.

For the operational handover, use a joint acceptance record with three possible outcomes: accepted, accepted with a specified limitation, or not yet accepted. This classification is an editorial working method. It does not replace the management agreement or a legal assessment of the change of operator.

Whether the property will run in your own PMS or the existing system is a separate decision. The guide to growing a portfolio without replacing the PMS covers ongoing portfolio operations. This article focuses on the point when a different team takes responsibility.

1. Define what changes at the handover time

“We take over on Monday” is not enough. Agree on the date, time, time zone, and affected units. Then specify what actually changes at that point: guest communication, incident intake, cleaning coordination, access administration, or authority to approve new expenses.

These duties may transfer at different times. The outgoing company might still handle earlier refund requests while the incoming operator provides on-call maintenance support. Each open matter needs one clear contact.

Keep three questions separate:

• Who acts? Who replies to the message, arranges the contractor, or updates the guest?
• Who can decide? What authority exists to approve expenses, discounts, and changes?
• Who holds the obligation? What do the booking, management agreement, and other arrangements establish?

An operational handover should not be treated as an implicit resolution of every payment, liability, or contractual question. Record unresolved matters as separate decisions to be made. If legal responsibility is unclear, the specific agreement needs to be reviewed.

An Airbnb account is not a transferable property key

Airbnb states that account ownership cannot be transferred to another host. Reservations cannot simply be moved to a new host or another account either. Review Airbnb’s account transfer rules before the change. Sharing login details does not resolve this restriction. Clarify the permitted process for existing bookings with the platform before closing accounts or reorganizing reservations.

2. Reconcile open work instead of merely passing on files

Create a dated overview from the system that holds the authoritative booking record. Add the information the calendar does not contain. A confirmed mid-stay cleaning, an agreed late checkout, or a scheduled contractor visit may matter more during the first week than a complete archive of old messages.

For each ongoing stay or imminent arrival, check:

• Unit, reservation reference, confirmed stay dates, and authoritative data source;
• Latest confirmed commitment communicated to the guest, including additional services;
• Unresolved requests and the next update already promised;
• Access for the guest and responsible team;
• Accepted contractor assignments with service time and contact;
• Outstanding reporting tasks or property documentation, insofar as needed for the work being taken over.

Record differences between the calendar, messages, and job list explicitly. “Not known” is a useful finding. “No open cases” is reliable only if a reconciliation has actually taken place.

A reservation extended during the handover belongs on a separate change list. Decide who records changes between the first data extract and acceptance of the handover. Keep the original snapshot identifiable. The existing guide to reservation changes and their operational consequences explains the subsequent implementation.

3. Secure guest support before changing access

A new password does not prove the team can operate. Check that the incoming team can reach the necessary accounts using its own permissions, handle the intended guest contact channel, and obtain access to the correct unit when an issue occurs. An agreed test with the new on-call contact reveals whether the phone number, forwarding, and backup contact work.

Plan the removal of previous permissions alongside this check. Where a transition period is permitted and necessary, limit its purpose, participants, and end time. Previous access should not remain available indefinitely just because someone might have a follow-up question. If that transition is not authorized, another approved fallback is needed.

A management change should not leave guests locked out. Establish which existing guest access arrangements remain valid and when a change is required. Record confirmation of the new access or an available fallback before a change interrupts the existing entry route. The article on roles and access rights explains the underlying process for granting and ending permissions.

4. Transfer guest data according to purpose and role

Before exchanging data, establish whether the incoming provider acts as a processor or determines the purposes and means of processing itself. The label “property manager” does not answer that question.

For Switzerland, the FDPIC explains that a controller outsourcing processing remains responsible for data protection and must select, instruct, and monitor the processor appropriately. Its guidance on outsourced data processing is not blanket permission to hand over an entire guest database.

As a practical measure, list the purpose, authorized recipient, and secure transfer method for each data package. Use booking references in the operational record wherever possible instead of unnecessary personal details. Separately assess which records must remain with the outgoing company and how remaining copies will be handled.

The Swiss duty to provide information generally also applies to data obtained from someone other than the individual concerned; statutory exceptions require a separate assessment. Coordinate the required privacy information with guest communication. Other countries and additional applicable requirements need their own review.

5. Example: Management changes while the guest stays

The following example is entirely fictional. It describes no customer, management engagement, or completed product test.

Starting point: Operational responsibility for unit B-12 changes on October 6 at 12:00 noon, time zone Europe/Zurich. Reservation R-218 continues until October 9. The outgoing operator has confirmed a mid-stay cleaning between 10:00 a.m. and noon on October 7. A stiff window has also been reported. Responsibility for repair costs remains unresolved.

Reconciliation at 10:30 a.m.: The stay dates and cleaning commitment match the available booking records. The cleaning provider confirms the assignment. The incoming team can handle guest communication through authorized access. The guest’s existing access remains valid for the stay, and an authorized backup contact is reachable.

Open issue: The incoming operations lead takes over the window assessment and will update the guest by 4:00 p.m. Who can approve a chargeable repair will be clarified with the owner by 2:00 p.m. The unresolved allocation of costs stays visible in the record. It is not replaced by an invented commitment.

Acceptance decision: Guest support is accepted with this limitation. A confirmed contact continues to manage the open issue. If neither guest access nor a fallback were secured, that part of the handover would need to be deferred and a workable interim arrangement agreed.

The value lies in keeping these matters separate: guest support continues while a clearly defined decision remains open.

6. Handover record to copy

Use one header per unit and a separate entry for each open case. This template works in an ordinary text field.

Unit and handover time: Property / unit reference / date / time / time zone.

Participants: Outgoing team / incoming team / authorized client representative / reachable backup contact.

Scope accepted: Duties from the handover time / expressly excluded duties / basis of the agreed authority.

Booking snapshot: Data source / reconciliation time / ongoing and upcoming reservation references / subsequent changes up to handover acceptance.

Open case: Situation / confirmed guest commitment / latest progress / action accepted / person performing it / next update / decision still required.

Access and availability: Verified guest access / verified work access / fallback / result and time of contact test / end of previous permissions.

Data transfer: Required data packages / permitted recipient / transfer method / agreed handling of remaining copies.

Decision: Accepted, accepted with a limitation, or not yet accepted / exact scope of limitation / responsible person / completion deadline / confirmation by both parties.

Check actual operations after the handover

Agree on a brief follow-up review, for example after the first arrival or on the next business day. Check that promised services have been delivered, pending decisions are progressing, and later reports reach the right recipient. Close the handover only when remaining items have been resolved or expressly accepted into ongoing operations.

Oprivia’s approach focuses on the connection between an accepted task, its execution, verification, and any outstanding decision. For a new management engagement, the actual handover situation is therefore the useful starting point: what must the team be able to handle on day one, which information is missing, and what addition to the existing operation is needed? An orderly transition starts with those answers.