> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/getting-started/faq-transitioning-from-the-desktop-client-to-the-web-client.md). # FAQ: Transitioning from the desktop client to the web Client ### What will happen to the desktop client? * **For cloud users (private or public)**: The desktop client will stop working as soon as we release the new aqua version that doesn't support a desktop client in April 2025. * **For on-premises customers**: The desktop client will continue working until you upgrade to the new version of aqua that doesn't support desktop client anymore. ### What happens with scheduled automations that I have in a desktop client? All scheduled automations will be seamlessly migrated to the aqua web client, so no action is required on your part. However, during the update process, we’ll notify you separately and strongly recommend that you avoid starting any new executions, as there’s a chance data could be lost during the transition. ### Will I need to reconfigure agents like JMeter, Ranorex, or SoapUI? Yes, you’ll need to set them up again from scratch. But don’t worry—we’ll provide step-by-step guidance to help you through the process. ### What happens to the custom report scripts I used in the desktop client? * **Public cloud users**: Custom scripts will no longer be supported. * **Private cloud:** You can still use custom scripts in the web client, but you’ll need to send the support request to our team to enable it for you. * **On-premises users**: You can still use custom scripts in the web client, but you’ll need to enable them in the configuration settings in case you haven't done it yet. ### The desktop client handled reporting and import/export tasks faster. What now? We understand this concern, and as part of our technical redesign, we’re enhancing the performance of these tasks in the web client. In addition, we’re introducing new functionality for long-running jobs to ensure smooth operation for reports. ### I use other desktop features that aren’t listed as moving to the web client. Why is that, and what should I do? All essential capabilities **will be gradually added to the web client, based on customer requests and what will benefit our users most.** The good news is that the speed of developing and adding new features to the web client will be 30-45% faster than when the desktop client was in use. ### Who should I contact if I want to request a feature or have additional questions? You can reach out to our **Support** or **Customer Success** teams for assistance at **** or If you'd like to set up a feedback session, feel free to contact the **product management** team at **** --- # 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.aqua-cloud.io/documentation/desktop-client/getting-started/faq-transitioning-from-the-desktop-client-to-the-web-client.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.