Onboard an agency portfolio of 50 to 150 properties

A portfolio of 50 to 150 properties is not onboarded by repeating data entry as quickly as possible. It is onboarded by maintaining one source of truth per data domain, proving one pilot property, and expanding only when each cohort passes the same controls.

The goal is a portfolio where every asset, operation, owner, listing, future booking, price, and responsible person can be traced without relying on someone's memory or internal Holidario tools.

Before touching the portfolio#

Assign separate owners for:

• portfolio and duplicate decisions;
• property owners and tax details;
• calendars, bookings, and channels;
• prices and minimum stays;
• daily operations and guests;
• team access;
• finance and compliance when those modules are activated;
• final acceptance of each cohort.

Confirm the Agency plan, active team, and individual accounts of everyone implementing the system. Do not share an administrator account.

1. Create the master inventory#

Before creating properties, prepare a controlled register with one row per real asset. It must not contain passwords, tokens, guest documents, or payment secrets.

Include at least:

Resolve duplicate addresses, repeated listings, and ambiguous owners before importing. Two different names do not prove there are two properties; one property with two listings must not become two properties by default either.

2. Declare one source of truth per domain#

During the transition, record which system controls each domain and from what moment:

Do not allow two systems to write the same calendar or price during an activation. Keeping the previous system available for consultation does not authorize it to continue publishing changes.

3. Divide the portfolio into cohorts#

Use a sequence that limits the reach of any error:

1. Pilot: one representative property, but not the most complex case.
2. Confirmation: 4 to 9 properties similar to the pilot.
3. Expansion: cohorts of 10 to 25, grouped by office, owner, location, platform, or operating model.
4. Exceptions: properties with multiple units, ownership changes, conflicting bookings, an uncertain channel, or special compliance are handled separately.

Size is not a target. Reduce the next cohort if the previous one left ownerless differences, undocumented manual work, or too many distinct cases.

4. Complete the pilot with visible actions#

For the first property:

1. If details must be collected, create and review a property onboarding form.
2. Search Properties first to rule out a duplicate.
3. Import one public Booking.com or Airbnb URL or create the property manually.
4. Verify the relationship between property, operation, and owner.
5. Complete the operation, office, capacity, beds, cleaning, keys, licence, and applicable identifiers.
6. Add every OTA listing with the exact platform, name, ID, and URL.
7. Configure and review prices, minimum stay, and availability.
8. Prepare the Channel Manager, but do not activate the listing before reconciliation is complete.
9. Invite one real user, assign minimum access, and test one allowed and one denied action.
10. Rehearse one arrival, one departure, and one incident with named owners.

The visible import processes one listing at a time. It does not provide a bulk upload of properties, historical bookings, or arbitrary PMS configuration. If the source cannot be represented through these actions, agree an assisted migration with a defined scope, format, validation, and owner before loading data; do not attempt database repair or internal imports.

5. Reconcile every property before channel activation#

Reconciliation must involve someone other than only the person who performed data entry. For each accommodation:

Identity#

• correct property, address, and office;
• one active short-term rental operation;
• correct owner and company;
• consistent capacity, beds, bathrooms, and cleaning fee;
• applicable licence and identifiers reviewed.

Bookings and availability#

• every future booking from the previous system located in Holidario;
• matching arrival, departure, state, channel, and reference;
• owner stays and blocks present;
• no occupied date shown as sellable;
• one free, one occupied, and one blocked date checked.

Do not create a manual copy of a missing OTA booking. Follow the synchronization recovery guide and keep the property out of cutover until the source is understood.

Prices and channels#

• rate plan assigned to every month that will be sold;
• price and minimum stay checked in normal season, high season, and season boundaries;
• correct listing platform, ID, and URL;
• Channel Manager property, room, and rate prepared;
• pre-activation checklist completed;
• only one system authorized to write after cutover.

People and operations#

• administrators and operators use their own accounts;
• property owners see only their assets;
• front desk can find a booking without editing sensitive configuration;
• every arrival, departure, cleaning, and incident has an owner and escalation path;
• the agency knows what to do when a channel remains pending or fails.

6. Record cohort acceptance#

A cohort is accepted only when every row has:

• Holidario property and operation identifiers;
• the person who entered the data and the person who reviewed it;
• the date and time of booking reconciliation;
• count by channel and either zero differences or an approved exception;
• price, minimum-stay, and availability samples;
• connection state and cutover owner;
• users and access tests performed;
• open incidents, owner, and next review;
• an explicit Accept, Accept with exception, or Do not accept decision.

Accept with exception requires contained risk and an exception that cannot cause overbooking, unauthorized access, incorrect charging, or non-compliance. A successful import message or created connection does not replace this acceptance.

7. Activate and observe before expanding#

Activate the pilot first and then a small part of the cohort. Immediately:

1. compare one free, occupied, and blocked date;
2. verify a future price and minimum stay;
3. confirm the mapped listing and accommodation;
4. observe the first new booking or modification received;
5. confirm the team can recognize a discrepancy;
6. record the time of the latest check.

Expand only when behavior is stable and every exception has an owner. If a new difference appears, stop further activations, preserve the reference system, and use the channel preparation recovery guide.

States, denial, and recovery#

• Inventoried: present in the master register, not necessarily in Holidario.
• Created: property and operation exist but are not reconciled.
• Reconciled: data, bookings, blocks, and prices match the approved sources.
• Activated: at least one channel has passed controlled cutover.
• Accepted: it passes cohort criteria and can enter normal operations.
• Blocked: a risky difference, unknown source, or assisted dependency remains.

If a limit is reached, permission is missing, or a module is absent, do not delete data or grant administration to everyone. Confirm the plan, role, and resource. If you see another team's or owner's data, stop viewing it and escalate immediately.

For a failed import, retain the public URL and error; for a calendar difference, retain the platform, reference, dates, and time; for an access issue, retain the user, role, expected property, and denied action. Follow Request help with the necessary information without sharing credentials, guest documents, or private links.

When the portfolio is operational from zero#

Onboarding is complete when:

• all 50–150 inventory rows have an explicit outcome;
• no active property lacks a source of truth or responsible person;
• future bookings, blocks, and prices are reconciled;
• every active channel passed a post-cutover check;
• every person completes their first task with their own account and minimum scope;
• unsupported cases are kept out of operation or have an approved assisted procedure;
• the agency can repeat the next onboarding without depending on the person who implemented the first one.

Keep the inventory and criteria as a living register. New properties must enter through the same abbreviated pilot, reconciliation, and acceptance process, not an informal path.