[Yandex Cloud documentation](../../../../index.md) > [Yandex Data Transfer](../../../index.md) > [Step-by-step guides](../../index.md) > [Configuring endpoints](../index.md) > Elasticsearch > Source

# Transferring data from an Elasticsearch source endpoint


Yandex Data Transfer enables you to migrate search and analytics data from an Elasticsearch database and implement various data transfer, processing, and transformation scenarios. To implement a transfer:

1. [Explore possible data transfer scenarios](#scenarios).
1. [Prepare the Elasticsearch](#prepare) database for the transfer.
1. [Set up a source endpoint](#endpoint-settings) in Yandex Data Transfer.
1. [Set up one of the supported data targets](#supported-targets).
1. [Create](../../transfer.md#create) a transfer and [start](../../transfer.md#activate) it.
1. Perform required operations with the database and [control the transfer](../../monitoring.md).
1. In case of any issues, [use ready-made solutions](#troubleshooting) to resolve them.

## Scenarios for transferring data from Elasticsearch {#scenarios}

Migration: Moving data from one storage to another. Migration often means migrating a database from obsolete local databases to managed cloud ones.

* [Migration with the storage type changed from Elasticsearch to OpenSearch](../../../tutorials/mes-to-mos.md)

For a detailed description of possible Yandex Data Transfer scenarios, see [Tutorials](../../../tutorials/index.md).

## Preparing the source database {#prepare}

{% note info %}

Elasticsearch versions lower than 7.x are not supported.

{% endnote %}

If not planning to use [Cloud Interconnect](../../../../interconnect/concepts/index.md) or [VPN](https://en.wikipedia.org/wiki/Virtual_private_network) for connections to an external cluster, make such cluster accessible from the Internet from [IP addresses used by Data Transfer](../../../../overview/concepts/public-ips.md#virtual-private-cloud).

For details on linking your network up with external resources, see [this concept](../../../concepts/network.md#source-external).

## Configuring the Elasticsearch source endpoint {#endpoint-settings}

When [creating](../index.md#create) or [updating](../index.md#update) an endpoint, you can define:

* [Custom installation](#on-premise) connection settings. These are required parameters.
* [Additional parameters](#additional-settings).

### Custom installation {#on-premise}

Connection to nodes with explicitly specified network addresses and ports.

{% list tabs group=instructions %}

- Management console {#console}

    * **Data nodes**: Click ![image](../../../../_assets/console-icons/plus.svg) to add a new data node. For each node, specify:

    * **Host**: IP address or FQDN of the host with the `DATA` role you need to connect to.

    * **Port**: Port number Data Transfer will use to connect to the host with the `DATA` role.

    * **SSL**: Select this option if a secure SSL connection is used.

    * **CA certificate**: Upload the certificate file or add its contents as text if data encryption is required, e.g., to comply with the PCI DSS requirements.

    * **Subnet ID**: Select or [create](../../../../vpc/operations/subnet-create.md) a subnet in the required [availability zone](../../../../overview/concepts/geo-scope.md).
      If this field has a value specified for both endpoints, both subnets must be hosted in the same availability zone.

   * **User**: Specify the username Data Transfer will use to connect to the cluster.

   * **Password**: Enter the user password to the cluster.

   * **Security groups**: Select the cloud network to host the endpoint and security groups for network traffic.

     Thus, you will be able to apply the specified security group rules to the VMs and clusters in the selected network without changing the settings of these VMs and clusters. For more information, see [Networking in Yandex Data Transfer](../../../concepts/network.md).

{% endlist %}

### Additional settings {#additional-settings}

{% list tabs group=instructions %}

- Management console {#console}

    * **Dump an index with type mapping**: Select this option to move data types from a source to a target before a transfer is started. If the option is disabled and no index schema is set on the target, data types on the target will be identified automatically during a transfer.

    {% note warning %}
    
    If a source index includes data types that are not supported on the target, enabling this option may cause a transfer run error. In this case, disable the option and create an index schema on the target manually.
    
    {% endnote %}

{% endlist %}


## Configuring the data target {#supported-targets}

Configure the target endpoint:

* [OpenSearch](../target/opensearch.md)
* [ClickHouse®](../target/clickhouse.md)
* [Greenplum®](../target/greenplum.md)
* [Yandex Managed Service for YDB](../target/yandex-database.md)
* [Yandex Object Storage](../target/object-storage.md)
* [Apache Kafka®](../target/kafka.md)
* [YDS](../target/data-streams.md)

For a complete list of supported sources and targets in Yandex Data Transfer, see [Available transfers](../../../transfer-matrix.md).

After configuring the data source and target, [create and start the transfer](../../transfer.md#create).