> 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/command-connector/installation/replace-a-command-connector.md).

# Replace a Command Connector

Move the storage drives from a failed Command Connector into a replacement of the same model to keep the recorded video

Use this procedure when a Command Connector has failed, and a replacement of the same model is available.

{% hint style="danger" %}
You need Site Admin permissions for the sites where the failed Command Connector and the replacement Command Connector are located.
{% endhint %}

{% hint style="warning" %}
If one storage drive has failed and the Command Connector is still operating, [contact Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support.md).
{% endhint %}

***

### Requirements

* The replacement Command Connector must meet all of the following:
  * Same model as the failed Command Connector
  * Online
  * Firmware that supports device replacement
  * No connected channels
* The failed Command Connector must meet all of the following:
  * &#x20;Must have at least one connected channel
  * It can be offline or online
* You need physical access to both Command Connectors.

***

### Replace the Command Connector

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

{% step %}
**Select the Command Connector you are replacing.**
{% endstep %}

{% step %}
**Next to Connected Channels, open the menu and select Start Device Replacement.**

<figure><img src="https://3780751499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2FPBOKu1PKWk2MNhg1Aprn%2FScreenshot%202026-11-03%20at%2012.17.48%E2%80%AFPM.png?alt=media&amp;token=a946124c-d124-4d01-ba70-77cb3a614106" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**On Replace your broken Command Connector, select Start.**
{% endstep %}

{% step %}
**Select the replacement Command Connector, then select Next.**

A Command Connector you cannot select shows one of these statuses:

* *Device Offline*
* *Model Mismatch*
* *Unsupported Firmware*
* *Has Connected Channels*

<div align="left" data-with-frame="true"><figure><img src="https://3780751499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2Fr2vFFPAYuezji3aU7vyw%2FScreenshot%202026-11-03%20at%2012.16.40%E2%80%AFPM.png?alt=media&amp;token=1513e131-9205-46bc-b89b-b2b102e8bcaa" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Press and hold the power button to power down both Command Connectors. When both are offline, select They've been powered down.**

<div align="left" data-with-frame="true"><figure><img src="https://3780751499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2FgjlWVNv3XQPJRmBwGVsI%2Fimage.png?alt=media&amp;token=c3f0b57d-1196-49bd-b513-fb139f0e9498" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Remove all drives from the replacement Command Connector, then select All drives are removed.**

Press the button to the right of the blue stripe, gently pull the caddy out, and set those drives aside.

<div align="left" data-with-frame="true"><figure><img src="https://3780751499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2F9m0Pz5VS8grXIzig5dWo%2Fimage.png?alt=media&amp;token=f307f6b1-b7b1-40bf-858d-6be496bb3b07" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Move all drives from the failed Command Connector into the matching slots on the replacement, then select All drives are in matching slots.**

{% hint style="danger" %}
Move every drive from the failed Command Connector into the matching slot on the replacement. Leave the caddy door open until the drive is fully seated, then close the caddy door until it clicks.
{% endhint %}

<div align="left" data-with-frame="true"><figure><img src="https://3780751499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2F6FIqZUoW7D5vawKmCuyh%2Fimage.png?alt=media&amp;token=0dd74de4-dc02-4d3a-9967-47ad9d0fc10f" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Power on the replacement Command Connector and leave the failed Command Connector powered off. When the replacement is online, select Transfer Channels.**

<div align="left" data-with-frame="true"><figure><img src="https://3780751499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2FlLkg1XdAvrhKCAO7jCAu%2Fimage.png?alt=media&amp;token=eb6a1add-d6cc-4b69-9544-539ce833a368" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Stay on this page while Command shows&#x20;*****Transferring Channels*****.**

This can take a few minutes.
{% endstep %}

{% step %}
**When Command shows&#x20;*****New device is set up successfully*****, select New Command Connector.**

The channels from the failed Command Connector are now on the replacement.
{% endstep %}
{% endstepper %}

***

### After the transfer

* Video stored on the drives you moved is available on the replacement Command Connector.
* The failed Command Connector no longer shows those channels.

{% hint style="warning" %}
Drive status can take a few minutes to update. You cannot add cameras while a device replacement is in progress.
{% endhint %}


---

# 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/command-connector/installation/replace-a-command-connector.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.
