Docs

Data Migration Service

Product Overview

DMS evolution roadmap

As business grows, the amount of data migrated to object storage continues to increase, raising higher requirements for migration services in terms of supported protocols and migration speed. To meet these needs, DMS has introduced the DMS 2.0 architecture. DMS 2.0 builds on 1.0 by further enriching source storage protocol support and enabling local file migration to object storage TOS. This article introduces the DMS evolution roadmap and compares the features of DMS 1.0 and DMS 2.0.

Evolution roadmap

Based on version 1.0, DMS 2.0 first supports semi-managed local file migration, and will continue to adapt to more source storage protocols, optimize bandwidth-adaptive migration capabilities, and further improve the service capabilities of DMS 1.0 until it fully replaces the previous version.

Feature comparison

Compared to DMS 1.0, DMS 2.0 offers extensive protocol support, adapts to more complex network environments, and provides greater flexibility and scalability.

Feature	DMS 1.0	DMS 2.0 semi-managed mode
Source protocol	S3, HTTP.	Currently supports LocalFS and S3. Additional data source protocols, including HTTP, NFS, HDFS, and FTP, will be supported in future updates.
Network environment	Retrieves data from the source over the public network and dedicated line.	Supports data retrieval from the source over the public network, private network, and dedicated line.
Resource elasticity	Limited adjustment capabilities; resource allocation is managed centrally by the backend. To request adjustments, you need to submit a ticket to contact technical support.	Highly adaptable, supports dynamic scaling by adding Agents flexibly, enables on-demand capacity expansion or reduction, and migration tasks can leverage bandwidth quota-based adaptive capabilities.
Ease of use	Each task requires entering both source and destination addresses, and different migration tasks cannot reuse this information.	Allows separate configuration of source and destination addresses, which can be flexibly reused across multiple migration tasks to streamline the setup process.

Last updated: 2026.02.02 11:05:22