About Exporting and Importing

Code Insight provides export and import functionality for project data. The export-import process can be performed on the same server or across servers. Project data can be quickly imported into an empty project to create inventory or imported into a scanned project to create inventory with file associations. The imported inventory in both cases is “live”—that is, ready to be reviewed and edited.

Export and import functionality is useful in any of these following scenarios:

•

Backup of project and audit data—Use export to create a full backup of a Code Insight project. The backup data file includes project and scan details, all inventory (with inventory details, field values, file associations, and inventory review status), the review status of files, and any custom data. The project data can be restored to a new project for an archived view or for ongoing scanning and auditing.

•

Copying or branching a project—Use the export-import process to create an exact copy of a project for future scanning and audit work. To do this, export the data from the source project, scan the target project (pointed to the same codebase), and import the data into the target project. The target project can be used for continued scanning and analysis work while the source project remains unchanged.

•

Versioning a project—Use the export-import process to apply analysis work performed on one product version to the next product version. For example, you can apply the analysis work performed on project “foo-v1” to project “foo-v2”. To do this, export the data from “foo- v1”, scan “foo-v2”, and import the data into “foo-v2”.

•

Audit work reuse—As in the versioning example above, you can use the export-import process to apply analysis work performed on one project to another project containing a subset of similar files. Export data from “project1”, scan “project2” (pointed to “project2” codebase), and import the data into “project2”. Likewise, this process can be used to apply analysis work from several different projects to the current project.

•

Sharing of live audit results between teams—Use the export-import process to share live audit results between teams or with Revenera Professional Services. For example, you can export data from “project 1” on “instance 1” and import the data into “project 2” on “instance 2”. Results are imported either into an empty project for a live view of inventory or into a scanned project for a live view of inventory with file associations and access to the codebase file tree.

Note:An empty project is one to which no codebase has been uploaded or synchronized or that has not yet been scanned.

•

Migrating audited projects from Code Insight v6 to v7—Use the import process to create live project inventory in Code Insight v7 from an exported v6 project or workspace data. After exporting data from a v6 project, run the Audit Data Migration Tool (available for download in the Product and License Center) to map inventory fields from Code Insight v6 to v7 and to convert the exported data to the proper JSON data format required for import into v7. Then perform an import into a Code Insight v7 project. Import into an empty project (see note for previous bullet) for a live view of inventory only or into a scanned project for a live view of inventory with file associations.

•

Creating inventory from an external system—Use import to create project inventory in Code Insight from a data file containing legacy or external data. This type of import requires the conversion of the legacy data to the required JSON format prior to importing into the new project.