> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/access-control/configuration/configure-a-door-in-command/move-doors-between-access-controllers.md).

# Move Doors between Access Controllers

Learn how to move doors between controllers without losing configuration and history

You can easily move the configuration and history of a door between slots on a single controller, or between different controllers altogether. This is useful if you are rewiring or replacing a controller for any reason.

{% hint style="danger" %}
You must be an Access Site Admin for the site where both the source and destination access controllers exist. Learn more about [Roles and Permissions for Access Control](/access-control/getting-started/roles-and-permissions-for-access-control.md).
{% endhint %}

{% hint style="warning" %}
You can only move doors within the same site.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Access.**
{% endstep %}

{% step %}
**Select the door to be moved and go to Settings.**
{% endstep %}

{% step %}
**Under Hardware > Controller and Port, click Change.**
{% endstep %}

{% step %}
**On Change Door Port, search for and select a new port for the door.**

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-0b07d3073475d01a98c3ff3123fcf2e951303285%2Fa748efe36898f0aea66ae5009357bc4eaea2df6e.png?alt=media" alt="" width="406"></div>
{% endstep %}

{% step %}
**Click Confirm to change the door port.**
{% endstep %}
{% endstepper %}


---

# 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.verkada.com/access-control/configuration/configure-a-door-in-command/move-doors-between-access-controllers.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.