> For the complete documentation index, see [llms.txt](https://docs.neverinstall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neverinstall.com/data-migration.md). # Data Migration * Migrating codebase: Migrating code can be done in the following ways - * GitHub - If the user is logged in to Github, they can directly clone the project from the terminal of IDE’s * Other code hosting repositories are fully supported, cloning the project is simple and effective * Uploading code and folder to Google Drive or hosting sites and then downloading through the terminal is supported currently. * Upcoming features of file upload/download will enable users to directly upload and download files from Neverinstall * Migrating dev environment: Docker file migrations can be done if the user has a docker file that can be pulled from the terminal of Neverinstall. The remaining things are the same as the local machine setup * Migrating IDEs' configurations: The majority of IDEs have SSO options that automatically sync the configurations once logged in successfully. * Almost all IDE support features of exporting configuration files, users can import them directly to other environments IDE * Migrating custom OS configurations: OS shortcuts are part of IDES' configurations migration * Migrating custom Keyboard configurations: Keyboard shortcuts are part of IDEs' configurations migration --- # 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.neverinstall.com/data-migration.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.