Which reservations NextPax can and cannot import during migrations and channel takeovers

During a migration or channel takeover, NextPax imports existing reservations directly from the channel's API. The core principle is simple: NextPax can only import reservations that the channel actually exposes to us. We cannot import a reservation that the channel does not return, that does not belong to a property connected to NextPax, or that the channel API no longer makes available. This is a limitation of the channel APIs, not of the migration process itself.

What can be imported

Active, current reservations that meet all of the following: the reservation has a check-out date in the future, the property is correctly connected to NextPax as the connectivity provider on that channel, and the listing is mapped to an NextPax property ID. For Booking.com these reservations are retrieved through the channel's reservations summary endpoint, which returns both old and new reservations that have a future check-out date and is also used to pick up modifications and cancellations of those future-dated reservations. Expedia and Vrbo behave the same way in practice: during recent migrations every reservation that could be retrieved and was in a booked/active state was successfully imported into NextPax.

What cannot be imported

• Past reservations. Reservations with a check-out date in the past — i.e. stays that were already consumed before the migration — are never imported and are not retrievable. The channel APIs only expose future-dated reservations to us.
• Reservations for properties that are not properly connected. If the hotel/property is not correctly connected to NextPax as the provider, Booking.com returns a 403 Forbidden with "hotel reservation does not belong to any of provider's hotels." NextPax cannot import a reservation that the channel does not consider ours. This must be resolved on the property side (connection and mapping) before the reservation can be retrieved.
• Reservations for unmapped listings. If a listing has no NextPax property ID, an incoming reservation cannot be matched to a property. The onboarding team must map the listing first.
• Cancelled reservations. NextPax does not fetch cancelled reservations from Booking.com. As a result, cancellations that occurred before or around the migration are not picked up automatically, which can leave a calendar out of sync. Cancellation data for the migration window therefore has to be handled separately (for example via a list of cancelled reservations supplied during the switch) rather than expected through the automatic import.

How the import handles large volumes

NextPax imports reservations through a queued, asynchronous pipeline that is built around the channels' own API limits. Channel reservation APIs apply rate limits and batch-size limits — for example, retrieval is paginated and mutation batches are capped (Vrbo, for instance, limits a batch to 100) — so NextPax queues reservations and processes them in controlled batches rather than all at once. This is a deliberate design that keeps large migrations, often involving thousands of reservations, stable and reliable while staying within each channel's limits, and it scales cleanly as portfolio and migration sizes grow. Continuous improvements have also been released to further reduce missing reservations and duplicates. These mechanics govern throughput and timing only; they do not change which reservations are retrievable — that is still determined by the channel API boundaries described above (future check-out date, correct connection, and mapping).

Practical guidance for migrations and takeovers

Before a takeover, make sure every property is correctly connected to NextPax as the provider and mapped to an NextPax property ID, so reservations are not rejected with a 403. During reconciliation, disregard past (already-consumed) reservations, since these are out of scope by design. Supply cancellation data for the migration window separately, as cancelled reservations are not fetched automatically. When a specific reservation is expected but missing, the first checks are whether its check-out date is in the future, whether the property is connected, and whether the channel actually returns it — if the channel does not return it, NextPax cannot import it.