Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Tutorials
    • All tutorials
      • Adding data to a ClickHouse® DB
      • Fetching data from Managed Service for Apache Kafka® to Managed Service for ClickHouse®
      • Fetching data from Managed Service for Apache Kafka® to ksqlDB
      • Fetching data from RabbitMQ to Managed Service for ClickHouse®
      • Migrating data to Managed Service for ClickHouse® using ClickHouse®
      • Migrating data to Managed Service for ClickHouse® using Data Transfer
      • Migrating databases from Google BigQuery to Managed Service for ClickHouse®
      • Migrating data from Managed Service for OpenSearch to Managed Service for ClickHouse® with a storage change using Data Transfer
      • Delivering data from Managed Service for MySQL® to Managed Service for ClickHouse® using Data Transfer
      • Exchanging data between Managed Service for ClickHouse® and Yandex Data Processing
      • Configuring Managed Service for ClickHouse® for Graphite
      • Saving a data stream from Data Streams to Managed Service for ClickHouse®
      • Asynchronously replicating data from PostgreSQL to ClickHouse®
      • Asynchronous replication of data from Yandex Metrica to ClickHouse® using Data Transfer
      • Using hybrid storage in Managed Service for ClickHouse®
      • Sharding Managed Service for ClickHouse® tables
      • Executing analytical queries in Managed Service for PostgreSQL with processing in Managed Service for ClickHouse®
      • Loading data from Yandex Direct to a Managed Service for ClickHouse® data mart using Cloud Functions, Object Storage, and Data Transfer
      • Loading data from Object Storage to Managed Service for ClickHouse® using Data Transfer
      • Loading data from Managed Service for YDB to Managed Service for ClickHouse® using Data Transfer
      • Yandex Managed Service for ClickHouse® integration with Microsoft SQL Server via ClickHouse® JDBC Bridge
      • Yandex Managed Service for ClickHouse® integration with Oracle via ClickHouse® JDBC Bridge

In this article:

  • Getting started
  • Required paid resources
  • Set up your infrastructure
  • Prepare your test data
  • Prepare and activate your transfer
  • Test the transfer
  • Delete the resources you created
  1. Building a data platform
  2. ClickHouse®
  3. Migrating data from Managed Service for OpenSearch to Managed Service for ClickHouse® with a storage change using Data Transfer

Copying data from Managed Service for OpenSearch to Managed Service for ClickHouse® using Yandex Data Transfer

Written by
Yandex Cloud
Updated at November 12, 2026
View in Markdown
  • Getting started
    • Required paid resources
  • Set up your infrastructure
  • Prepare your test data
  • Prepare and activate your transfer
  • Test the transfer
  • Delete the resources you created

Data Transfer enables you to transfer data from a Managed Service for OpenSearch source cluster to Managed Service for ClickHouse®.

To transfer data:

  1. Set up your infrastructure.
  2. Prepare your test data.
  3. Prepare and activate the transfer.
  4. Test the transfer.

If you no longer need the resources you created, delete them.

Getting startedGetting started

Sign up for Yandex Cloud and create a billing account:

  1. Navigate to the management console and log in to Yandex Cloud or create a new account.
  2. On the Yandex Cloud Billing page, make sure you have a billing account linked and it has the ACTIVE or TRIAL_ACTIVE status. If you do not have a billing account, create one and link a cloud to it.

If you have an active billing account, you can create or select a folder for your infrastructure on the cloud page.

Learn more about clouds and folders here.

Required paid resourcesRequired paid resources

  • Managed Service for OpenSearch cluster: use of computing resources, storage and backup size (see Managed Service for OpenSearch pricing).
  • Managed Service for ClickHouse® cluster: use of computing resources allocated to hosts, storage and backup size (see Managed Service for ClickHouse® pricing).
  • Public IP addresses if public access is enabled for cluster hosts (see Yandex Virtual Private Cloud pricing).

Set up your infrastructureSet up your infrastructure

Manually
Terraform

Note

