Import & Export

Asset Manager supports bulk export and import of your entire asset inventory as JSON, as well as a PDF import workflow for populating assets from CONF-JIRA style documents. Full and selective export/import live under Asset Manager → Settings → Import / Export.

Exporting Assets

Full Workspace Export

Export produces a full JSON backup of all Asset Manager data, including:

All assets and their property values
All asset types and property definitions
All parent-child links

This is useful for backups, migrating data between workspaces, or inspecting your inventory programmatically. From Asset Manager → Settings → Import / Export, click Download full export to download the sanitized JSON file.

Selective Export

From the Tree View in Asset Manager, check one or more assets and click Export Selected (or Export All to export the whole tree) to download just those assets — with their descendants and the types/properties they use — as JSON. Use this to move a subset of your inventory into another workspace or environment without a full backup/restore.

Importing Assets

Full Workspace Import

Importing a full workspace backup replaces your existing asset data. All current assets, types, and properties will be removed before the import is applied. Make sure you have a current export before importing.

From Asset Manager → Settings → Import / Export, choose a previously downloaded full export JSON file under Full workspace import. VSEC will restore the full asset structure as it existed at the time of the export.

Selective Import

Upload a selective export (from Export Selected / Export All) under Selective import to create or update just those assets in the current workspace, preserving their parent-child structure. It applies immediately — there is no review step. Asset types and properties referenced in the file that don’t already exist in this workspace are created automatically, including the standard properties (Product Owner, Keywords, Interfaces) and, for common type names, an inferred parent type (Component under Vehicle, Variant under Component, Feature under Vehicle).

Firmware links and risks are never included in exports. After a full or selective import, relink firmware (e.g. via xZETA) on the imported assets to regenerate Country-of-Origin risks.

PDF Import

The PDF import workflow lets you create a Vehicle + Component asset structure from a CONF-JIRA style product document.

How It Works

VSEC parses the PDF for a set of known fields and uses them to build a proposed asset tree:

PDF Field	Maps To
Vehicle Line	Vehicle asset name + Vehicle Line property
Initial / Lead Model Year	Vehicle asset name + Model Year property
Project Name	Product ID property on both Vehicle and Component
ECU CS.##### (line)	Component asset name

The result is a two-level hierarchy:

Vehicle: <Vehicle Line> <Model Year>
└── Component: <ECU name>

Both assets are pre-populated with the extracted property values.

Re-importing

If you import a PDF for a vehicle that already exists (matched by Vehicle Line + Model Year), VSEC detects the existing asset and updates it rather than creating a duplicate. The same deduplication applies to components linked to that vehicle.

After Import

After the PDF is parsed, a proposed tree is presented for your review. You can edit the names and properties before confirming. Once applied:

The assets are created (or updated) in your inventory
The original PDF is automatically attached to the Vehicle asset as a file attachment

Last updated on September 18, 2026

Asset Details