All Products
Search

This Product

    :One-click migration from HoloStudio to DataStudio

    Document Center

    :One-click migration from HoloStudio to DataStudio

    Last Updated:Jun 20, 2026

    To provide a consistent and unified development experience, we are consolidating the capabilities of HoloStudio into DataStudio. You can then use DataStudio to continue your data development for Hologres. Within a specified timeframe, you can manually migrate your existing files from HoloStudio to DataStudio by following the instructions in this article. After this period, the system automatically migrates your assets, and HoloStudio will be retired. For the detailed timeline, see DataWorks HoloStudio Retirement Announcement.

    Migration plan

    HoloStudio has three core features: SQL Console, PG management, and Data Development. This section describes the migration plan for these features.

    1. SQL Console migration

      Your files and directory structure from the HoloStudio SQL Console will be migrated to DataStudio > Ad Hoc Query based on the default migration policy.

      Migration policy: The migration process creates a new folder named HoloStudioMigration in the Ad Hoc Query feature of DataStudio. It moves all folders and files from your SQL Console into this folder, preserving their original names.

    2. PG management

      The Workspace Tables feature in DataStudio replaces the PG management feature in HoloStudio. However, Workspace Tables sources its Hologres metadata from the Data Map metadata collector. You must configure the metadata collector in Data Map. For more information, see metadata collection.

    3. Data Development migration

      Assets from the Data Development module in HoloStudio, including directories and files, are migrated to a scheduled workflow in the DataStudio Data Development module according to the default migration policy. For more information about scheduled workflows, see Create a workflow.

      Migration policy:

      1. Scheduled tasks in HoloStudio Data Development are not migrated. For unscheduled tasks, the entire workflow is migrated to DataStudio Data Development.

      2. To prevent naming conflicts during the migration, the migration process appends a suffix to the name of each migrated task. The default suffix is _HoloStudioMigration. You can change this suffix during a manual migration.

    4. Hologres Development node upgrade

      Hologres Development nodes in DataStudio are upgraded to HologresSQL nodes and moved from the custom directory to the Hologres/Data Development directory. You can then develop directly in DataStudio without associating them with HoloStudio nodes.

    Manual migration

    Note

    Before starting the manual migration, ensure you have created a Hologres data source in your workspace and bound it to Data Development. For information about the timeline for manual migration, see Key Dates.

    1. Log on to the DataWorks console. In the target region, click Data Development and O&M > Data Development in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.

    2. Go to the HoloStudio one-click migration page.

      1. Click the image.png icon in the top menu bar and choose All Products > Data Development & Operations > HoloStudio.

      2. In the left-side navigation pane of the HoloStudio page, click One-click Migration to DataStudio.

      3. On the One-click Migration from HoloStudio page, click Start Migration in the upper-right corner.

        After the migration starts, the page displays its progress and results. Once the migration is complete, you can no longer edit or create files in HoloStudio and must use DataStudio for all subsequent development.