> 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/ja/she-ding/configure-a-door-in-command/move-doors-between-access-controllers.md).
# アクセスコントローラ間でドアを移動する
設定や履歴を失わずにコントローラ間でドアを移動する方法を学ぶ
1台のコントローラー内のスロット間、または別のコントローラー間で、ドアの設定と履歴を簡単に移動できます。これは、何らかの理由でコントローラーの配線を変更したり交換したりする場合に便利です。
{% hint style="danger" %}
ソースと移動先の両方のアクセスコントローラーが存在するサイトで、Access Site Adminである必要があります。詳細はこちら [アクセスコントロールのロールと権限](/access-control/ja/hajimeni/roles-and-permissions-for-access-control.md).
{% endhint %}
{% hint style="warning" %}
ドアを移動できるのは、同じサイト内のみです。
{% endhint %}
{% stepper %}
{% step %}
**Verkada Command で、All Products > Access に移動します。**
{% endstep %}
{% step %}
**移動するドアを選択し、［設定］に移動します。**
{% endstep %}
{% step %}
**［ハードウェア］>［コントローラーとポート］で、［変更］をクリックします。**
{% endstep %}
{% step %}
**［ドアポートの変更］で、ドアの新しいポートを検索して選択します。**
{% endstep %}
{% step %}
**［確認］をクリックして、ドアポートを変更します。**
{% 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/ja/she-ding/configure-a-door-in-command/move-doors-between-access-controllers.md?ask=&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.
