> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/connect-v3.1-en/migracion/clasico-a-connect.md).

# Migration to Connect

This document details step by step the migration process from Editran Classic to Editran Connect 3.0.

The migration is divided into two sections:

1. Core module migration
2. Migration to Connect 3.0

## Before you begin

Before the migration can be carried out, the following requirements must be met and it must be clear which scenario we are in: A. Migration on the same platform (machine/PC change supported) C. Migration with machine change to a different platform

The following sets of operating systems are understood as platforms:

* Windows platform (e.g. Windows 10, Windows 11, Windows Server, ...): the Editran configuration is directly compatible across all of them.
* Unix platform (Red Hat 8, Red Hat 9): the Editran configuration is directly compatible across all of them.
* AIX operating systems
* HP operating systems
* zOS operating systems

### Previous steps

* If using the same machine to migrate to the current version, it is necessary to uninstall the Editran Classic version before installing the Editran Connect product. **It is recommended to make a full backup of the Editran Classic installation before uninstalling it.**
* The machine where the migration to the current version is being performed must have the configuration files for the different scopes to be migrated:
  * Editran Classic configuration:
    * If migrating to the same platform: files editranp.cfg, editranp.sdx and editrang.cfg
    * Migration with platform change: text files editranp.txt and editrang.txt.
  * Cryptography configuration:
    * EditranGC module configuration file: controlgc.cfg
    * File with the DES keys: ckds.des
    * Files with the RSA keys: ckds.rsa or .rsa folder depending on the Editran Classic version
  * EditranGT configuration:
    * editrangt.cfg file
* The configuration files to be migrated must be organized with the same directory tree they had in the source installation.\
  For more detail, see the section *Location of the configuration files in Editran Classic* of the general Connect Migration document.
* The Connect 3.0 product must already have the license installed in the folder `%EDITRAN_HOME%/bin/SL/licencia.dat` and the service `Editran License Service` must be running.
* The *onboarding* of the Connect application must have been completed, which is done after creating the IP when logging in for the first time.

![finOnboarding](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-eda9aa68254f713a78b97b073c54a9e8a48934e2%2FfinOnboarding.png?alt=media)

### Text dump of the configuration profiles

If a platform change was chosen when installing Connect 3.0, as detailed above, it is necessary to convert the Editran Classic configuration to text format.

To do this, two commands included in the Editran Classic product installation folder on the source machine must be run. By default, the commands will create the files `.txt` in the folder `bin`, unless another directory is specified in the parameter `-o"full_path/other_location/filename.txt"` :

* Run the command `ediperfi -r -a -n -oeditranp.txt` to dump the local profile and all configured sessions that contain TCP configuration to the file *editranp.txt*.
* Run the command `igaperfi -r -a -oeditrang.txt` to dump all configured presentations to the file *editrang.txt*.

Once the text configuration files have been obtained, **they must be copied to the folder `%EDITRAN_HOME%/cfg` of the new Editran Connect 3.0 installation.**

#### On Windows platforms

![windows-volcado-a-texto](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-c595538846fe37075991c3109552d1415d208192%2Fwindows-ediperfi-igaperfi_volcado_a_texto.jpg?alt=media)

The Connect 3.0 installation path is indicated by the environment variable `%EDITRAN_HOME%`.

![windows-copiar-volcado-a-texto](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-5f1bf00537263586c6cf1474ab299cad62710fa9%2Fwindows-ruta_cfg_volcado_texto.png?alt=media)

#### On Linux platforms:

![linux-volcado-a-texto](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-fd3e77ad7ff88bdd854f4a6be9d9b6a5e5f64850%2Flinux-ediperfi-igaperfi_volcado_a_texto.png?alt=media)

The Connect 3.0 installation path is indicated by the variable `$EDITRAN_HOME`, defined in the file `$EDITRAN_CONNECT_HOME/services/Env.conf` of the installation.

