Before leaving VS Code, identify which part you want to replace: the editor, the extension ecosystem, the remote workflow, or the data it stores. A different editor may solve one issue while breaking another.
Use a copy of a project with your normal formatter, language server, debugger, test runner, and Git workflow. Time the steps you perform daily: opening the project, finding a symbol, debugging a failing test, and reviewing a diff. Record any extensions that cannot be replaced and any configuration you cannot export.
If portability is the reason for switching, check the installation method first. VS Code's portable mode uses a ZIP/TAR.GZ build with a data directory; ordinary installer behavior is different. A successful trial ends with a build and debug session, plus a documented rollback to your old settings.
Akousa