Migrate from Mews

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

Start a migration from Mews

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

The hosted page asks for exactly what Mews needs to grant access — see connecting Mews 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, active state.
	Photos	Room-type images, when the property has assigned them.
	House rules	Check-in and check-out times.
	Fees	Nightly room charges plus products (cleaning, pet, extra guest, other) per reservation.
	Taxes	Per-tax-code breakdown, including city tax.
	Guests	Name, email and phone from each reservation.
	Reservations	Past and future stays with the assigned room, channel, and the money breakdown in the property's own pricing basis.
	Payments	Charged payments against each reservation.
	Calendar	Rooms left per night for each room type, and stop-sell closures.
	Nightly rates	Nightly price of each room type on its default base rate; other rate plans are not read.

Not carried from Mews: 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

Mews 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.