CSV Export
A guided ETL wizard for exporting CMDB data to CSV files. Define column mappings, select the target asset type, and generate downloadable exports — ideal for sharing data with external teams, feeding downstream tools, or creating offline backups of your migration inventory.
Overview
The CSV Export module is the counterpart to CSV Import. While CSV Import brings data into Clarity, CSV Export extracts data out — generating well-formed CSV files from the CMDB that can be shared with stakeholders, loaded into external tools, or archived for compliance.
The wizard guides you through uploading a template that defines the desired output structure, mapping CMDB fields to export columns, and running the export to produce a downloadable file.
When to Use CSV Export
Prerequisites
CSV Export requires Administrator or Project Manager access. You need data already populated in the CMDB — export works against the live database.
- CMDB populated with data. The export wizard queries live CMDB records. If the target asset type has no records, the export will produce an empty file.
- A CSV template file (optional). You can upload a template that defines the desired column structure. Alternatively, you can build column mappings from scratch in the wizard.
- Target asset type identified. Know which CMDB asset type you're exporting (Device, Application, Database, etc.) before starting the wizard.
Step 1 — Upload Template
Navigate to Integrations → CSV Export → New Export to open the wizard.
Choose the CMDB asset type to export (e.g. Device, Application, Database) from the dropdown.
If you have a pre-defined CSV template with the desired column headers, upload it here. The wizard will use the column headers to pre-populate the mapping step. If you don't have a template, skip this and build mappings manually.
Proceed to the column mapping step. The wizard unlocks subsequent steps as each prerequisite is completed.
Step 2 — Column Mapping
Map each desired output column to a CMDB field. This determines which data appears in the exported CSV.
For each column in the output, select the corresponding CMDB field from the dropdown. If you uploaded a template, the column names are pre-populated from the template headers.
Columns set to Ignore will not appear in the exported file.
Click Save Mappings to persist the column configuration. Once saved, the Run Export step is unlocked.
Step 3 — Run Export
Confirm the asset type and column mappings displayed on the summary screen.
Click Run Export to generate the CSV. A progress indicator shows the export status. When complete, the file downloads automatically.
The generated CSV is timestamped (e.g. device_export_2026-04-01_09-30-00.csv) and downloaded to your browser's default download location.
Managing Export Definitions
All saved export definitions are listed on the CSV Export index page. From here you can:
- Re-run a previously configured export with one click.
- Edit column mappings to adjust the output structure.
- Delete export definitions that are no longer needed.
Example Workflow
A project manager needs to send a weekly spreadsheet of all in-scope devices to the infrastructure team. She creates a CSV Export definition targeting the Device asset type, maps columns for Name, IP Address, OS, Environment, Owner, and Migration Status, and saves the configuration as "Weekly Infra Report".
Each week, she opens the CSV Export page, finds the saved definition, clicks Run Export, and downloads the latest data in seconds — no re-mapping required.
Tips
If you run the same export regularly, save the definition once and re-run it each time. This eliminates the need to reconfigure column mappings and ensures consistent output format.
- Use scope filters before exporting. If your CMDB contains both in-scope and out-of-scope records, apply scope filtering to ensure the export only includes relevant data.
- Map only the columns you need. Including every CMDB field creates large, unwieldy files. Map only the columns your downstream consumer requires.
- Use human-readable column names in templates. The exported CSV uses the template header names. Using clear, descriptive names makes the output immediately useful without post-processing.
Common Mistakes & Troubleshooting
- Empty export file. If the exported CSV contains only headers and no data rows, check that the target asset type has records in the CMDB and that any scope filters are not excluding all records.
- Missing columns in the output. If expected columns are missing, re-open the column mapping step and verify that all desired fields are mapped (not set to Ignore).
- Wizard steps remain locked. The wizard enforces sequential completion. If a step is greyed out, complete the prerequisite step first (upload template → save mappings → run export).