Migrate from Smoobu
Moving a property manager off Smoobu: they sign in to Smoobu on the hosted page, and their data is copied into a workspace you read with the regular API. Nothing changes in their Smoobu account.
Start a migration from Smoobu
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": ["smoobu"]
}'The hosted page asks for exactly what Smoobu needs to grant access — see connecting Smoobu for where the property manager finds it.
What comes across
| Properties | Name, address and occupancy. Descriptions, photos and amenities are not mapped. | |
| Amenities | Amenity names. | |
| Rooms & beds | Bedrooms, beds and bed types. | |
| Fees | Total price only — no cleaning fee / tax / host-fee breakdown. | |
| Guests | Name, email and phone from each reservation. | |
| Reservations | Past and future stays: dates, status, guest count, total price, source channel. | |
| Conversations | Conversation threads with every message. | |
| Calendar | Availability per night. | |
| Nightly rates | Nightly price and minimum stay per night; no rate plans or seasonal rules. |
Not carried from Smoobu: photos, house rules, taxes, owners, payments, 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
Smoobu 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.
AI