Before You Start

• Make sure you have access to the old SCG primary instance. 
• Make sure the new SCG installation is available and accessible. 
• Make sure you have permission to copy files using scp and access servers using ssh. 
• Prepare a local system where you can temporarily store the exported archive file. 

• Use this procedure when migrating from SCG 1.2409. For these migrations, an additional manual export script is provided to create the required data archive. 

  Important: The migration export scripts under migrationExport/migrationExport are discontinued. Use /opt/unicon/scg/scripts/dataExport.sh from the new SCG installation instead. 

Step 1: Export Data from the Old SCG

For customers migrating from version 1.2409, data must be exported manually with the provided script. 

1. Locate the export script on the new SCG installation:
   /opt/unicon/scg/scripts/dataExport.sh 

2. Copy dataExport.sh from the new SCG installation to the old SCG primary instance using scp. 

3. Connect to the old SCG primary instance using ssh.

4. Make the script executable and run it. 
   
   chmod +x dataExport.sh
   ./dataExport.sh
   

5. The script writes the export file to a temporary location similar to:
   /tmp/scg-data_mko-scg-2409_...json
   
   

      6.Copy the exported file from the old SCG system to your local system using scp.

Best practice: Keep the exported file in a safe location until the migration is fully validated.

Step 2: Import Data into the New SCG

On the new SCG installation, use the data import function in the user interface and provide the exported data file created in the previous step. 

The import process includes built-in warnings and error checks to help identify potential issues before completing the migration.

Possible Warnings During Import

The following warnings may appear during import: 

• Old archive: The provided file is older than three months. Imported client certificates may have expired. 
• Inactive clients: None of the eLux clients in the archive were active within the last three months. 
• Expired clients: None of the eLux clients in the archive have valid certificates. 
• Different authentication type: Import will overwrite the current user authentication method. 
• Local user update: Import will overwrite currently configured WebAdmin users. The special administrator username admin is not changed. 
• Acknowledge warnings: You must confirm the warnings before continuing. 

Warning: Review all import warnings carefully before proceeding. They may indicate authentication changes, expired client certificates, or inactive client records. 

Possible Errors During Import

The following errors may prevent the import from completing: 

• Corrupted file: The selected file is corrupted or unreadable. 
• Invalid archive: The selected file is not a valid SCG data archive. 
• Unsupported version: The selected file was created by a newer SCG version and cannot be imported. 
• Import failed: The system could not import the data. 

If an error appears, do not continue the migration until the issue is resolved.
Verify that the correct export file was used and that it was created from the supported source version. 

Optional: Data Export Using the SCG Dialog

SCG installations also provide a data export function in the user interface. 

This function can export:

• data from the local database,
  or
• data from another SCG instance by connecting to it with valid credentials. 

For migration from version 1.2409, use the manual export script procedure unless instructed otherwise. 

Migration Test Scenario

Test Setup

• Optional: Configure a generic DNS CNAME redirect to scg_old. 

• scg_old

  • Install and configure SCG version 1.2409. 
  • Configure all required settings. 

• eLux client

  • PXE boot the client. 
  • Onboard the client to scg_old. 

• scg_new

  • Install and configure the target SCG version, for example 1.2605. 
  • Configure all required settings. 

Test Steps

1. Export data on scg_old using the manual export procedure. 
2. Import the exported data on scg_new using the SCG data import function. 
3. Change the DNS CNAME entry from scg_old to scg_new,
   or
4. modify the /setup/terminal.ini file: 

ScoutCloudGateway=scg_old
ScoutCloudGateway=scg_new

Expected result: After the import and client redirection, the eLux client should connect to the new SCG instance successfully.