![linux-copiar-volcado-a-texto](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-df0dab788b4a85a841df50748eb8ade26740b80f%2Flinux-ruta_cfg_volcado_texto.png?alt=media)

***

## Windows Platform Guide

Once the prerequisites have been met and the configuration files `*.cfg` or the text-dumped configuration are available on the destination machine, proceed as follows.

### 1. Core migration

This configuration migration step **only applies to installations without a platform change**.

At this point, we start from the original configuration in binary format and use the tools `Migrar.exe` and `MigrarRSA.exe` included in the Core module of the Editran Connect 3.0 product (the full path to the tools is `%EDITRAN_HOME%/bin`)

![core-migrators-path](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/public/connect/3.1/migracion/assets/Ruta_migradores_core.png)

#### Migrar.exe: Configuration migrator

We run the tool `Migrar.exe` to adapt the profile configuration and EditranGT (only if the license contains the feature `scheduler`).

In this dialog, we must select the full path to the original configuration profiles (the path to the folder with the copied profiles, if applicable), the source version of the migration and the checkbox for only copying sessions with TCP network data. By default, the dump directory will be the folder `%EDITRAN_HOME%/cfg`

![run-migrar-exe](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-e9c4f22c7255edecff678240007fb6b679775628%2Fmigrar_exe_ejecutado.png?alt=media)

#### MigrarRSA.exe: RSA cryptography migrator

We run the tool `MigrarRSA.exe` to migrate the DES and RSA keys used in Editran Classic presentations. This process automatically runs the command `checkgc -u` to adapt the DES keys if necessary.

In this dialog we must also select the full path to the original configuration profiles and the source version of the migration. By default, the dump directory will be the folder `%EDITRAN_HOME%/cfg`

![run-migrarRSA-exe](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-38a537499b8d41239303d11c20fb7f60a44f921a%2FmigrarRSA_exe_ejecutado.png?alt=media)

#### Files for migration to Connect 3.0

Finally, if everything has gone correctly, we should find all the files needed for the migration to Connect 3.0 in the dump folder `%EDITRAN_HOME%/cfg`

![files\_dumped\_for\_connect](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-9504a95b069cd546c0ddb31118bc81a78dd608dc%2Fficheros_volcados_core.png?alt=media)

### 2. Migration to Connect 3.0

At this point we assume that the files needed to migrate to Connect 3.0 are already available, having previously carried out the Core migration if necessary.

All the scripts needed from this point on are located in the folder `%EDITRAN_CONNECT_HOME%/utils`

![migration\_scripts\_connect](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-21cfa94794ecd5bee4b253ae41b9c52477e07bfe%2Fscripts-migrar-connect-utils.png?alt=media)

Before running the scripts, it is necessary to finish the *onboarding* of the Connect application, which is completed when the IP is created after logging in for the first time.

For the two configuration profile migration programs, if no parameter is specified, it will automatically look for the files `editranp.txt` and `editrang.txt` in the folder `%EDITRAN_HOME%/cfg`, the location where the tool `Migrar.exe` leaves the profiles.

#### Run script migraContactos.bat

This tool migrates the *local configuration*, that is, the local codes, IPs and the Editran/P sessions. Then, for each remote code it will create a contact, which groups the channels (old presentations)

This first migrator is located at `%EDITRAN_CONNECT_HOME%/utils/migraContactos.bat`. To be used it requires the service `Editran Connect Base` to be started.

The command accepts several arguments, among which we highlight:

