Docs/Migrate/Migrate from

Migrate from Guesty

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

Start a migration from Guesty

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": ["guesty"]
  }'

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

What comes across

PropertiesName, public title, address, occupancy, check-in/out times, active state.
PhotosCarried across in full.
AmenitiesCarried across in full.
Rooms & bedsBedroom and bed counts; no per-room bed layout.
House rulesHouse manual, check-in instructions, wifi, parking and trash notes.
FeesCleaning, pet, extra-guest and other fees per reservation.
TaxesPer-tax breakdown per reservation.
GuestsName, email and phone from each reservation.
ReservationsPast and future stays with the full money breakdown, channel and confirmation codes.
PaymentsPayments recorded against each reservation.
ConversationsThreads, messages, and audit entries as timeline events.
CalendarAvailability per night.
Nightly ratesNightly price and minimum stay per night; no rate plans or seasonal rules.
Channel linksAirbnb, Booking.com and VRBO ids from the listing's channel integrations.

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

Airbnb, Booking.com and VRBO

Guesty 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