If you are in Site Administrator and rt-click on a project you can perform an ''export'' of that project.

This will generate a ''QCP'' extension file (actually a ZIP).
This file will be SPECIFIC to your version of QC and can only be imported to the SAME version of QC.

the QCP file contains all of the information it needs to re-create your project (repository, DB and everything). It is also ''database agnostic'', meaning that it can be imported to a server using EITHER SQL-Server or Oracle.

You might want to use the QCP file to migrate a project from one QC11.52 server to a DIFFERENT QC11.52 server, for instance.

BEWARE, though of trying to re-import the SAME project from a QCP file to a server that has the original project (a round-trip). The QCP contains a ''dbid.xml'' file that has the unique ID (GUID) for the original project. If you try to re-import, QC will sense the ID is the same and will ask if you want to overwrite. To avoid confusion and overwriting, you can edit the DBID.xml that is in the QCP (rename to ZIP, open file for edit, save, then rename back to QCP) and blank out it's GUID.

QCP-Project SIZE warning: Due to the Export process using a 32-bit zip-compression routine, the combined size of the project's repository + Database cannot exceed 2.5GB. Large projects cannot be exported to QCP files.

QCP-Pending Repository Migration warning: If you have a project that was upgraded from a version prior to QC11, it might not be able to be exported to QCP because it is has a pending (unfinished) repository migration. If you get this error, look in the Site Admin Tools/Repository Migration Status for any projects that are not 100% migrated. If you have any, re-run/resume migration for the project and look at eh log window for what it dies not like and fix it. Sometimes a project may be in this ''pending'' status for months or years.