> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-site-configuration/salto-native-mode-migration.md).

# Salto Native Mode Migration

### Introduction

This section is intended to provide a set of instructions for the migration of a Legacy Mode integration into Native Mode. If your site is already in Native Mode, this section can be skipped.

Salto's Native Interface enhances cyber security and user functionality, and future-proofs the Salto integration with Command Centre, allowing extended functionality in the future. It also ensures Gallagher Command Centre will work with future Salto features. Salto's legacy interface does not support end-to-end encryption. By migrating to Salto Native Interface, encryption is enabled between Command Centre and Salto Space. Operators will benefit from additional features, for example, Access during lockdown, improving the user experience.

### Native Mode versus Legacy Mode

<table><thead><tr><th width="480">Native - Salto-managed users (access managed by Command Centre)</th><th>Legacy - Host-managed users</th></tr></thead><tbody><tr><td>Command Centre Cardholders are the Users in Salto's database</td><td>Command Centre Cardholders do not exist as Users in Salto's database</td></tr><tr><td>Communication between Gallagher Command Centre and Salto Space is encrypted (HTTPS)</td><td>Communication between Gallagher Command Centre and Salto Space is unencrypted (STP)</td></tr><tr><td>New user access features are available</td><td>User access features are limited</td></tr></tbody></table>

### Lockdown overrides

The Lockdown override only works for Native Mode. When the **Entry allowed during lockdown** access privilege (on the **Privileges** tab of the Access Group) is enabled, a Lockdown override can be performed to allow members to enter Access Zones contained in the Access Group, when those Access Zones are in lockdown mode.

### Reports

Cardholder Reports can be configured in Command Centre Client that show whether a cardholder has a Salto Native encoded card, Salto Legacy card or no Salto card.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-22541b480edda3faa2e240464d271b4178630eb6%2Fsaltonative_chreport.png?alt=media)

Refer to these sections to ensure you have configured Salto to encode cards in native mode, if you are using 26 bit cards configuration is required in Salto Space:

* [Reason for using 64-bit Wiegand format](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/encoding-cards/reason-for-using-128-bit-wiegand-format.md)
* Configuring Key to support Space CUADAP 64-bit integration
* [26 bit Wiegand Setup](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/encoding-cards/set-up-a-salto-reader-as-a-third-party-reader-using-wiegand-connection.md)

### Migrating Salto Legacy Cards to Salto Native Mode

The Salto Legacy Card Migration Tool enables a smooth transition from Salto Legacy Cards to Salto Native Mode, simplifying the upgrade process.

**Note:** You must be in Salto Native Mode to use this tool.

For further detail refer to the document **"Salto Migration Tool\_Release Note.pdf"** located in the `'Utilities/Salto'` directory of the Command Centre installation media.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/space-site-configuration/salto-native-mode-migration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
