> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/deployment-and-maintenance/migration/askedgi.md). # askEdgi This article provides a detailed reference for migrating existing customer environments to the AskEdgi model. It outlines the complete process to ensure a secure, consistent, and efficient transition of infrastructure, applications, and data without impacting system availability or compliance. The migration process includes account setup, environment provisioning, AWS-based automation, network and security configuration, application and data migration, and post-deployment validation. By following these standardized steps, existing customers can seamlessly move to the AskEdgi architecture with minimal downtime and complete operational alignment. **Included Documents:** * [Existing Customer Migration](https://docs.ovaledge.com/deployment-and-maintenance/migration/askedgi/existing-customer-migration) *** Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ovaledge.com/release8.1/deployment-and-maintenance/migration/askedgi.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.