> 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/site-installation/server-properties/card-security/identifying-unmigrated-cardholders-after-key-migration.md).

# Identifying unmigrated cardholders after Key Migration

### Introduction

During or after a key migration, this procedure describes how to identify cardholders with unmigrated cards (cards that haven’t been presented at a reader and are still using the old keys).

### Prerequisites

Before proceeding with this procedure ensure:

1. Your Command Centre system is upgraded to vEL8.50 and controllers are updated with the relevant software, and
2. A Key Migration has been performed after upgrading to vEL8.50.
3. You have the "Manage Keys" operator privilege.

   **Note:** For migrations being performed across multiple servers in a multi-server system, this procedure should be performed on the server that first started the migration.

### Procedure

1. Click **File** > **Server Properties**.
2. Click the **Card Security** tab, then the **MIFARE Site Keys** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b9c4b36fd09e48425d9afd887107097aa46240dc%2Fcardsecuritytab_managecardmigration.png?alt=media)
3. Click the **Manage Card Migration** button.

   The Manage Card Migration dialog displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-28a928ecb5eb24b318a55ab34c827097b1b268f3%2Fmanagecardmigrationscreen.png?alt=media)
4. Click the **Find unmigrated cardholders** button.

   The Find Tool opens with the **Advanced** tab displayed.

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

   The **Active** radio button will be selected, and an **Only show cardholders with unmigrated cards** checkbox is ticked.

   **Note:** The **Find unmigrated cardholders** button (on the Manage Card Migration dialog), and the **Only show cardholders with unmigrated cards** checkbox will only display if a Key Migration has been performed after upgrading Command Centre to vEL8.50 and controllers have been updated with the relevant software.
5. Click the **Start Search** button. If the site is using multiple card types or technologies, you should use the card ‘Type’ filter to only display results for the relevant DESFire card type.

   The Search grid displays a list of cardholders that meet the unmigrated criteria.

   **Note:** The list of cardholders can be dragged from the Find Tool Search grid into a "dummy" Access Group in Configuration Client that can be used later as criteria for a broadcast notification in Command Centre Client.


---

# 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/site-installation/server-properties/card-security/identifying-unmigrated-cardholders-after-key-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.
