Migrate from Cloudbeds

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

Start a migration from Cloudbeds

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

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

What comes across

	Properties	Each room type as a listing: name, description, capacity, property address, check-in/out times.
	Photos	Room-type photos, else the property's photos.
	House rules	Check-in and check-out times.
	Fees	Accommodation and additional-items totals; additional items are not itemized.
	Taxes	Total taxes and fees per reservation.
	Guests	Name, email and phone from each reservation.
	Reservations	Past and future stays with the assigned room and channel. A multi-room booking becomes one reservation per room.
	Payments	The amount paid so far per reservation, not individual payments.
	Calendar	Rooms left per night for each room type, and blocked nights.
	Nightly rates	Nightly price of each room type on its base rate; derived rate plans are not read.

Not carried from Cloudbeds: amenities, rooms & beds, owners, conversations, channel links. Set these up in the destination — the migration report lists them so your onboarding can prompt for them.

Airbnb, Booking.com and VRBO

Cloudbeds does not expose its channel links, so the property manager matches each channel listing to its property when reconnecting the channels in your product. See channel links and cutover.