# Migrate data from ALM/PC to SaaS

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

Every ALM/PC 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.

In this topic:

## 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.

   UNIX

   To summarize the directory and all sub-directories and display size values in a human-readable format, use:

       du –sh <directory name>

   For example,

       root@ubuntu# du -sh /usr/ X11R6
       4.0K /usr/X11

   If you find all your path repositories follow the same path, use the following command to show the summary of only the first level of the sub-directories within the folder. This summary lets you know the size of all the file repositories folders on the same path.

   For example,

       root@ubuntu# du -sh /usr/*

       4.0K /usr/X11R6
       96M /usr/bin
       24K /usr/games
       12M /usr/include
       164M /usr/lib
       0 /usr/lib64
       96K /usr/local
       25M /usr/sbin
       197M /usr/share
       4.0K /usr/src

   Linux

   To summarize the directory and all sub-directories and display size values in a human-readable format, use:

       du –sh

   For example,

       $ du -sh svn/ports
       6.2M svn/ports

   Windows

   Right-click the folder and select Properties to view the size of the folder.

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.

   Oracle

   To obtain the size of the DB_USER_SCHEMA schema, connect to the Oracle instance and run the following SQL query.

   - To obtain the size of each database schema, run:

         SELECT SUM(BYTES)/1024/1024 "MB" FROM DBA_SEGMENTS WHERE owner='<SCHEMA>';

   - To obtain the size of all database schemas at one time, run:

         SELECT owner, SUM(BYTES)/1024/1024 "MB" FROM DBA_SEGMENTS group by owner

   SQL Server

   Run the following command to print a summary of space used in the current database.

       sp_spaceused

   Output:

       database_name database_size
       --------------- ---------------------------
       master 5 MB
       reserved data index_size unused
       --------- --------- ----------- --------
       2176 KB 1374 KB 72 KB 730 KB

   Note: The database_size metric shows the size of the current database in megabytes, including both data and log files.

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:

Oracle

1. Connect to the database server as a database user.

2. Run the following command for each schema you want to export.

       expdp system/<password> schemas=<schema name> dumpfile=<schema name>_<date>.dmp logfile=<schema
       name>_<date>.log exclude=statistics directory=DATA_PUMP_DIR

3. Connect to the database as a system user, for example, sqlplus system/<password>, and run the following command to loate your data dump directory:

       SELECT directory_path FROM dba_directories WHERE directory_name = 'DATA_PUMP_DIR';

4. Change to the directory, and you will see all the dump files.

5. Compress the backups of the database schemas.

6. Run `md5sum`.

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

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

   For example:

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

   The command returns the md5sum output. For example,

       24BCED0C939DD7E61C6E4CCE252687BE db_schemas.zip

8. Copy the output to a text file.

9. Upload the compressed database schema and the text file to the FTP server.

SQL Server

1. Back up the database schemas by one of the following options.

   - Back up each database schema by running:

         Backup database X to disk=’<path>’

   - Detach each database schema by running:

         Sp_detach_db ‘database name’

2. Compress the backups of the database schemas.

3. Run `md5sum`.

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

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

   For example:

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

   The command returns the md5sum output. For example,

       24BCED0C939DD7E61C6E4CCE252687BE db_schemas.zip

5. Copy the output to a text file.

6. Upload the compressed database schema and the text file to the FTP server.

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:

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

   For example,

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

   The command returns the md5sum output. For example,

       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,

          <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:

       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:

- Export a project from ALM/PC to SaaS
- Migrate LoadRunner Enterprise to SaaS

https://admhelp.microfocus.com LoadRunner Enterprise 8942
Tips to improve your search results... LoadRunner Enterprise Help Center LoadRunner Enterprise Help LR Enterprise Help 2020_SP2-SP3 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: