Docs/Migrate/Migrate from

Migrate from Hostaway

Moving a property manager off Hostaway: they sign in to Hostaway on the hosted page, and their data is copied into a workspace you read with the regular API. Nothing changes in their Hostaway account.

Start a migration from Hostaway

curl https://api.repull.dev/v1/connect \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "purpose": "migrate",
    "redirectUrl": "https://yourapp.com/onboarding/migrated",
    "workspace": { "name": "Seaside Rentals" },
    "allowedProviders": ["hostaway"]
  }'

The hosted page asks for exactly what Hostaway needs to grant access — see connecting Hostaway for where the property manager finds it.

What comes across

PropertiesName, address, occupancy, check-in/out times.
PhotosCover image.
AmenitiesAmenity ids as Hostaway names them.
Rooms & bedsBedroom and bed counts.
House rulesHouse rules text.
FeesCleaning fee and channel commission; other fee lines are not split out.
TaxesTotal taxes only.
GuestsName, email and phone from each reservation.
ReservationsPast and future stays: dates, status, guest count, total price, source channel.
ConversationsConversation threads with every message.
CalendarAvailability per night.
Nightly ratesNightly price and minimum stay per night; no rate plans or seasonal rules.
Channel linksAirbnb and VRBO listing ids from their listing URLs. Hostaway exposes no Booking.com id.

Not carried from Hostaway: owners, payments. Set these up in the destination — the migration report lists them so your onboarding can prompt for them.

Airbnb, Booking.com and VRBO

Hostaway exposes which channel listing each property is linked to, so the channel map can link them for you when the property manager reconnects the channels in your product. See channel links and cutover.

AI