All Products
Search

This Product

    ApsaraDB for MongoDB:Migrate a self-managed standalone MongoDB database to ApsaraDB for MongoDB by using DTS

    Document Center

    ApsaraDB for MongoDB:Migrate a self-managed standalone MongoDB database to ApsaraDB for MongoDB by using DTS

    Last Updated:Sep 15, 2025

    This topic describes how to use Data Transmission Service (DTS) to migrate a self-managed MongoDB database with a standalone architecture to ApsaraDB for MongoDB.

    You can also use MongoDB tools to migrate your self-managed database to a standalone instance. For more information, see Migrate a self-managed database to a standalone instance using MongoDB tools.

    For more information about data migration or data synchronization solutions, see Data migration and synchronization.

    Preparations

    • For information about the versions supported by the self-managed MongoDB database and ApsaraDB for MongoDB, see Overview of migration solutions.

    • Ensure that the storage space of the ApsaraDB for MongoDB instance is at least 10% larger than the storage space occupied by the self-managed MongoDB database.

    Usage notes

    • By default, a self-managed MongoDB database with a standalone architecture does not support oplog. To perform an incremental migration using DTS, you must enable oplog by configuring the standalone instance as a single-node replica set.

    • To avoid affecting your services, migrate data during off-peak hours.

    • The config database is an internal system database. Do not migrate this database unless necessary.

    • For information about the versions and storage engines supported by ApsaraDB for MongoDB instances, see Versions and storage engines. To migrate data across versions or storage engines, check for compatibility in advance.

    • The admin and local databases cannot be used as the source or destination databases.

    • DTS writes data concurrently. As a result, the destination database may use 5% to 10% more storage space than the source database.

    • Ensure that the destination MongoDB instance does not contain documents with the same primary key (_id) as the source database. Otherwise, data loss may occur. If the destination instance has documents with the same primary key as the source, you must delete the conflicting documents from the destination instance before you start the migration.

    Billing

    Migration type

    Link Configuration Fees

    Data transfer cost

    Full data migration

    Free of charge

    You are charged when you transfer data out of Alibaba Cloud over the Internet. For more information, see Billing overview.

    Permissions required for database accounts

    Data Source Migration

    Full data migration

    Self-managed MongoDB database

    read permission on the database to be migrated

    ApsaraDB for MongoDB database

    readWrite permission on the destination database

    To create a database account and grant permissions:

    Procedure

    1. Use one of the following methods to go to the Data Migration page and select the region in which the data migration instance resides.

      DTS console

      1. Log on to the DTS console.

      2. In the left-side navigation pane, click Data Migration.

      3. In the upper-left corner of the page, select the region in which the data migration instance resides.

      DMS console

      Note

      The actual operation may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Customize the layout and style of the DMS console.

      1. Log on to the DMS console.

      2. In the top navigation bar, move the pointer over Data + AI > DTS (DTS) > Data Migration.

      3. From the drop-down list to the right of Data Migration Tasks, select the region in which the data synchronization instance resides.

    2. Click Create Task to go to the task configuration page.

    3. Configure the source and destination databases. The following table describes the parameters.

      Warning

      After you configure the source and destination databases, we recommend that you read the Limits that are displayed in the upper part of the page. Otherwise, the task may fail or data inconsistency may occur.

      Category

      Configuration

      Description

      N/A

      Task Name

      The name of the DTS task. DTS automatically generates a task name. We recommend that you specify an informative name that makes it easy to identify the task. You do not need to specify a unique task name.

      Source Database

      Select Existing Connection

      • If you use a database instance that is registered with DTS, select the instance from the drop-down list. DTS automatically populates the following database parameters for the instance. For more information, see Manage database connections.

        Note

        In the DMS console, you can select the database instance from the Select a DMS database instance drop-down list.

      • If you fail to register the instance with DTS, or you do not need to use the instance that is registered with DTS, you must configure the following database information.

      Database Type

      Select NoSQL Database > MongoDB.

      Access Method

      Select a type based on the deployment location of the source database. This topic uses Public IP Address as an example.

      Note

      If you select another connection type for the self-managed database, you must also perform the corresponding preparations.

      Instance Region

      Select the region where the self-managed MongoDB database is located.

      Note

      If the region of your self-managed MongoDB database is not listed, you can select the region that is geographically closest to it.

      Architecture

      Select Replica Set.

      Migration Method

      The method used to migrate incremental data from the source database. Select a method based on your business requirements. Valid values:

      • Oplog (recommended):

        This option is available if the oplog feature is enabled for the source database.

        Note

        By default, the oplog feature is enabled for both self-managed MongoDB databases and ApsaraDB for MongoDB instances. This feature allows you to migrate incremental data at a low latency because of a fast log pulling speed. Therefore, we recommended that you select Oplog for the Migration Method parameter.

      • ChangeStream: This option is available if change streams are enabled for the source database. For more information, see Change Streams.

        Note

        • If the source database is an inelastic Amazon DocumentDB cluster, you can set the Migration Method parameter only to ChangeStream.

        • If you select Sharded Cluster for the Architecture parameter, you do not need to configure the Shard account and Shard password parameters.

      Endpoint Type

      Select Standalone.

      Note

      This configuration item appears only when you connect to a self-managed MongoDB database using Express Connect, VPN Gateway, or Smart Access Gateway, Public IP Address, or Cloud Enterprise Network (CEN).

      Domain Name or IP

      Enter the domain name or IP address of the self-managed MongoDB database. In this example, enter the public IP address.

      Port Number

      Enter the service port of the self-managed MongoDB database.

      Authentication Database

      Enter the name of the database to which the database account belongs in the self-managed MongoDB. The default is admin if it has not been changed.

      Database Account

      Enter the account for the Mongos node of the self-managed MongoDB. For permission requirements, see Permissions required for database accounts.

      Note

      If the Access Method for the self-managed MongoDB is Self-managed Database on ECS or Database Gateway, enter the account for the shard node.

      Database Password

      The password that is used to access the database instance.

      Encryption

      Specifies whether to encrypt the connection to the source database. You can select Non-encrypted, SSL-encrypted, or Mongo Atlas SSL based on your business requirements. The options available for the Encryption parameter are determined by the values selected for the Access Method and Architecture parameters. The options displayed in the DTS console prevail.

      Note

      • If the Architecture parameter is set to Sharded Cluster, and the Migration Method parameter is set to Oplog for the ApsaraDB for MongoDB database, the Encryption parameter SSL-encrypted is unavailable.

      • If the source database is a self-managed MongoDB database that uses the Replica Set architecture, the Access Method parameter is not set to Alibaba Cloud Instance, and the Encryption parameter is set to SSL-encrypted, you can upload a certification authority (CA) certificate to verify the connection to the source database.

      Destination Database

      Select Existing Connection

      • If you use a database instance that is registered with DTS, select the instance from the drop-down list. DTS automatically populates the following database parameters for the instance. For more information, see Manage database connections.

        Note

        In the DMS console, you can select the database instance from the Select a DMS database instance drop-down list.

      • If you fail to register the instance with DTS, or you do not need to use the instance that is registered with DTS, you must configure the following database information.

      Database Type

      Select MongoDB.

      Access Method

      Select Alibaba Cloud Instance.

      Instance Region

      Select the region where the destination ApsaraDB for MongoDB instance is located.

      Replicate Data Across Alibaba Cloud Accounts

      In this example, a database instance of the current Alibaba Cloud account is used. Select No.

      Architecture

      Select the architecture type of the destination ApsaraDB for MongoDB instance.

      Instance ID

      Select the ID of the destination ApsaraDB for MongoDB instance.

      Authentication Database

      Enter the name of the database to which the database account of the destination ApsaraDB for MongoDB instance belongs. The default is admin if it has not been changed.

      Database Name

      Enter the name of the database to which the migration object belongs in the destination ApsaraDB for MongoDB instance.

      Database Account

      Enter the database account for the destination ApsaraDB for MongoDB instance. For permission requirements, see Permissions required for database accounts.

      Database Password

      The password that is used to access the database instance.

      Encryption

      Specifies whether to encrypt the connection to the destination database. You can select Non-encrypted, SSL-encrypted, or Mongo Atlas SSL based on your business requirements. The options available for the Encryption parameter are determined by the values selected for the Access Method and Architecture parameters. The options displayed in the DTS console prevail.

      Note

      • If the destination database is an ApsaraDB for MongoDB instance and the Architecture parameter is set to Sharded Cluster, the Encryption parameter SSL-encrypted is unavailable.

      • If the destination database is a self-managed MongoDB database that uses the Replica Set architecture, the Access Method parameter is not set to Alibaba Cloud Instance, and the Encryption parameter is set to SSL-encrypted, you can upload a CA certificate to verify the connection to the destination database.

    4. In the lower part of the page, click Test Connectivity and Proceed, and then click Test Connectivity in the CIDR Blocks of DTS Servers dialog box that appears.

      Note

      Make sure that the CIDR blocks of DTS servers can be automatically or manually added to the security settings of the source and destination databases to allow access from DTS servers. For more information, see Add the CIDR blocks of DTS servers.

    5. Configure the objects to be migrated.

      1. On the Configure Objects page, configure the objects that you want to migrate.

        Configuration

        Description

        Migration Types

        Select both Schema Migration and Full Data Migration.

        Processing Mode of Conflicting Tables

        • Precheck and Report Errors: checks whether the destination database contains collections that have the same names as collections in the source database. If the source and destination databases do not contain collections that have identical names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started.

          Note

          If the source and destination databases contain collections with identical names and the collections in the destination database cannot be deleted or renamed, you can use the object name mapping feature to rename the collections that are migrated to the destination database. For more information, see Map object names.

        • Ignore Errors and Proceed: skips the precheck for identical collection names in the source and destination databases.

          Warning

          If you select Ignore Errors and Proceed, data consistency is not ensured and your business may be exposed to potential risks.

          • DTS does not migrate data records that have the same primary keys as data records in the destination database.

          • Data may fail to be initialized, only specific columns are migrated, or the data migration task fails.

        Capitalization of Object Names in Destination Instance

        The capitalization of database names and collection names in the destination instance. By default, DTS default policy is selected. You can select another option to ensure that the capitalization of object names is the same as that of the source or destination database. For more information, see Specify the capitalization of object names in the destination instance.

        Source Objects

        Select one or more objects from the Source Objects section. Click the 向右小箭头 icon to add the objects to the Selected Objects section.

        Note

        You can select objects at the Database or Collection level.

        Selected Objects

        • To specify the name of an object to be migrated in the destination instance or specify the object to receive data in the destination instance, right-click the object in the Selected Objects section. For more information, see Map object names.

        • To remove one or more objects that are selected for migration, click the objects in the Selected Objects section and then click the image icon to move the objects to the Source Objects section.

        Note

        • To filter data based on conditions, right-click the collection to be migrated in the Selected Objects box and configure the settings in the dialog box that appears. For more information, see Set filter conditions.

        • If you use the object name mapping feature to specify a database or collection to receive data, other objects that depend on the mapped object may fail to migrate.

      2. Click Next: Advanced Settings to configure advanced settings.

        Configuration

        Description

        Dedicated Cluster for Task Scheduling

        By default, DTS schedules tasks on a shared cluster, so you do not need to make a selection. You can purchase a dedicated cluster with specific specifications to run DTS migration tasks. For more information, see What is a DTS dedicated cluster?.

        Retry Time for Failed Connections

        The retry time range for failed connections. If the source or destination database fails to be connected after the data migration task is started, DTS immediately retries a connection within the retry time range. Valid values: 10 to 1,440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS is reconnected to the source and destination databases within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails.

        Note

        • If you specify different retry time ranges for multiple data migration tasks that share the same source or destination database, the value that is specified later takes precedence.

        • When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at the earliest opportunity after the source database and destination instance are released.

        Retry Time for Other Issues

        The retry time range for other issues. For example, if DDL or DML operations fail to be performed after the data migration task is started, DTS immediately retries the operations within the retry time range. Valid values: 1 to 1440. Unit: minutes. Default value: 10. We recommend that you set the parameter to a value greater than 10. If the failed operations are successfully performed within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails.

        Important

        The value of the Retry Time for Other Issues parameter must be smaller than the value of the Retry Time for Failed Connections parameter.

        Enable Throttling for Full Data Migration

        Specifies whether to enable throttling for full data migration. During full data migration, DTS uses the read and write resources of the source and destination databases. This may increase the loads of the database servers. You can enable throttling for full data migration based on your business requirements. To configure throttling, you must configure the Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) parameters. This reduces the loads of the destination database server.

        Note

        You can configure this parameter only if you select Full Data Migration for the Migration Types parameter.

        Only one data type for primary key _id in a table of the data to be synchronized

        Specifies whether the data type of the primary key _id is unique in a collection to be migrated.

        Important

        • Enable this parameter based on your business requirements. Otherwise, data loss may occur.

        • This parameter is required only if you select Full Data Migration for the Migration Types parameter.

        Valid values:

        • Yes: The data type is unique. During full migration, DTS does not scan the data type of the primary key in source database. DTS only migrates a data type of the primary key in a collection to be migrated.

        • No: The data type is not unique. During full migration, DTS scans the data types of the primary key in source database and migrates the data of all data types.

        Environment Tag

        You can select an environment tag to identify the instance based on your needs. No selection is needed for this example.

        Configure ETL

        Specifies whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values:

        Monitoring and Alerting

        Specifies whether to configure alerting for the data migration task. If the task fails or the migration latency exceeds the specified threshold, the alert contacts receive notifications. Valid values:

      3. Click Next Step: Data Verification to configure the data verification task.

        For more information about how to use the data verification feature, see Configure a data verification task.

    6. Save the task settings and run a precheck.

      • To view the parameters to be specified when you call the relevant API operation to configure the DTS task, move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters.

      • If you do not need to view or have viewed the parameters, click Next: Save Task Settings and Precheck in the lower part of the page.

      Note

      • Before you can start the data migration task, DTS performs a precheck. You can start the data migration task only after the task passes the precheck.

      • If the task fails to pass the precheck, click View Details next to each failed item. After you analyze the causes based on the check results, troubleshoot the issues. Then, run a precheck again.

      • If an alert is triggered for an item during the precheck:

        • If an alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issues. Then, run a precheck again.

        • If the alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur, and your business may be exposed to potential risks.

    7. Purchase the instance.

      1. Wait until Success Rate becomes 100%. Then, click Next: Purchase Instance.

      2. On the Purchase Instance page, configure the Instance Class parameter for the data migration instance. The following table describes the parameters.

        Section

        Parameter

        Description

        New Instance Class

        Resource Group

        The resource group to which the data migration instance belongs. Default value: default resource group. For more information, see What is Resource Management?

        Instance Class

        DTS provides instance classes that vary in the migration speed. You can select an instance class based on your business scenario. For more information, see Instance classes of data migration instances.

      3. Read and agree to Data Transmission Service (Pay-as-you-go) Service Terms by selecting the check box.

      4. Click Purchase And Start, and in the OK dialog box, click OK.

        You can view the progress of the migration instance on the Data Migration Tasks page.