> 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-v2.1-en/instalacion/migracion/migragt.md). # Migration of configurations from EditranGT to Connect A command-line application is distributed with the Connect installation that will allow creating schedules in Editran Connect from the EditranGT configurations. The input with the information, which will be incorporated into the Connect database, will be the file generated by EditranGT and which the migration application will extract from the Editran 5.2.2 installation. ## Requirements The initial configuration of the Editran Connect application must have been performed and the Connect services (Editran Connect Base and Editran Connect Scheduler) must be running. The Connect scheduler must be included in the license. EditranGT cannot be running. In addition, **it is necessary that the profile migration has been carried out**, described in section [migration](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/develop/connect/2.1/migracion/README.md). The configurations will be taken from the file generated by EditranGT, whose name is *editrangt.cfg* and which must exist in the path \/cfg. ## Usage 1. Open a CMD terminal. 2. Go to the path \/utils, where the file is located *migraGT.bat*. 3. In the terminal, run the following: > *migraGT.bat -e -i \* > > *After the -i modifier you must indicate the file search interval (in seconds) that has been configured in EditranGT.* ![GT Configuration. File search interval](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-08767c5f352774115324f4940ddfa9aa063491ae%2Fimage183.png?alt=media) 1. Once the process has finished, to see the result check the file *migraGT.log* located in the path *\ /log/migrar.* 2. EditranGT configurations (lines of the file) with any conflict or error, and that could not be migrated, can be consulted in the file *migraGT.err* located in the path *\/log/migrar*. 3. The content of the original file *editrangt.cfg,* with the EditranGT configurations, will be replaced with the content of the file *migraGT.err*. This will allow configurations that for some reason could not be migrated to remain in EditranGT. 4. Each time the migration process is launched, a backup of the file is created *editrangt.cfg.* The backup file will be generated in the folder *\/cfg* and will have the following format: *editrangt-yyyy-MM-dd-hhmmss.cfg.bak* ## Important matters 1. A schedule will be created in Editran Connect for each EditranGT configuration. The schedule name will match the channel name followed by the letter E for transmission schedules, or the letter R for reception schedules. If the configuration is bidirectional, two schedules will be created. 2. Configurations that cannot be migrated will not be deleted from EditranGT. ## Possible errors 1. Not specified *-e* or *-i*. The application will inform the user how to perform the execution. 2. A numeric value is not provided in *File search interval (seconds).* The application will inform the user how to perform the execution. 3. The Connect services are not running, including the scheduler, and an attempt was made to use the migrator. In this case the program will notify that it was not possible to connect to the remote server (Connect). 4. Numbered errors. These are internal program errors (bug) and the exact cause cannot be indicated. Report the problem to the Connect provider so it can be analyzed by the development team. 5. You do not have the scheduler contracted and an attempt was made to use the migrator. The application will report the error. ## Example Will be executed `*migraGT.bat -e -i 60*` ![Execution of the EditranGT configuration migration process.](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-b60bee6b690fbf2f574de15b297ef46377282ecb%2Fimage184.png?alt=media) Next, the corresponding logs should be reviewed to check the result of the migration of each configuration, possible errors, and configurations that could not be migrated. ![Log of the EditranGT configuration migration process](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-b421d0402035a4603a0b66cfb282e288a7130a6b%2Fimage185.png?alt=media) ![EditranGT configurations with errors and not migrated to Editran Connect](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-88317786a7de9c94c69f92a779ea4d5313dafd66%2Fimage186.png?alt=media) --- # 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-v2.1-en/instalacion/migracion/migragt.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.