Transfer a project
A project can move to another ComputeSphere account, for example when a client takes over an app you built, or when you bring projects together under one account. The project moves in place: its services keep running, its URLs don't change, and nothing is copied or rebuilt.
Ask for a transfer
Ask us from the sending account; we confirm with the receiving account's owner or admin before we move it. An owner or admin of the account the project belongs to opens a support ticket naming the project and the receiving account.
Once the receiving account agrees, our support team moves the project, usually within one business day.
Your services keep running and their URLs don't change. Each service restarts once, the next time it's deployed after the transfer (straight away for services behind access protection). Services with a health check keep serving during the restart; services with an attached volume, and services without a health check, can be unavailable for a few seconds.
What moves
- Environments, services, deployments, volumes and custom domains.
- The project's spherelets. The receiving account pays for them from the transfer on.
- Secret managers that only this project uses. Their credentials stay encrypted and are never shown. To keep one out of the transfer, disconnect it first.
What the receiving account sets up again
- Builds from GitHub. A service that builds through the sending account's GitHub connection keeps serving its current image. Connect GitHub in the receiving account to build it again.
- Team access. Teams belong to an account, so team grants don't carry over. Grant access with the receiving account's teams.
- API tokens. The sending account's API tokens stop reaching the project. The receiving account issues its own.
- SphereGate bypass tokens stop working when the project moves. Create new ones under Access protection.
- Images the receiving account can't deploy. Such a service keeps running. Build it again in the receiving account before you restart, scale or redeploy it.
What stays with the sending account
- Audit and activity history up to the transfer.
- Invoices and usage up to the transfer.
- Its GitHub connections, teams and API tokens.
- Secret managers the project shares with other projects. The project leaves their lists.
What has to change first
Support tells you if one of these applies:
- Projects with SphereDB, SphereCache or SphereQueue services can't be transferred yet.
- Secrets that read from a secret manager that stays behind. Point them at another secret manager, or remove them.
- A suspended service, or a project on the sending account's Dedicated Compute.
- Log export destinations. Remove the project's log export destinations before the transfer. The receiving account adds its own afterward.
- The receiving account isn't ready: it isn't active, it has no room for the project's spherelets or SphereStor storage, or its trial or credit limit doesn't allow them.
A build or deploy that's running when the move is due delays it until that work ends.