> 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.md). # Migration The migration from a classic editran to an editran connect can be performed between different operating systems and different versions of editran (from 5.0 onwards). This process extracts the data contained in the profiles of the source Editran and processes it to adapt it to the Connect format. This process is not reversible; you cannot go from an editran connect to a classic one. It is necessary to perform the migration to adapt the Editran profiles to the new Connect 3.0 data model. Among them, we can highlight changes to security configurations, but we will address the details in the specific section on migrating from Editran Classic to Editran Connect. ## Compatibility Migration to Editran Connect 3.0 is viable from Editran versions 5.0 onward. ## Compendium of Editran Classic configuration files The different Editran Classic configuration files are listed below, as well as their location within the installation. It is necessary to have them in order to carry out the different steps of the migration to Connect 3.0. ### List of configuration files **Profile configuration files:** * **editranp.cfg and editranp.sdx**: binary files with the configuration of the local environment and the Editran/P sessions. * **editrang.cfg**: binary file with the configuration of Editran/G presentations. **EditranGT module configuration file:** * **editrangt.cfg**: binary file with the scheduling configuration of the EditranGT module (if the editrangt functionality was purchased with the product). **Configuration files related to cryptography in Editran:** * **controlgc.cfg**: binary file with the configuration of the EditranGC module, used for the exchange and management of Editran RSA keys. * **ckds.des**: binary file containing the DES keys used for secure file transmission. > *(Only for versions 5.0.x and 5.1.x, earlier than 5.2.0)* > > * *ckds.rsa*: binary file containing the RSA cryptography keys of Editran > > *(Only for versions 5.2.0 and later)* > > * *.rsa*: folder containing the RSA cryptography keys of Editran. ### Location of configuration files in Editran Classic The location of the different configuration files varies depending on the installed version of Editran Classic. * **For Editran Classic versions earlier than 5.2.0 (v5.0 and v5.1):** The profile configuration files, EditranGT configuration, and cryptography configuration are located in the root of the installation folder. ```txt 📂 Editran_50 ┣ 📄 ckds.des ┣ 📄 ckds.rsa ┣ 📄 editranp.cfg ┣ 📄 editranp.sdx ┣ 📄 editrang.cfg ┣ 📄 controlgc.cfg ┗ 📄 editrangt.cfg ``` * **For Editran Classic versions 5.2.0:** * The Editran profile configuration files, the EditranGT configuration file and the file `controlgc.cfg` are located in the folder `cfg`, and this may be located in the product installation path, or in the path defined in the registry variable `EDI_DATA` if a different path than the installation path was specified. * The file `ckds.des` is located inside the folder `bin` located in the product installation path. ```txt 📂 Editran_520 ┣ 📂 bin ┃ ┗ 📄 ckds.des ┗ 📂 cfg ┣ 📂 .rsa ┃ ┗ 📄 Files with the RSA keys ┣ 📄 editranp.cfg ┣ 📄 editranp.sdx ┣ 📄 editrang.cfg ┣ 📄 controlgc.cfg ┗ 📄 editrangt.cfg ``` * **For Editran Classic versions 5.2.1 and later:** * All profile, EditranGT, and cryptography configuration files are located in the folder `cfg`, and this may be located in the product installation path, or in the path defined in the registry variable `EDI_DATA` if a different path than the installation path was specified. ```txt 📂 Editran_521 ┗ 📂 cfg ┣ 📂 .rsa ┃ ┗ 📄 Files with the RSA keys ┣ 📄 ckds.des ┣ 📄 editranp.cfg ┣ 📄 editranp.sdx ┣ 📄 editrang.cfg ┣ 📄 controlgc.cfg ┗ 📄 editrangt.cfg ``` As we can see, the Editran Classic configuration files and their location vary depending on the installed version. To achieve a correct migration of the profiles, it is necessary to specify in the process which source version is to be migrated to Connect 3.0 and to have the necessary files for each version. ## Migration process The profiles from the different versions of Editran Classic are not directly compatible with the new product Editran Connect 3.0, nor with the integrated Editran Core 5.3 software. For this reason, migration to Connect 3.0 is carried out starting from the configuration profiles of Editran Classic in textual mode, that is, by dumping the local environment, sessions, and presentations configured in Classic to a file. We highlight three main scenarios, each with different procedures, to address the migration. The detailed procedure for how to carry out the migration in each scenario will be explained later in the step-by-step guide. Depending on each scenario, dumping the profiles to text (the starting point of the migration to Connect 3.0, as mentioned above) can be done automatically (by the profile migrator included in the Core module) or manually by the operator who will carry out the migration (how to do it is detailed in the step-by-step guide). It is important to note that sessions/presentations may undergo automatic adaptation when dumped to text, necessary for adaptation to Connect 3.0, but in any case, without modifying the original Classic installation configuration (the binary format configuration profiles will not change in the source installation). You can consult the summary of all changes made to adapt the profiles to Connect 3.0 on this same page. ### Between different machines with the same operating system If the new Editran Connect 3.0 system is on a different machine from the source one (where Editran Classic is installed), ensuring that the operating system is the same, it is necessary to copy all Editran configuration in its binary format *(depending on the source version, the location of the different configuration files varies as noted above)* to the destination machine, before starting the migration process. ### On the same machine In this case, the Editran Classic configuration already exists on the same machine and it is only necessary to ensure that it is accessible from the new Editran Connect 3.0 system. It is recommended to make a full backup of the Editran Classic installation before migrating to Connect. ### Migration between different operating systems In environments where the source OS is different from the destination OS, the migration process differs slightly. The configuration profiles must be dumped to text format, before copying them to the destination machine, using the commands `ediperfi` and `igaperfi` from the Editran Classic version on the source machine. The cryptography configuration files must also be copied, together with the textual profile configuration files, *as is* (in binary format, without dumping them to text or performing any transformation on them) and the EditranGT configuration if available (also in binary format). ## Summary of changes made in the migration to the Editran profiles The changes implemented in the new version of Connect 3.0 include: * Incompatibility with the Editran 4.1 protocol * Incompatibility with DES 2.2 cryptography version * The parameter has been removed *increase presentation number*. * Reimplementation of the download acknowledgment functionality (only valid between Connect 3.0 and Editran Classic 5.3 systems). * Incompatibility of the DES and TD2 encryption algorithms. * *Confidentiality incompatibility in P* --- # 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.md?ask=&goal= ``` `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.