Migration · Legacy → Guest Talk · 7-14 days

Migrating to Guest Talk from a legacy PMS or spreadsheet.

Not every property is on a modern cloud PMS. Guest Talk has migrated properties from Beds24, roomMaster, WebRezPro, Rezovation, and a surprising number of Excel spreadsheets that ran real hotels for a decade. This page covers the generic path we use for a legacy source, with notes for each of the source systems we see most often.

The generic path

Days 1-2. Scoping and export. We inspect your current system and determine which export mechanism is available. Modern legacy systems usually have a CSV export; older ones (Excel, homebrew databases) require a bespoke extraction. Very old systems (green-screen terminals on Windows XP) need an on-site visit to run the extract.

Days 3-5. Dry-run workspace populated. You review and correct the mapping.

Days 6-8. Production workspace configured. Staff training. OTA re-certification kicks off.

Days 9-11. Cutover. Guest Talk becomes the write plane; legacy system goes read-only.

Days 12-14. Stabilisation and decommission of legacy system.

Notes per source system

Beds24. Beds24 has a comprehensive CSV export; migration is straightforward. Watch for custom booking form fields that need to be preserved as Guest Talk custom fields.

roomMaster. Legacy Windows PMS. Extract via the built-in export utility; older versions require the report writer to generate CSV. Certain financial history categories require manual reformatting.

WebRezPro. Cloud-based; export via the Data tab. Rate plan model differs slightly from Guest Talk's; expect to spend time in dry-run reviewing rate mappings.

Rezovation. Legacy platform. Export via the Reports tab. Reservation notes come through unfiltered; we help you triage stale notes during dry-run.

Little Hotelier. Modern SiteMinder platform; export via Settings > Data Export. Channel connections need to be moved from SiteMinder to Guest Talk's channel manager during cutover.

Sirvoy. Modern platform; standard CSV export. Migration is usually smooth, especially for small properties.

Spreadsheet. Send us the spreadsheet. We format it to a normalised CSV during dry-run and highlight fields that require your input. Spreadsheet migrations are often faster than software migrations because there is no rate model to align.

Homebrew database. Send us the schema (or the SQL dump). Our migration engineer builds a bespoke ETL for the specific tables. Add 2-3 days to the timeline.

Data quality

Legacy sources often contain duplicate guest records, stale reservations that were never cancelled, orphan folios and other data debris. During dry-run we surface every such record and ask you to decide: merge, delete, keep. This is often the most useful part of the migration because your staff finally sees a clean list.

What we do not migrate automatically

User accounts and passwords are not migrated (users are re-created in Guest Talk with new credentials for security). Financial history older than 5 years is kept in the legacy export archive but not imported into Guest Talk. Cache-only data (search history, temporary drafts) is discarded.

Getting started