How to move files from Codeanywhere safely

Start with Git if it already exists

If the project already has a healthy Git remote, push every uncommitted change first. This is the safest way to preserve source files, branch history, and deployment-relevant code before you change tools.

• Commit and push all branches you still need.
• Do not assume a local-only workspace branch will be recoverable later.
• Check for ignored files that matter in production.

Export what Git does not cover

Uploads, compiled assets, media directories, generated files, and hidden configuration files often exist outside normal Git history. Download these directly from Codeanywhere or from the server that currently hosts them.

• Check `.env` files and other hidden dotfiles explicitly.
• Verify storage, uploads, media, and cache directories you actually need.
• Keep secrets in a secure local vault rather than committing them.

Validate before you delete anything

Before you consider the migration complete, confirm that the same file tree exists on the destination server you plan to connect through ServerDesk. A quick Explorer pass and a `find` or `ls -la` check in Terminal is usually enough to catch missing assets early.