Evaluate the downloaded file, not the button
A PMS export button does not prove that a file contains the records your operation needs in the correct scope. During a buying demonstration, ask whether the downloaded file can be understood and reconciled elsewhere. Real customer information is unnecessary; prepared fictional records provide a useful start. Review filters, dates, page limits, field meaning and unique references together. This article guarantees neither complete migration nor backup for any product. It uses two public documents to propose asking for an actual file and a repeatable check. A polished screen and a usable export are separate purchasing considerations.
Check the documented version and scope
Cloudbeds’ November 24, 2025 documentation for the new reservation list explains that list filters do not automatically carry into the export wizard and must be selected separately. It is a workflow example, not today’s news. Oracle OPERA Cloud 25.4 documents exporting the current page’s search results in supported table views. Neither establishes identical behaviour across products. Ask which screen, version and export operation are demonstrated. “Excel export available” does not establish all-record extraction, complete backup, restoration or trouble-free migration. Keep the documented action separate from any wider promise that has not been tested.
Prepare six fictional reservations
Ask for six entirely fictional reservations with some inside and outside the date range, a cancelled record and differing statuses. Write each record’s identifiable reference and expected scope before running the export. Do not add real identity, contact or access information. State which records should appear under the selected filters beforehand rather than redefining success after opening the file. This test demonstrates a workflow, not a success rate. Six records cannot cover a large property’s full needs. Nevertheless, an unexplained field or missing filter in the small test gives a clear reason to seek clarification before accepting a broader export.
Verify filters and pagination again
Compare the displayed date range with the file’s actual scope. If the export window has its own filters, inspect those too. When results span several pages, does the file contain the current page, selected records or all results? Ask the supplier to demonstrate the answer. Do not equate rows with reservations: one reservation may appear across several rows. Reconcile included records through unique references. This is a purchasing requirement, not an assertion about a specific product’s large-file behaviour. The operation’s scope should be visible and repeatable, with results consistent with the data selected for the test.
Check what the fields mean
A date or amount alone is insufficient. Does the date mean creation time, arrival day or stay night? Which currency and amount scope apply? Can another tool interpret the time zone, decimal separator and Turkish characters? Use the fictional file rather than requesting payment details or real guest records. Compare field explanations with supplier documentation. When a field is missing, identify the need it prevents; treating every available column as necessary adds needless data. This is not a technical integration recipe. It checks whether an operator can correctly interpret the file and whether a field’s label matches its content.
Ask about permissions, support and later access
Who can generate the file, what may each role see, and how does support help if the wrong scope is chosen? Ask the supplier to distinguish a standard operation from a specially prepared output. Obtain written clarification of export arrangements when service use ends; no contractual entitlement or legal outcome is assumed here. The supplier should explain timing, scope and responsibility. Downloadability does not establish secure storage; the team needs its own sharing and retention routine. Leave undemonstrated abilities as open questions rather than marking them present. Visible uncertainty is a more assessable result than an unsupported promise of complete migration.
Write acceptance criteria before export
For the small test, require expected fictional references, clear exclusion of out-of-scope records, explained repeated rows and correctly readable fields in an independent tool. Keep an unmet condition open rather than accepting the file as successful. Generate another output with the same scope and repeat the check. This does not prove complete historical migration or import into another product; it defines requirements for a larger trial. Compare suppliers using the same fictional test and needs list. Evaluate tangible scope before “you can export everything,” including the property’s future ability to work with its information in the purchasing decision.