> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-4-2/guides/migration.md).

# Migration

These guides show you how to move an existing connectivity configuration from another industrial connectivity product to Connectware. Each guide follows the same pattern: export the existing configuration, translate it into a [service commissioning file](/2-4-2/data-flows/service-commissioning-files.md) with the help of an AI assistant, review the result, and verify the data in Connectware.

The following guides are available:

| Guide                                                                                                           | Description                                                                                                            |
| --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| [Migrating from Kepware KEPServerEX](/2-4-2/guides/migration/migrating-from-kepware-kepserverex.md)             | Export a KEPServerEX project as JSON and translate channels, devices, and tags into a Connectware service.             |
| [Migrating from Ignition](/2-4-2/guides/migration/migrating-from-ignition.md)                                   | Export Ignition tags as JSON and translate device connections and tags into a Connectware service.                     |
| [Migrating from HighByte Intelligence Hub](/2-4-2/guides/migration/migrating-from-highbyte-intelligence-hub.md) | Export the Intelligence Hub project as JSON and translate connections, inputs, and outputs into a Connectware service. |
| [Migrating from Litmus Edge](/2-4-2/guides/migration/migrating-from-litmus-edge.md)                             | Export DeviceHub tags as CSV and devices as a template, and translate them into a Connectware service.                 |
| [Migrating from HiveMQ Edge](/2-4-2/guides/migration/migrating-from-hivemq-edge.md)                             | Read protocol adapters from config.xml or the REST API and translate them into a Connectware service.                  |
| [Migrating from Node-RED](/2-4-2/guides/migration/migrating-from-node-red.md)                                   | Export flows as JSON and translate the connectivity portion into a Connectware service.                                |
| [Migrating from EMQX Neuron](/2-4-2/guides/migration/migrating-from-emqx-neuron.md)                             | Export southbound drivers, groups, and tags as JSON and translate them into a Connectware service.                     |
| [Migrating from United Manufacturing Hub](/2-4-2/guides/migration/migrating-from-united-manufacturing-hub.md)   | Extract protocol converter YAML from UMH Core or Classic and translate it into a Connectware service.                  |
| [Migrating from OPC Router](/2-4-2/guides/migration/migrating-from-opc-router.md)                               | Export the project, extract the configuration XML, and translate plug-ins and flows into a Connectware service.        |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybus.io/2-4-2/guides/migration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.