Codeanywhere Migration
Codeanywhere Migration FAQ
Answers to common questions about moving projects, credentials, files, and team workflows from Codeanywhere to ServerDesk.
Do I need to move my hosting
No. ServerDesk is designed to connect to the server you already use. If you were working against a VPS, cloud server, staging box, or shared host, keep that server and reconnect it over SSH or SFTP.
Can I keep my existing server and connect with SSH or SFTP
Yes. Collect the hostname, port, username, and SSH key or password you already use, then add that connection in ServerDesk. The same details power Explorer, editor, and terminal workflows.
Can I still use Git and terminal
Yes. Explorer replaces remote file browsing, Monaco handles editing, Terminal covers shell work, and Git remains available for stage, diff, commit, push, and pull workflows once the project is connected.
Can Robbie help understand my old project
Yes. Robbie can answer built-in product questions immediately and use AI credits only when you need deeper analysis such as explaining selected code, reviewing a config file, or explaining terminal output from the migrated project.
What if my connection fails
Check the hostname, port, username, root path, and whether the server exposes SFTP as well as SSH. If you still hit a failure, use the troubleshooting guide or contact support with the exact error and the affected server.
What plan should I choose and can agencies migrate multiple servers
Free is the fastest way to validate one server. Starter and Pro fit freelancers and small teams. Studio and Agency are better when you need more connections, more AI credits, and multi-client workflows across several servers.
Need something else?
Move back into the searchable Help Centre, open the Support Hub, or use the public bug report and feature request routes if this article does not cover your workflow.