* `migraContactos -e`: this option will directly migrate the configuration from the file `editranp.txt` dumped by the tool `Migrar.exe` in the folder `%EDITRAN_HOME%/cfg`. See process [Core migration](#windows-migrar-core)
* `migraContactos -f -fp "<absolute_path_to_editranp.txt_file>"`: use this option if the profiles in text format are available following the [platform change](#volcado-cambio-plataforma), indicating the full path to the location of the editranp.txt file.

![migraContactosH](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-a543e7b3b5640cbae59b427d0ec22246bef4db2b%2FmigraContactosH.png?alt=media)

After running the tool, the command output itself will indicate whether there are errors or not. The message `Execution completed successfully` means there were no errors or warnings in the migration process. In any other case, a file will be generated at the path `%EDITRAN_HOME%/log/migrar/conflictosREMOTOS.txt`, which will contain information about actions to be taken on the profiles or warnings that occurred.

![executionMigraContactos](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-deeb7d2e4270664f71817fbebdc7b09e363f016d%2FejecucionMigraContactos.png?alt=media)

**Once this process has finished without errors, it is necessary to start the service `Editran Base Service` to continue with the channel migration tool. This is a mandatory condition; otherwise the next process will fail.**

#### Run script migraCanales.bat

This tool migrates transmission channels to Connect. To do this, it reads the Editran/G presentations (present in the editrang.txt file) and the Editran/P sessions (present in the editranp.txt file) to create a channel (sessions and presentations that contain the same local-remote-application code) in the contact to which they belong (the remote code).

This second migrator is located at `%EDITRAN_CONNECT_HOME%/utils/migraCanales.bat`. To be used it requires the services `Editran Connect Base` and `Editran Base Service` to be started. It is also essential that the script `migraContactos.bat` has been executed correctly in order to create the contacts that will store the channels.

The command accepts several arguments, among which we highlight:

* `migraCanales -e`: this option will directly migrate the configuration from the file `editrang.txt` dumped by the tool `Migrar.exe` in the folder `%EDITRAN_HOME%/cfg`. See process [Core migration](#windows-migrar-core)
* `migraContactos -f -fg "<absolute_path_to_editrang.txt_file>" -fp "<absolute_path_to_editranp.txt_file>"`: use this option if the profiles in text format are available following the [platform change](#volcado-cambio-plataforma), indicating the full path to the location of the editrang.txt and editranp.txt files.

![migraCanalesH](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-e3114d5bde9121839adb63f3f40bb5bce78bfbab%2FmigraCanalesH.png?alt=media)

After running the tool, the following message will appear in the console `Execution finished, to see the result of the process check the output log`. This log is located at the following path `%EDITRAN_HOME%/log/migrar/logCANALES.txt`, which contains information about the channels that were migrated and those that could not be incorporated into Connect.

![executionMigraCanales](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-1a455a87bdb54069b4ad4096480b6af62ec44581%2FejecucionMigraCanales.png?alt=media)

Once the process is finished, the channels will be registered in Editran/P and in Connect. It is recommended to check the MenuP panel to confirm that everything is correct.

#### Run script migraGC.bat

This tool migrates the DES and RSA cryptographic key configuration used in Editran Classic to the new channels created in Connect.

According to the [cryptography adaptations introduced in the Connect 3.0 product version and Editran 5.3 protocol](#adaptaciones-criptografia-Connect3.0), the original cryptography configuration may vary, making it necessary for the Connect operator to perform manual adjustments on each specific channel.

This migration tool only accepts one parameter:

* `migraGC -e`: this option migrates to the Connect 3.0 database the RSA keys found in the folder `%EDITRAN_HOME%/cfg/.rsa` and applies, to the created channels, the cryptography configuration from the file `controlGC.cfg` (file migrated by the tool `MigrarRSA.exe` and present in the folder `%EDITRAN_HOME%/cfg`. See process [Core migration](#windows-migrar-core) for more information).

Halfway through the tool execution, when the message *Press any key to continue...* appears, it is necessary to press a key so that it continues with linking the keys to the previously created channels.

![executionMigraRSA](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-9dad1bf6522aad8d02157d99c8c10f17fa8c92bc%2FejecucionMigraRSA.png?alt=media)

#### Run script migraGT.bat

This tool allows migrating schedules from the EditranGT configurations present in the file `%EDITRAN_HOME%/cfg/editrangt.cfg`.

This migration tool needs to receive two parameters in its invocation:

* `migraGT -e -i <file_search_interval_(seconds)>`: After the modifier `-i` the file search interval (in seconds) configured in EditranGT must be indicated. By default, the command will look for the configuration file `%EDITRAN_HOME%/cfg/editrangt.cfg` to migrate the scheduler configurations.

![executionMigraRSA](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-6e248347887805d45ea085c112d643f963fd5fdf%2Fwin-migraGT-bat.png?alt=media)

Details to keep in mind:

* EditranGT configurations (file lines) with any conflict or error, and that could not be migrated, can be found in the file `migraGT.err` located at the path `%EDITRAN_HOME%/log/migrar`.
* The contents of the original file `editrangt.cfg`, with the EditranGT configurations, will be replaced with the contents of the file `migraGT.err`. This will allow any configurations that for some reason could not be migrated to remain in EditranGT.
* Each time the schedule migration tool is run, a backup of the file will be created `editrangt.cfg`. The backup file will be generated in the folder `%EDITRAN_HOME%/cfg` and will have the following name: `editrangt-yyyy-MM-dd-hhmmss.cfg.bak`

***

## Linux Platform Guide

Once the prerequisites have been met and the configuration files `*.cfg` or the text-dumped configuration are available on the destination machine, proceed as follows.

### 1. Core migration

This configuration migration step **only applies to installations without a platform change**.

At this point, we start from the original configuration in binary format and use the scripts `migra-cfg.bash` and `migra-rsa.bash` included in the Core module of the Editran Connect 3.0 product. The full path to the scripts is `%EDITRAN_HOME%/inst`.

![linux-core-migrators-path](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-383705ff91297fbf6fa805897117032231f9fa1a%2Flinux-ruta_migradores_Core.png?alt=media)

#### migra-cfg.bash script: Configuration migrator

We run the script `migra-cfg.bash` to adapt the profile configuration and EditranGT (only if the license contains the feature `scheduler`).

This script guides us through entering all the parameters needed for the migration, such as the version and release of the source Editran Classic being migrated and the full path to the original configuration profiles (the path to the folder with the copied profiles, if applicable). By default, the dump directory will be the folder `%EDITRAN_HOME%/cfg`

![run-migrar-exe](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-2eaede1ee23bb60029c8acfdbfa0c1804992470b%2Fmigra-cfg_bash_ejecutado.png?alt=media)

#### migra-rsa.bash script: RSA cryptography migrator

We run the script `migra-rsa.bash` to migrate the DES and RSA keys used in Editran Classic presentations. This process automatically runs the command `checkgc -u` to adapt the DES keys if necessary.

In this script we must enter, likewise, the source version of the migration and the full path to the original configuration profiles. By default, the dump directory will be the folder `%EDITRAN_HOME%/cfg`

![run-migrarRSA-exe](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-981121945ef9a699906890d44c213e9e7906b93e%2Fmigra-rsa_bash_ejecutado.png?alt=media)

#### Files for migration to Connect 3.0

Finally, if everything has gone correctly, we should find all the files needed for the migration to Connect 3.0 in the dump folder `%EDITRAN_HOME%/cfg`

![files\_dumped\_for\_connect](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-f60b58206d5a0012803045a2e564ebe5b7ed9212%2Flinux-ficheros_volcados_core.png?alt=media)

In turn, we can find all the intermediate files used for the migration in the folder`%EDITRAN_HOME%/migration`. These intermediate files are:

* binary files *.cfg* copied from the original installation
* files *.err* with possible output errors when running the ediperfi and igaperfi commands
* file *migra\_cfg.log* with the migration result

![files\_dumped\_for\_connect](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-5d213dedb0bd776dab48e11c27d08c642474c449%2Flinux-ficheros_intermedios_core.png?alt=media)

### 2. Migration to Connect 3.0

At this point we assume that the files needed to migrate to Connect 3.0 are already available, having previously carried out the Core migration if necessary.

All the scripts needed from this point on are located in the folder `%EDITRAN_CONNECT_HOME%/utils`

![migration\_scripts\_connect](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-ef6fc527b5035c95f399c522a32248b4033c20f4%2Flinux-scripts-migrar-connect-utils.png?alt=media)

Before running the scripts, it is necessary to finish the *onboarding* of the Connect application, which is completed when the IP is created after logging in for the first time.

For the two configuration profile migration programs, if no parameter is specified, it will automatically look for the files `editranp.txt` and `editrang.txt` in the folder `%EDITRAN_HOME%/cfg`, location where the script `migra-cfg.bash` leaves the profiles.

#### Run script migraContactos.sh

This tool migrates the *local configuration*, that is, the local codes, IPs and the Editran/P sessions. Then, for each remote code it will create a contact, which groups the channels (old presentations)

This first migrator is located at `%EDITRAN_CONNECT_HOME%/utils/migraContactos.sh`. To be used it requires the service `Editran Connect Base` to be started.

The command accepts several arguments, among which we highlight:

* `migraContactos -e`: this option will directly migrate the configuration from the file `editranp.txt` dumped by the script `migra-cfg.bash` in the folder `%EDITRAN_HOME%/cfg`. See process [Core migration](#linux-migrar-core)
* `migraContactos -f -fp "<absolute_path_to_editranp.txt_file>"`: use this option if the profiles in text format are available following the [platform change](#volcado-cambio-plataforma), indicating the full path to the location of the editranp.txt file.

![migraContactosH](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-63e38806db0797dfe629cc6d6cc61bb127ff11bf%2Flinux-migraContactos-help.png?alt=media)

After running the tool, the command output itself will indicate whether there are errors or not. The message `Execution completed successfully` means there were no errors or warnings in the migration process. In any other case, a file will be generated at the path `%EDITRAN_HOME%/log/migrar/conflictosREMOTOS.txt`, which will contain information about actions to be taken on the profiles or warnings that occurred.

![executionMigraContactos](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-486e71054b15592bd91384b21d97cd0e60ac37ba%2Flinux-ejecucionMigraContactos.png?alt=media)

**Once this process has finished without errors, it is necessary to start the service `Editran Base Service` to continue with the channel migration tool. This is a mandatory condition; otherwise the next process will fail.**

![start-base-service](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-e61a453032375bb45b67bc7513146da51042b4c2%2Flinux-arrancar-servicio-base.png?alt=media)

#### Run script migraCanales.sh

This tool migrates transmission channels to Connect. To do this, it reads the Editran/G presentations (present in the editrang.txt file) and the Editran/P sessions (present in the editranp.txt file) to create a channel (sessions and presentations that contain the same local-remote-application code) in the contact to which they belong (the remote code).

This second migrator is located at `%EDITRAN_CONNECT_HOME%/utils/migraCanales.sh`. To be used it requires the services `Editran Connect Base` and `Editran Base Service` to be started. It is also essential that the script `migraContactos.sh` has been executed correctly in order to create the contacts that will store the channels.

The command accepts several arguments, among which we highlight:

* `migraCanales -e`: this option will directly migrate the configuration from the file `editrang.txt` dumped by the script `migra-cfg.bash` in the folder `%EDITRAN_HOME%/cfg`. See process [Core migration](#linux-migrar-core)
* `migraContactos -f -fg "<absolute_path_to_editrang.txt_file>" -fp "<absolute_path_to_editranp.txt_file>"`: use this option if the profiles in text format are available following the [platform change](#volcado-cambio-plataforma), indicating the full path to the location of the editrang.txt and editranp.txt files.

![migraCanalesH](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-d57fbc6e00f0df85c64b5524b162c3b639bfb884%2Flinux-migraCanales-help.png?alt=media)

After running the tool, the following message will appear in the console `Execution finished, to see the result of the process check the output log`. This log is located at the following path `%EDITRAN_HOME%/log/migrar/logCANALES.txt`, which contains information about the channels that were migrated and those that could not be incorporated into Connect.

![executionMigraCanales](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-8fa25dc901af198f22e05874dea7fd6463ef3e49%2Flinux-ejecucionMigraCanales.png?alt=media)

Once the process is finished, the channels will be registered in Editran/P and in Connect. It is recommended to check the MenuP panel to confirm that everything is correct.

#### Run script migraGC.sh

This tool migrates the DES and RSA cryptographic key configuration used in Editran Classic to the new channels created in Connect.

According to the [cryptography adaptations introduced in the Connect 3.0 product version and Editran 5.3 protocol](#adaptaciones-criptografia-Connect3.0), the original cryptography configuration may vary, making it necessary for the Connect operator to perform manual adjustments on each specific channel.

This migration tool only accepts one parameter:

* `migraGC -e`: this option migrates to the Connect 3.0 database the RSA keys found in the folder `%EDITRAN_HOME%/cfg/.rsa` and applies, to the created channels, the cryptography configuration from the file `controlGC.cfg` (file migrated by the script `migra-rsa.bash` and present in the folder `%EDITRAN_HOME%/cfg`. See process [Core migration](#linux-migrar-core) for more information).

Halfway through the tool execution, when the message *Press any key to continue...* appears, it is necessary to press a key so that it continues with linking the keys to the previously created channels.

![executionMigraRSA](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-4108f7f4b2af747a4098abbb81c02e7c04622404%2Flinux-migraGC_ejecutado.png?alt=media)

***

## Output logs with the migration result

After running the Connect migrators, they will leave a trace of the result in the folder `%EDITRAN_HOME%/log/migrar`. It is recommended to review these logs since they will contain information needed about the migration process to Connect 3.0. Likewise, they may contain errors or warnings that require the operator's attention to adapt the source profiles before performing the operation again.

## APPENDIX: Adaptations in Editran Classic profiles

A concise summary of all transformations and adaptations to the Editran profiles in the migration process to Connect 3.0.X with the new Editran 5.3 protocol.

### Changes in Editran P sessions

* Incompatibility with remotes in protocol version 4.1. The channel's remote version parameter is automatically updated to version 5.0.
* Sessions that do not have an analogous presentation in G are not migrated (a session configured ONLY in P).

### Changes in Editran G presentations

* Presentations that do not have an analogous session in P are not migrated (a presentation configured ONLY in G).
* The configuration parameter is removed `Increment presentation number`.
* The parameter is removed `character set` with ASCII/EBCDIC values. Now, the alphabet travels in the CSB and the remote Editran system adapts automatically.
* The `download confirmation` is always migrated to `NO`. This functionality has been reimplemented in protocol 5.3 and is only compatible between endpoints with 5.3 versions.

### Changes in cryptography configuration

* **DES cryptography version 2.2 incompatibility:** Now, when migrating, depending on the features configured in the license and the protocol version, the final cryptography configuration is calculated according to the following diagrams. In any case, *when a cryptography configuration is modified, the channel may become unusable and a coordinated key exchange with the remote side is required*:

In EditranP:

![modifs-P-cripto-DES22](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-562b61c0ab48fba6890cadace38b4da754c80238%2FDiagrama_modificaciones_criptografia-P_DES22.png?alt=media)

In EditranG:

![modifs-G-cripto-DES22](https://1190478111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzO0mk2eo5LONjICfqrP8%2Fuploads%2Fgit-blob-b0f97fbae8be287fcdc60154854783885dfaf0f3%2FDiagrama_modificaciones_criptografia-G_DES22.png?alt=media)

* Incompatibility of the DES and TD2 encryption algorithms. The minimum encryption algorithm will be TD3, leaving the possibility of not encrypting.
* Configuring a confidentiality algorithm in P is poor practice; by default it is disabled in channel migration. If it needs to be enabled, it must be manually modified again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/connect-v3.1-en/migracion/clasico-a-connect.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.