Public access to cluster hosts is required if you plan to connect to the cluster via the internet. This connection option is simpler and is recommended for the purposes of this guide. You can connect to non-public hosts as well but only from Yandex Cloud virtual machines located in the same cloud network as the cluster.

  1. Create a Managed Service for OpenSearch source cluster using any suitable configuration with publicly accessible hosts.

  2. In the same availability zone, create a Managed Service for ClickHouse® target cluster with any suitable configuration and publicly accessible hosts.

    To connect to the cluster via Yandex WebSQL, enable WebSQL access in the cluster settings.

  3. Obtain an SSL certificate required to connect to the Managed Service for OpenSearch cluster.

  4. Make sure the Managed Service for OpenSearch and Managed Service for ClickHouse® cluster security groups allow connecting from the internet.

  1. If you do not have Terraform yet, install it.

  2. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

  3. Configure and initialize a provider. Instead of manually creating the provider configuration file, you can download it.

  4. Place the configuration file in a separate working directory and specify the parameter values. If you have not added the authentication credentials to environment variables, specify them in the configuration file.

  5. Download the opensearch-to-clickhouse.tf configuration file to your current working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group and rules allowing connections to the Managed Service for OpenSearch and Managed Service for ClickHouse® clusters.
    • Managed Service for OpenSearch source cluster and its admin account.
    • Managed Service for ClickHouse® target cluster, its user account, and a database.
    • Target endpoint.
    • Transfer.
  6. In opensearch-to-clickhouse.tf, specify the following settings:

    • source_admin_password: Managed Service for OpenSearch cluster admin password.

    • mos_version: OpenSearch version.

    • mch_db_name: Managed Service for ClickHouse® cluster database name.

    • mch_username: Managed Service for ClickHouse® cluster user name.

    • mch_user_password: Managed Service for ClickHouse® cluster user password.

    • source_endpoint_id: Source endpoint ID.

    • profile_name: Name of your CLI profile.

      If you do not have the Yandex Cloud CLI yet, install and initialize it.

  7. Validate your Terraform configuration using this command:

    terraform validate
    

    Terraform will display any configuration errors detected in your files.

  8. Create the required infrastructure:

    1. Run this command to view the intended changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Prepare your test dataPrepare your test data

  1. In the source cluster, create a test index named people and define its schema:

    curl --cacert ~/.opensearch/root.crt \
         --user <user_name_in_source_cluster>:<user_password_in_source_cluster> \
         --header 'Content-Type: application/json' \
         --request PUT 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people' && \
    curl --cacert ~/.opensearch/root.crt \
         --user <user_name_in_source_cluster>:<user_password_in_source_cluster> \
         --header 'Content-Type: application/json' \
         --request PUT 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_mapping?pretty' \
         --data'
         {
               "properties": {
                  "name": {"type": "text"},
                  "age": {"type": "integer"}
               }
         }
         '
    
  2. Populate the test index with data:

    curl --cacert ~/.opensearch/root.crt \
         --user <user_name_in_source_cluster>:<user_password_in_source_cluster> \
         --header 'Content-Type: application/json' \
         --request POST 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_doc/?pretty' \
         --data'
         {
               "name": "Alice",
               "age": "30"
         }
         ' && \
    curl --cacert ~/.opensearch/root.crt \
         --user <user_name_in_source_cluster>:<user_password_in_source_cluster> \
         --header 'Content-Type: application/json' \
         --request POST 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_doc/?pretty' \
         --data'
         {
               "name": "Robert",
               "age": "32"
         }
         '
    
  3. Optionally, check the data in the test index:

    curl --cacert ~/.opensearch/root.crt \
         --user <user_name_in_target_cluster>:<user_password_in_target_cluster> \
         --header 'Content-Type: application/json' \
         --request GET 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_search?pretty'
    

Prepare and activate your transferPrepare and activate your transfer

  1. Create a source endpoint for your pre-configured Managed Service for OpenSearch cluster using the following settings:

    • Database type: OpenSearch.
    • Connection settings:
      • Connection type: Managed Service for OpenSearch cluster.
      • Managed Service for OpenSearch cluster: Select your Managed Service for OpenSearch cluster from the list.
      • User: admin.
      • Password: admin password.
  2. Create a target endpoint and set up the transfer:

    Manually
    Terraform
    1. Create a target endpoint:

      • Database type: ClickHouse.
      • Endpoint parameters:
        • Connection type: Select Managed cluster.
        • Managed cluster: Select the Managed Service for ClickHouse® cluster from the list.
        • User: Enter the Managed Service for ClickHouse® cluster user name.
        • Password: Enter the Managed Service for ClickHouse® cluster user password.
        • Database: Enter the Managed Service for ClickHouse® cluster database name.
    2. Create a transfer of the Snapshot type that will use the endpoints you created.

    3. Activate the transfer.

    1. In opensearch-to-clickhouse.tf, specify the following settings:

      • source_endpoint_id: Source endpoint ID.
      • transfer_enabled: Set to 1 to create a target endpoint and a transfer.
    2. Validate your Terraform configuration using this command:

      terraform validate
      

      Terraform will display any configuration errors detected in your files.

    3. Create the required infrastructure:

      1. Run this command to view the intended changes:

        terraform plan
        

        If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

      2. If everything looks correct, apply the changes:

        1. Run this command:

          terraform apply
          
        2. Confirm updating the resources.

        3. Wait for the operation to complete.

      Once created, the transfer becomes active automatically.

Test the transferTest the transfer

  1. Wait for the transfer status to change to Completed.

  2. Make sure the Managed Service for ClickHouse® database now contains the data from the Managed Service for OpenSearch source cluster:

    Yandex WebSQL
    CLI
    1. Create a connection to the database in the Managed Service for ClickHouse® cluster.

    2. Check that the database contains the people table populated with test data by running this query:

      SELECT * FROM people;
      
    1. Obtain an SSL certificate required to connect to the Managed Service for ClickHouse® cluster.

    2. If you do not have clickhouse-client, install it.

    3. Connect to the database in the Managed Service for ClickHouse® cluster.

    4. Check that the database contains the people table populated with test data:

      SELECT * FROM people;
      

Delete the resources you createdDelete the resources you created

To reduce resource usage, delete the resources you no longer need:

  1. Delete the source endpoint.

  2. Delete other resources, applying the same method used for their creation:

    Manually
    Terraform
    1. Delete the transfer.

    2. Delete the target endpoint.

    3. Delete the Managed Service for OpenSearch cluster.

    4. Delete the Managed Service for ClickHouse® cluster.

      Yandex WebSQL will automatically delete the database connection in the Managed Service for ClickHouse® cluster.

    5. Delete the subnet.

    6. Delete the network.

    1. In the terminal window, go to the directory containing the infrastructure plan.

      Warning

      Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

    2. Delete resources:

      1. Run this command:

        terraform destroy
        
      2. Confirm deleting the resources and wait for the operation to complete.

      All the resources described in the Terraform manifests will be deleted.

ClickHouse® is a registered trademark of ClickHouse, Inc.

Was the article helpful?

Previous
Migrating databases from Google BigQuery to Managed Service for ClickHouse®
Next
Delivering data from Managed Service for MySQL® to Managed Service for ClickHouse® using Data Transfer
© 2026 Direct Cursus Technology L.L.C.