> 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/products/product-advisories/current-advisories/controller-6000-superseded-status-and.md).

# Controller 6000 superseded status and obsolescence pathway

Plan Controller 6000 replacement and Command Centre upgrades before support ends.

Introduced in 2009, the Controller 6000 became the cornerstone component of the Gallagher solution ecosystem. It is now being obsoleted to clear the pathway to the **C7000 platform**.

Building on the Controller 6000's reputation, Gallagher introduced the **Controller 7000 Single Door in February 2023**, the **Controller 7000 Standard in November 2023**, the **Controller 7000 Enhanced in October 2024**, and the **High Sec Controller 7000 in February 2025**. The C7000 is equipped with a powerful **iMX8 System-on-Chip** and maintains the **same footprint as the C6000**.

In April 2020 Gallagher announced extended Controller 6000 support from April 2027 until July 2031. **This notice announces that C6000 will not be supported after July 2031.**

In **March 2025 the Controller 6000 transitioned to 'Superseded' status.** A new product is available, but the C6000 can still be purchased for a limited time and still receives full technical support, with no new features added.

> **Note. Not affected by this obsolescence notice:** SMB Controller 6000; Type 1A products.

## Key dates

Gallagher will make commercially reasonable efforts to adhere to these dates.

| Date                  | Detail                                                                                      |
| --------------------- | ------------------------------------------------------------------------------------------- |
| March 2025            | C6000 moved to 'Superseded' status                                                          |
| July 2026             | Last manufacture of C6000                                                                   |
| July 2028             | 12-month notification of C6000 removal from Command Centre                                  |
| July 2029             | C6000 removed from Command Centre                                                           |
| July 2029 - July 2031 | C6000s still supported, but sites unable to upgrade Command Centre without replacing C6000s |
| July 2031             | No supported versions of Command Centre with C6000                                          |

## Upgrade options

Plan upgrades to the **Controller 7000 platform and Command Centre v9.0 or later**.

## Support through the change

* The **Hardware Warranty Report**, launching with Command Centre v9.30, shows the type and age of a site's controller hardware.
* The **C6000-to-C7000 upgrade tool** is available from v9.0.
* The Controller 6000 Obsolescence Toolkit includes the *Controller 7000 Lifecycle Upgrade Document* and the *C6000 Obsolescence FAQ document*.

Questions: contact your [local Gallagher representative](https://security.gallagher.com/Meet-the-Team).

***

🔗 **Related**

* [Controller 6000 extended support statement — April 2020](/knowledge-hub/products/product-advisories/historical-notices/controller-6000-extended-support-state.md). Review the earlier support commitment.
* [Controller 6000](/knowledge-hub/products/cc-hardware/controllers/controller-6000.md). Setup, faults, and reference for the controller.


---

# 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/products/product-advisories/current-advisories/controller-6000-superseded-status-and.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.