The starting point
Marlowe Bay Hotels operates three independent coastal properties, each with its own history and — until recently — its own on-site server. Every property had been set up separately over the years, by different local contractors, at different times. The result was three servers of different ages, three slightly different software configurations, and a reception experience that varied depending on which property you happened to be working at.
None of it was quite broken enough to force a decision, but all of it added friction: seasonal staff had to be trained differently at each site, finance had to reconcile three separate systems, and the group's IT support was really three loosely related arrangements rather than one coherent setup.
Understanding before building
We spoke with each general manager and with head office finance before designing anything, mapping how the property management system, reservations and back-office finance software were actually used at each site, where the differences genuinely mattered, and where they were simply historical accidents.
That groundwork let us design a single environment that suited all three properties, rather than forcing one site's setup onto the other two — and it shaped a migration order built around each property's quiet season.
What we built
We deployed one centrally managed Remote Desktop Services (RDS) environment with FSLogix profile containers, shared across all three properties. Reception, reservations and back-office staff at every site now see the exact same desktop, the exact same version of every system, and the exact same performance — regardless of which property they're logging in from.
One platform, three properties
A single centrally managed environment replacing three separate servers — the same desktop and software at every site.
FSLogix profiles
Fast, consistent logins for reception and back-office staff, wherever they're working from.
Property software, handled
PMS, reservations and Sage 50 finance installed, configured and data-migrated by us, licensed correctly per property.
Seasonal-ready by default
Onboarding a new seasonal hire is now the same five-minute process at every property, not a different routine per site.
The migration — property by property, off-season
With three live, guest-facing properties, a big-bang cutover was never on the table. Instead we migrated one property at a time, each scheduled around its own quietest weeks, so reception never had to run a live front desk on unfamiliar systems during a busy period.
Discovery & planning
PMS, reservations and finance mapped across all three properties, alongside each site's seasonal calendar.
Build
One shared RDS environment designed and deployed with FSLogix, sized for all three properties with room for peak season.
Property-by-property migration
Each property's data and software migrated during its own off-season, one site at a time, old servers decommissioned as each cutover completed.
Cutover & support
All three properties now run the same platform. We stayed close through each site's first weeks and manage the group ongoing.
The result
Marlowe Bay Hotels retired three ageing, mismatched servers and now run one consistent platform across every property. Reception and back-office staff see the same systems wherever they're based, seasonal onboarding is fast and repeatable, and head office finance works from one coherent picture instead of three.