Migrate data to SaaS

This section provides instructions about how to migrate ALM/QC data from on-premises to SaaS.

Every ALM/QC project has its own database schema and file repository. All the steps in this topic should be performed for every project you want to migrate to SaaS.

Obtain file repository size

Follow the step below to obtain the size of the file repository from the file server.

  1. Open ALM Site Administration.

  2. Select the project you want to migrate. In the Project Details tab, under the Project Directory field, find the file repository path of the project.

  3. On the file server machine, navigate to the repository path of the project and run the following command.

Back to top

Obtain database schema size

Follow the steps below to obtain the size of the database schema.

  1. Open ALM Site Administration.

  2. Select the project you want to migrate. In the Project Details tab, under the Database Name field, find the database schema of the project. Under the Database Server field, find the server where the schema is located.

  3. On the database server, run the following command to obtain the size of the database schema.

Back to top

Export database schema

Export the database schema of each project you want to migrate.

Prerequisites

Consider the following prerequisites before you export the database schema.

MD5 software For example, md5.
FTP server A FTP server location should be provided by your CSM during the migration process.

To export the database schema:

Perform one of the following export actions, depending on your database type:

Back to top

Export file repository

Follow the steps below to export the file repository.

  1. Open ALM Site Administration.

  2. Select the project you want to migrate. In the Project Details tab, under the Project Directory field, find the file repository path of the project.

  3. Connect to the application server, navigate to the project directory path, and compress the entire file repository folder.

  4. Run md5sum.

  5. Open a command window, navigate to the location where the md5.zip file was extracted, and run the following command.

    Copy code
    md5.exe -generate <compressed folder path><compressed folder name.zip>

    For example,

    Copy code
    md5.exe – generate C:\”Documents and Settings”\Desktop\ project1_filereposiotry.zip

    The command returns the md5sum output. For example,

    Copy code
    24BCED0C939DD7E61C6E4CCE252687BE db_schemas.zip
  6. Copy the output to a text file.

  7. Upload the compressed file repository and the text file to the FTP server.

  8. Repeat the above steps for each project you want to migrate.

Back to top

Migrate users to SaaS

Follow the steps below to migrate users from on-premises to SaaS.

  1. From the ALM server, search for the site admin schema name.

    1. Log in to the ALM server.

    2. Navigate to the directory where ALM is installed.

    3. Navigate to the directory where the siteadmin.xml file is saved.

    4. Open the file and search for the site admin schema name using the DBNAME tags. For example,

      Copy code
      <DbName>qc_sa_esar_db</DbName>
  2. Contact the DBAs to search for the users tables on the site admin schema. The DBAs should then perform a select all query from the users tables. For example,

    Copy code
    select * from td.users
  3. Copy the results of the select all query into an Excel spreadsheet and upload it to the FTP server.

Back to top

See also: