> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/feature-guides/pipeline-intelligence/migrate-configurations.md).

# Migrate Configurations

Pipeline Intelligence can convert existing configurations from several vendors into Bindplane configurations. You can provide your current configuration file, run the Pipeline Intelligence analysis, review the compatible resources, and create a configuration.

<figure><img src="/files/RNukyu99hjihWPzGVphl" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/HRU1ZmqkZRwedGoFc8mV" alt=""><figcaption></figcaption></figure>

## OpenTelemetry

Pipeline Intelligence will analyze an OpenTelemetry configuration and return compatible sources, processors, and destinations. Resources that are available in your available components but not as a Bindplane resource will be shown as a custom resource.

{% hint style="info" %}
The OpenTelemetry migrator is only available for Enterprise, Bindplane Enterprise (Google Edition), and Honeycomb licenses.
{% endhint %}

## Chronicle Forwarder

Pipeline Intelligence maps all Chronicle Forwarder collector types (Splunk, syslog, file, packet capture, Kafka, and web proxy) into Bindplane sources, adds processors for standardization, and creates a Google SecOps destination.

Syslog collectors map to separate TCP and/or UDP sources, preserving their port settings. The web proxy and PCAP collector types automatically translate to OS-appropriate capture methods: npcap on Windows and libpcap (via tcpdump) on Linux. Tcpdump is typically preinstalled, but the collector host must have it available. [See PCAP source prerequisites for details.](https://docs.bindplane.com/integrations/sources/packet-capture#prerequisites) Kafka collectors translate to the Kafka stream source with their corresponding broker configuration.

Bindplane supports both Chronicle Forwarder configuration formats:

* **Two-file configuration** (more common): Upload the main configuration file containing your collectors plus the separate authentication file containing credentials and TLS settings.
* **Single-file configuration**: Upload your combined configuration file in the first field and leave the second field blank.

For instructions on how to download your Chronicle Forwarder configuration files, [see here](https://docs.cloud.google.com/chronicle/docs/install/forwarder-management-configurations#download_configuration_files).

For more information about migrating from the legacy Chronicle Forwarder, [see here](https://docs.bindplane.com/how-to-guides/partner-integrations/google-secops/migrating-from-the-deprecated-google-chronicle-forwarder).

## Splunk Universal Forwarder

Pipeline Intelligence will map several Splunk inputs – Monitor, Windows Event Log Monitor, TCP, UDP, Batch – into Bindplane sources. Pipeline Intelligence will map HTTP outputs into corresponding Splunk HEC destinations.


---

# 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.bindplane.com/feature-guides/pipeline-intelligence/migrate-configurations.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.