A hotel converting from magstripe to SALTO is not swapping one lock for another. It's replacing a standalone door device with a single access network that spans guest rooms, back-of-house doors, and the PMS that drives both. Before a conversion starts, it helps to see that network as one diagram rather than a list of hardware.
How a reservation becomes a credential
The PMS stays the system of record for who is allowed where and when. In a SALTO-PMS integration, a key creation command originates either from staff at the front desk or from a guest self-service kiosk, and that command is what triggers the credential — not the room assignment by itself. As the Mews-SALTO integration documents it, "when a system operator triggers a new key creation either via the PMS (Mews Web app) or via the Mews Kiosk, a key encoding command is created and the Mews Connector application receives this new command notification" (MEWS | Salto). The same source distinguishes two kiosk modes — a guest-only self-check-in flow and a co-op mode where staff walk the guest through check-in together — which matters when deciding how much unattended self-service a property actually wants at the front desk.
Once that command fires, both a physical card encode and a mobile digital key can be issued from the same event, and cancelled bookings or completed checkouts trigger automatic key deactivation on the SALTO side. Ask your PMS and integrator exactly which PMS actions (new reservation, re-rooming, early checkout, no-show) generate which SALTO events, because that mapping — not the lock model — is what determines whether a guest's key actually stops working when it should.
Staff and housekeeping rights are a separate layer
Guest credentials and staff credentials aren't the same object in the system, and conflating them during setup is a common source of access problems after go-live. Staff and housekeeping access is managed as its own set of operations inside the PMS-access integration, separate from the guest check-in flow, and housekeeping's real-time room-status data is what lets the access system route staff efficiently: "Housekeeping gets access based on real-time room status. No need to knock on doors — staff can head straight to rooms they know have been vacated" (Reimagining Hospitality: the role of PMS integration in smart access ecosystems). That only works if housekeeping zones, shift schedules, and department-level door groups are mapped in the access software as their own hierarchy — ask your integrator to walk through how a housekeeper's credential differs from a front-desk credential and from an engineering credential before locking the door schedule.
Bringing back-of-house doors and elevators onto one network
The architectural piece that makes zoning possible is SALTO's SVN (Salto Virtual Network) backbone, which lets both battery-operated, stand-alone locks and hardwired online access points share one access-rights database without every door needing a home-run cable. SVN-Flex specifically extends real-time credential updating beyond the front desk to any door in the property: it "brings guest and staff credential updating to the ultimate point in access control: the door," and SVN-Flex functionality can be enabled "on any product in the Salto XS4 electronic lock range including guest room doors ... guest services doors and back-of-house access points" (Salto's SVN-Flex electronic locking technology). That same source notes SVN uses stand-alone, battery-operated locks with no door hardwire installation required, cross-links wireless locks and online access points, and is built to scale "up to hundreds of doors with thousands of users" without consuming significant IT resources.
For an integrator, that network decision point is specific: which doors justify an online, hardwired connection (main entrances, elevator car-call restriction, high-traffic back-of-house doors where real-time revocation matters most) versus which doors are fine as battery-operated offline locks that simply need to be visited periodically by an authorized credential to pick up permission updates. Elevator integration, loading dock doors, and amenity spaces like a pool or gym typically sit on the same SVN backbone as guest rooms, with access rights to each tied to the same reservation and department logic rather than managed as a separate system — but confirm with your SALTO integrator exactly which doors in your property plan will run online versus battery-operated SVN before conduit and door hardware are ordered.
What the network and integrator need to provision
SVN's design goal is to avoid taxing hotel IT infrastructure, but a conversion still has real network dependencies: encoders at the front desk and any satellite check-in points, a server or cloud instance running the access management software (ProAccess SPACE or equivalent), and a defined number of online gateway nodes wherever real-time door status, lockdown, or remote-open capability is required. Your integrator should document, door by door, whether each lock is online (wired, real-time) or offline/SVN (battery, updated by credential traffic), because that decision drives both cabling scope and how quickly a lost-card cancellation actually reaches that specific door.
Sequencing a floor-by-floor conversion without taking rooms offline
A magstripe-to-SALTO conversion is a hardware swap at the door, but the credential and PMS-interface work can largely run in parallel with operations. Phasing by floor or wing lets a property keep selling rooms on floors that haven't converted yet while the new locks and encoders are commissioned and tested on completed floors; housekeeping and front-desk staff need brief training on the new encode/check-in flow before each floor goes live, and a short overlap period where both key types are issuable on a transitioning floor reduces the risk of a guest arriving to a card that doesn't work yet. The specific pacing should be built with your integrator and PMS vendor around your reservation calendar and housekeeping staffing, not assumed from a generic schedule.
This kind of access architecture work is part of what Cave Group designs for hotel and club properties under its hospitality practice — guest-room automation, PMS integration, networking, and access control built and supported as one system rather than separate vendor silos. For related coverage of how the PMS and electronic lock stack fit alongside guest-room lighting control, see Hotel PMS Integration: Opera, Mews, Salto & myRoom XC.
Questions to resolve before signing off on the design
- Which PMS events (reservation, re-rooming, early checkout, no-show) map to which SALTO credential actions, and has that mapping been tested, not just configured?
- How are staff and housekeeping access rights structured separately from guest credentials, and who owns updating department-level door groups after go-live?
- Which doors in the property — elevators, loading dock, amenity spaces — will run as online SVN nodes versus battery-operated offline locks, and why?
- What is the floor-by-floor conversion sequence, and how much overlap time is built in so no occupied room loses key access mid-stay?
Answering these before the lock order goes in avoids the scramble of re-mapping zones or re-running cable after doors are already hung.