Identify source sheets, active tabs, formulas, lookup tables, manual notes, and the people who depend on them.
Spreadsheet-to-software transition
Moving hospitality operations from spreadsheets into HOS.
A spreadsheet migration is not just a file import. The important work is deciding which columns are real records, which formulas encode business rules, which tabs represent workflows, and which manual conventions should become explicit product states.
This page describes the HOS implementation approach. Exact import tooling, migration assistance, supported file formats, and rollout scope depend on the active commercial release.
Implementation principle
Preserve the operating logic, not just the cells.
A spreadsheet can contain years of embedded operating knowledge. A responsible transition identifies that knowledge before replacing flexible cells with more structured software.
Transition model
A controlled sequence before cutover.
The exact implementation may vary, but each stage should make assumptions, ownership, and validation more explicit.
Distinguish properties, reservations, guests, payments, tasks, and evidence from the formulas or conventions used to coordinate them.
Define which spreadsheet fields map into HOS records, statuses, relationships, permissions, or retained reference data.
Test a controlled subset before attempting a broader cutover so field interpretation and workflow assumptions can be checked.
Historical data should be migrated because it supports operations, audit, or reporting—not simply because it exists.
Control points
What should remain protected during the move.
Keep the original workbook or exports available as a reference until the migrated state has been reconciled.
Document formulas and manual conventions before deciding whether HOS should reproduce, replace, or retire them.
Avoid making the team depend on an unvalidated new workflow while live bookings and guest obligations continue.
Keep spreadsheets where they remain the simpler tool for analysis, planning, or ad hoc modelling.
Readiness
A spreadsheet transition is ready when the team can explain the new source of truth.
01
Core records have owners and clear destinations in HOS.
02
Critical formulas and manual rules have been reviewed rather than silently discarded.
03
A representative sample reconciles against the source workbook.
04
The team knows which spreadsheet workflows remain, which retire, and which become product workflows.
Boundary
Keep the implementation promise narrower than the evidence.
SheetSolutions does not claim every spreadsheet can be imported automatically. Complex formulas, macros, scripts, custom schemas, or inconsistent historical data may require manual mapping or may be better retained as reference material.
Compare spreadsheets with the HOS operating model →