Migrating RND 3.0 Configurations Data to the RND 4.0 Database

You can move the RND 3.0 configurations data to the RND 4.0 database. For RND 3.0, you must export the RND 3.0 configurations data by running certain commands from the console. The commands to export configuration data from RND 3.0 MongoDB to the RND 4.0 PostgreSQL database vary depending on the build version. The exported RND 3.0 configurations data file must be copied to the local machine. This file can be uploaded later to RND 4.0 using the import option available in the Admin portal user interface. For RND 3.5 configuration data, you can download the Config Backup feature on the RND 3.5 platform, and upload downloaded configuration data to RND 4.0 directly.

In this section:

  1. Exporting Configuration Data from RND 3.0.40 and Later Builds to RND 4.0
    To export configuration data from RND 3.0.40 and later builds and copy the file to the local machine, complete the following steps.
  2. Exporting Configuration Data from RND 3.0.39 and Previous Builds to RND 4.0
    To export configuration data from RND 3.0.39 and previous builds and copy the file to the local machine, complete the following steps.
  3. Exporting Configuration Data from RND 3.5 and Later Builds to RND 4.0
    To export configuration data from RND 3.5 and later builds and copy the file to the local machine, complete the following steps.
  4. Importing RND 3.0 and RND 3.5 Configuration Data to the RND 4.0 Database
    You can import RND 3.0 MongoDB or RND 3.5 PostgreSQL data to the RND 4.0 PostgreSQL database.
Parent topic: Upgrade Information