> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/organizing-tests/projects.md). # Projects Discover BugBug's guide on organizing tests within projects. Learn effective strategies for seamless test automation management and maximize your testing efficiency. Start now! ## What is a project? Projects are a higher level "folder" for your tests, suites and schedules. Learn about it in [your first project section](/quick-start/your-first-test.md) of our quick start guide. ## Switching projects To switch to another project, open the project dropdown next to the BugBug logo in the top left and pick a project. To see all your projects, click the BugBug logo. This opens the **Your projects** list, where you can search projects by name and sort them by name, last modification, last cloud run, tests in progress, or queued tests. ![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FZ7OlWTN9U6KMP4esRbcv%2Fimage.png?alt=media\&token=1067c523-475a-4c12-bf78-91775271bf70) ## Creating a project Click **New project** on the projects list, or **Create project** in the project dropdown. Enter the project name and the homepage URL of the website you are going to test. The number of projects depends on your [subscription plan](/your-account/subscriptions-bugbug-versions.md). When you reach the limit, BugBug asks you to upgrade before you can add another project. {% hint style="info" %} If your organization has more projects than the current plan allows, the extra projects are marked **Limited** or **Inactive** and can't be opened until you upgrade. {% endhint %} ## Managing a project Open the **...** menu on a project card to: * **Rename** the project or change its homepage URL * **Duplicate** the project * **Export** the project * **Delete** the project ### Duplicating a project Choose **Duplicate** to make a copy of the project in the same organization. The copy has the same name as the original, so rename it afterwards to tell them apart. The copy counts towards the project limit of your plan. {% hint style="info" %} Duplicating a large project can take several minutes. The card shows **DUPLICATE IN PROGRESS** until it's done. If it takes longer than a few seconds, you also get an email when the copy is ready. {% endhint %} ![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FookJCkTTUIxR1lTpKyrN%2Fimage.png?alt=media\&token=87d8d8f7-7ebc-4669-8fae-9caa1009366e) ## Exporting and importing a project Choose **Export** on a project card to download the whole project as a ZIP file. The export contains the tests, components, suites, profiles, project settings, folder structure, and uploaded files. It doesn't contain run history. See [Exporting](/export-import-and-backup/exporting.md) for details. To bring a project back, click **Import** on the projects list and select the ZIP file. An import always creates a **new project**. It never overwrites an existing one. See [Importing](/export-import-and-backup/importing.md) for details. {% hint style="danger" %} An export contains secret values, such as passwords and secret profile variables, in plain text. Store it like a `.env` file. {% endhint %} ## Automatic backups On paid plans, BugBug backs up every project automatically once a day. There is nothing to set up. You can download a backup from **Project settings → Export & Backup** and restore it by importing it as a new project. See [Automatic backups](/export-import-and-backup/backups.md) for the schedule, how long backups are kept on each plan, and how to restore one. ## Transfer a project to a different organization You can move projects to another organization. This is helpful when you need to transfer tests to a different account managed by your client or a different department. Just ask our [support](https://bugbug.io/contact) and we will do it for you. Send us a link to the project you want to transfer and the link to the target organization. Please note that our support would need to authorize you before the transfer by sending an email with a confirmation request. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bugbug.io/organizing-tests/projects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.