Migrating from Cloudbeds to Talk with Guest — a two-week playbook.
This is the playbook the Talkguest migration team runs when a Portuguese property moves from Cloudbeds. Fourteen working days from kick-off to go-live, one named migration engineer, no downtime, no stopped bookings, Autoridade Tributária factura sequence continuous.
The shape of the property and the shape of the migration
This playbook is written for an independent Portuguese property currently on Cloudbeds — typically between 15 and 80 keys, a mix of OTAs (Booking, Expedia, Airbnb, sometimes Hostelworld or Google Hotels), a Portuguese factura setup running through a Cloudbeds partner module, and WhatsApp handled either on a personal reception phone or through a marketplace connector. If your property is very different — a 400-key resort, a purely OTA-driven vacation rental network, a non-Portuguese property with no factura requirement — the general approach still applies but specific timings and steps will differ. Ask the migration engineer at kick-off.
The playbook assumes a fourteen-working-day window (Monday of week one through Friday of week three, allowing a working weekend or a low-occupancy midweek slot for the channel-manager cutover). A property that is running above 90% occupancy every night can extend the parallel-run window to twenty-one working days without adding cost; a property with an idle midweek can compress to ten working days if the general manager can be available for daily one-hour stand-ups.
Fourteen working days, one page
- Day 1 — Kick-off call. Migration engineer, general manager and the property's accountant on one call. Current-state stack documented: Cloudbeds plan tier, active add-ons, OTAs and their room-type mapping, active PSP, WhatsApp status, factura partner module in use, active VAT profiles. Target-state configuration signed off. Cutover date agreed.
- Day 2 — Data export from Cloudbeds. Guest CRM exported (up to five years of profiles); upcoming and historic reservations exported (24 months by default); rate plans and room types exported; OTA property IDs recorded; PSP tokens and mandate references documented.
- Day 3 — Talkguest tenant provisioned. Property record created; users invited; rooms and room types mapped to Talkguest's model; VAT profiles configured to match Portuguese accommodation, cleaning fee, city tax and utility passthrough rates as applicable; certified factura series carried across from the AT registration.
- Day 4 — Guest CRM load. Historic guest profiles loaded into Talkguest with preferences, allergies, VIP flags and lifetime value pre-computed. Duplicate detection runs; conflicts surfaced to the general manager for resolution.
- Day 5 — Reservation load, historic. The 24-month historic reservations loaded read-only, linked to the correct guest profiles. Purpose is guest-history search, not operational use.
- Day 6 — Reservation load, upcoming. Every upcoming reservation loaded and cross-checked one by one against Cloudbeds. Discrepancies (rate mismatches, deposit differences, folio balances) resolved and countersigned by the general manager.
- Day 7 — Cross-check pass one. Every upcoming reservation, every folio balance, every deposit, verified between the two systems. This is the day where discrepancies get caught before they turn into guest-facing problems.
- Day 8 — OTA re-mapping. Booking, Expedia, Airbnb and any other active OTAs re-mapped in Talkguest's channel manager. Rate plans, room types and cancellation policies aligned. No live connection yet — this is preparation.
- Day 9 — WhatsApp setup. WhatsApp Business API number provisioned or ported. Pre-arrival, in-stay and post-checkout templates loaded in Portuguese, English and any additional language the property serves. Templates tested end-to-end on a dummy reservation.
- Day 10 — Cross-check pass two. Every reservation, every folio, every deposit, verified one more time. New reservations that came in during the parallel-run period are captured. Final go/no-go decision with the general manager at end of day.
- Day 11 — Channel-manager cutover afternoon. Between 14:00 and 18:00 Lisbon time, Booking, Expedia and Airbnb are switched from Cloudbeds' channel manager to Talkguest's. Rates and inventory push confirmed on each channel; a small end-user test booking is placed and traced end-to-end.
- Day 12 — Go-live morning. Talkguest becomes the master of record. Cloudbeds moves to read-only. WhatsApp Business API becomes live for guest conversations. The migration engineer is on the property or on a permanent Zoom bridge until end of day.
- Day 13 — First full day, live. Reception, housekeeping and reservations run entirely on Talkguest. Migration engineer on-call. Any operational surprises resolved same-day.
- Day 14 — Sign-off and hand-off. Migration engineer runs a walk-through of the first live day's numbers with the general manager and the property's accountant. Post-go-live support window opens; standard support queue takes over at day fourteen plus fourteen.
Three things that catch first-time migrators
Cloudbeds virtual-card handling. Cloudbeds processes Booking.com virtual credit cards through its own PSP. Talkguest processes them through the property's configured PSP (Stripe, SumUp, Mollie, Adyen, Redsys or Ifthenpay). During cutover, VCC-paid reservations arriving between cutover minus 15 days and cutover plus 15 days need to be manually reconciled — the migration engineer produces a spreadsheet of these, the property's accountant signs off, and the money follows the new PSP from cutover onwards. This is a real accounting event, not a marketing footnote, and it needs the accountant's attention.
Portuguese factura partner module. Cloudbeds handles Portuguese factura through a partner module. That module typically produces its own factura sequence separate from anything the property's accountant would recognise as the AT-registered series. The migration engineer verifies with the accountant which series is the true AT-registered series and continues that one on Talkguest — the partner module's sequence is retired as of cutover date. Historic facturas from the partner module are imported as an audit trail.
Cloudbeds marketplace apps. Any marketplace apps active on the Cloudbeds tenant — WhatsApp connector, upsell engine, reputation tool, review-response bot — are enumerated at day one and either replaced by native Talkguest modules or, if the property wants to keep them, connected through Talkguest's API integrations. This is a decision the general manager makes explicitly; it does not happen by default.
The two weeks after go-live
The migration engineer stays on the account for fourteen working days after go-live. During this window they run a daily fifteen-minute check-in with the general manager, watch the platform for operational irregularities, and resolve edge cases the migration itself did not surface. Typical day-15-plus surprises: a Booking VCC that lands on an unmapped rate plan; a factura where the VAT rate needs a manual override because the guest is an EU-VAT-registered corporate; a WhatsApp template that needs a small edit because the pre-arrival address changed after cutover.
At day 28 the migration engineer runs a final review with the general manager and the accountant, walks through the first monthly SAF-T (PT) export, and formally hands the account to Talkguest's standard support queue. The relationship does not disappear — the migration engineer remains a warm contact for anything ambiguous — but from day 28 the property is fully self-sufficient.
Read the Solar do Chiado case study for a real migration from a legacy PMS, and the FAQ for the accountant's questions we hear most often. Ready to start? Head to get access.