# US 2026/0064458 A1 · Systems and methods for upgrading controllers of a building management system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2026/0064458 A1 - Document ID: US20260064458A1 - Status: Published application - Kind: A1 - Application number: 19/299,995 - Filed: 2025-08-14 - Published: 2026-03-05 - Earliest claimed: 2024-08-28 - Assignees: Honeywell International Inc. - Applicants: Honeywell International Inc. - Inventors: Graham Lewry; Shyamsundhar Madhusudhan; Weilin Zhang; Yi Sun - Web page: https://patentgrep.com/patent/US20260064458A1 ## CPC - G06F 9/4856: {resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence)} - G06F 9/44526: {Plug-ins; Add-ons} - G06F 9/453: {Help systems} - G06F 2209/482: Application - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A source controller running a control application that includes a plurality of control application components may be migrated to a target controller of a BMS system. The source controller may be selected and the plurality of control application components running on the source controller may be detected. A selection of the target controller and one or more of the control application components may be selected to migrate to the selected target controller. An application component migration strategy is assembled for each of the selected control application components that identifies a migration plugin from a migration plugin library for migrating the respective control application component from the selected source controller to the selected target controller. Each of the selected control application components are migrated from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy. ## Claims ### Claim 1 A method for migrating a source controller to a target controller of a BMS system, wherein the source controller runs a control application that includes a plurality of control application components, the method comprising: receiving a selection of the source controller; detecting the plurality of control application components running on the source controller; receiving a selection of the target controller; receiving a selection of one or more of the control application components running on the source controller to migrate to the selected target controller; assembling an application component migration strategy for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration plugin from a plurality of predefined migration plugins of a migration plugin library for migrating the respective control application component from the selected source controller to the selected target controller; and migrating each of the selected control application components running on the selected source controller from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy. ### Claim 2 (depends on 1) The method of claim 1, wherein one or more of the plurality of control application components is configured by one or more configuration settings, the method comprising: collecting configuration settings associated with each of the control application components running on the source controller; and wherein migrating each of the selected control application components from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy includes migrating the configuration settings associated with the respective control application component. ### Claim 3 (depends on 1) The method of claim 1, wherein one or more of the plurality of control application components collects and stores respective support data and/or log information, the method comprising: collecting support data and/or log information associated with each of the control application components running on the source controller; and wherein migrating each of the selected control application components from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy includes migrating the support data and/or log information associated with the respective control application component. ### Claim 4 (depends on 3) The method of claim 3, wherein the support data and/or log information includes one or more of current and/or historical data. ### Claim 5 (depends on 4) The method of claim 4, wherein the support data and/or log information includes one or more of alarm data and sensor data. ### Claim 6 (depends on 1) The method of claim 1, where assembling the application component migration strategy for each of the selected control application components running on the selected source controller comprises: extracting the application component migration strategy for each of the selected control application components from a master component migration strategy source. ### Claim 7 (depends on 1) The method of claim 1, wherein extracting the application component migration strategy comprises parsing the master component migration strategy source to include one or more parts of the master component migration strategy source based at least in part on one or more of: the selected control application component; the selected source controller; and the selected target controller. ### Claim 8 (depends on 7) The method of claim 7, wherein the selected control application component running on the selected source controller has a first version, and the selected control application component to be migrated to the selected target controller has a second version that is different from the first version, wherein parsing the master component migration strategy source to include one or more parts of the master component migration strategy source is based at least in part on the first version of the selected control application component running on the selected source controller and the second version of the selected control application component to be migrated to the selected target controller. ### Claim 9 (depends on 1) The method of claim 1, wherein each of the selected one or more of the control application components running on the source controller include one or more control points, the method comprising: receiving a selection of one or more additional points to add to a selected one of the control application component that are to be migrated to the selected target controller; and adding the selected one or more additional points to the selected control application component during the migration of the selected control application component from the selected source controller to the selected target controller. ### Claim 10 (depends on 1) The method of claim 1, wherein each of the selected one or more of the control application components running on the source controller include one or more control points, wherein each of the one or more control points are mapped to a corresponding terminal of the source controller, the method comprising: receiving a mapping of one or more of the control points of a selected one of the control application components to a selected terminal of the target controller. ### Claim 11 (depends on 1) The method of claim 1, wherein the application component migration strategy for each of the selected control application components running on the selected source controller includes a human readable description of one or more steps of the migration of the respective control application component from the selected source controller to the selected target controller. ### Claim 12 (depends on 11) The method of claim 11, wherein the migration plugin identified by the respective application component migration strategy automatically performs one or more of the steps of the migration of the respective control application component from the selected source controller to the selected target controller. ### Claim 13 (depends on 12) The method of claim 12, wherein one or more of the steps that are automatically performed by the migration plugin include one or more of: migrating one or more configuration settings from the selected source controller to the selected target controller; migrating support data and/or log information from the selected source controller to the selected target controller; migrating schedule information from the selected source controller to the selected target controller; and migrating one or more Fast Access List (FAL) entries from the selected source controller to the selected target controller. ### Claim 14 (depends on 1) The method of claim 1, comprising: determining one or more components running on the source controller that have an upgrade available; and providing one or more component upgrade suggestions to a user via a user interface. ### Claim 15 A migration tool for migrating a source controller to a target controller of a Building Management System (BMS), wherein the source controller runs a control application that includes a plurality of control application components, the migration tool comprising: an input/output for communicating with the source controller and the target controller; a user interface; a controller operatively coupled to the input/output and the user interface, the controller of the migration tool is configured to: receive a selection via the user interface of the source controller; receive via the input/output an identification of the plurality of control application components running on the source controller; receive via the user interface a selection of the target controller; receive via the user interface a selection of one or more of the control application components running on the source controller to migrate to the selected target controller; assemble an application component migration strategy for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration plugin from a plurality of predefined migration plugins of a migration plugin library for migrating the respective control application component from the selected source controller to the selected target controller; and migrate each of the selected control application components running on the selected source controller from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy. ### Claim 16 (depends on 15) The migration tool of claim 15, wherein one or more of the plurality of control application components is configured by one or more configuration settings, and wherein the controller of the migration tool is configured to: collect configuration settings associated with each of the control application components running on the source controller via the input/output; and wherein migrating each of the selected control application components from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy includes migrating the configuration settings associated with the respective control application component. ### Claim 17 (depends on 15) The migration tool of claim 15, wherein one or more of the plurality of control application components collects and stores respective support data and/or log information, and wherein the controller of the migration tool is configured to: collect support data and/or log information associated with each of the control application components running on the source controller; and wherein migrating each of the selected control application components from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy includes migrating the support data and/or log information associated with the respective control application component. ### Claim 18 (depends on 15) The migration tool of claim 15, wherein the controller is configured to migrate each of the selected control application components running on the selected source controller from the selected source controller to the selected target controller using the respective migration plugin identified in the respective application component migration strategy without interrupting the operation of the Building Management System (BMS). ### Claim 19 A non-transitory computer readable medium storing instructions that when executed by one or more processors cause the one or more processors to: receive a selection via a user interface of a source controller of a Building Management System (BMS); receive an identification of one or more control application components running on the source controller; receive a selection of a target controller; receive a selection of one or more of the control application components running on the source controller to migrate to the selected target controller; assemble an application component migration strategy for each of the selected control application components running on the selected source controller, wherein the respective application component migration strategy identifies a migration process for migrating the respective control application component from the selected source controller to the selected target controller; and migrate each of the selected control application components running on the selected source controller from the selected source controller to the selected target controller in compliance with the respective application component migration strategy. ### Claim 20 (depends on 19) The non-transitory computer readable medium of claim 19, wherein the instructions cause the one or more processors to: collect configuration settings associated with each of the control application components running on the source controller; migrate the configuration settings associated with the respective control application component from the selected source controller to the selected target controller; collecting support data and/or log information associated with each of the control application components running on the source controller; and migrate the support data and/or log information associated with the respective control application component from the selected source controller to the selected target controller.