Manage, transfer, export, and restore projects
Project-level actions are separate from changing source code. Read each confirmation screen because archive, transfer, remix, and export have different effects.
Archive and restore
An owner can archive a project from the Studio project list. Archiving removes it from the active list and starts the cleanup/retention state shown by the page; it is not the same as immediately deleting all records. Open the Trash view to inspect the cleanup or purge deadline. Restore is available only while the project remains recoverable and no purge is in progress. Restore promptly if you archived the wrong project.
Transfer ownership
Use the transfer action to review eligible destination organizations and a transfer preview. Confirm the source, destination, project access, data, and integrations that the preview says will move or remain. Acknowledge the explicit transfer summary before confirming. Transfer can change who controls the project; do not use it as a route switch.
Remix or create a copy
Remix creates a separate project from eligible source material. Review the new project name and whether development database data or secrets are copied. Integrations, authentication configuration, deployment, or conversation history may be handled differently from source code. Never copy production secrets or data without authorization.
Export source
Use the Code export action when available, review the checkpoint or export ticket, and download the generated archive only after the page reports it is ready. Verify the selected source version. An export does not include external service accounts or guarantee that a project can be deployed outside BuildWhat without additional configuration.