CSV Imports

Modified on Tue, 30 Jun at 9:36 PM

CSV Import

How to bulk import and update records using the CSV Import tool in the Clew Platform


Contents


1. Introduction & Context

The CSV Import tool lets system administrators bulk upload or bulk update records across multiple modules in the Clew Platform, saving significant time compared to creating or editing records one by one.

Who is it for? System administrators responsible for data setup, migrations, or large-scale record updates.

What does it impact? Imports create or modify records directly in the Clew Platform and maintain a complete audit trail. Import actions cannot be undone once confirmed, so it is important to validate your data before running an import.


2. Key Features & Functions

  • Bulk record creation: Upload hundreds of new records at once instead of creating them individually in the platform.
  • Bulk record updates: Mass update specific fields on existing records using a unique identifier to match each row to the right record.
  • Automatic field mapping: The importer attempts to auto-map your CSV columns to system fields. Any columns it cannot match are flagged for manual mapping.
  • Validation before import: Run a check pass before committing any changes. The system identifies invalid rows, warnings, and unmapped fields so you can fix issues first.
  • Clone existing imports: Reuse the settings and field mapping from a previous import when bringing in data with the same structure.
  • Full audit trail: Every import is logged. Successfully imported records are linked directly from the import results view.

3. Requirements

  • Feature must be enabled: CSV Import is disabled by default. Contact Clew support to have it enabled for your organisation.
  • System administrator access: Only system administrators can access and run CSV imports.
  • CSV file format: The import file must be in CSV format with one record per row. The only exception is risk imports, where causes, consequences, and controls can be entered as multiple values within a single cell. The Clew Platform will create the separate linked records automatically.
  • Nested records require separate imports: If you need to import parent and child records together (e.g. Audits with Findings), these must be done as two separate imports. Import the parent records first, then use the Clew Platform ID assigned to each parent to link the child records in the second import.

4. Step-by-Step Guide

The CSV Import tool is located in the Import & Export section at the bottom of the Admin page.

The Import and Export section on the Admin page, with CSV Imports listed.

CSV Imports is found under the Import & Export section on the Admin page.

Note: If you cannot see CSV Imports in this section, the feature has not yet been enabled for your organisation. Contact Clew support to request access.

Creating New Records

Initiating a New Import

  1. Navigate to Admin > CSV Imports. This displays a list of all previous imports. From here you can also view, edit (title only), and clone existing imports.
The CSV Imports list page showing previous imports and the Add button in the top right.

The CSV Imports list showing previous imports and the Add button.

  1. Click Add and give the import a clear, descriptive title. For example: Create - Strategic Risks - Test Register.
The new import form with a title field filled in with an example name.

Give the import a clear title so it is easy to identify later.

  1. Select the module you are importing records into and click Save. You will be taken to the upload page.
Tip: If you have imported similar records before, use the Clone function to reuse the settings and field mapping from that import. Only use this when the CSV structure is identical to the previous import.
The module selection dropdown on the new import form before saving.

Select the module before saving to proceed to the upload page.

Uploading Your CSV File

  1. On the upload page you will see options to download a template for the selected module. Click Upload and select your CSV file.
The CSV upload form showing template download, file upload field, and delimiter selection options.

The upload form with template download, file upload, and delimiter options.

Tip: If you are unsure which column maps to which field, create one record manually in the system with all the required fields filled in. Export that record as a CSV and use it as your import template. The column headings will already match the system field names.
  1. The Template field is optional and only applies if you are using the template downloaded from this page.
  2. Select the correct Delimiter for your file. Available options are Comma, Pipe, Semicolon, and Tab. The delimiter defines the file format (e.g. a comma-separated CSV or a tab-separated TSV).
  3. Click Upload to proceed to field mapping.

Mapping Fields

  1. Click the Configure button to view and update the field mapping for your import.
The import configuration screen with the Configure button visible.

Click Configure to open the field mapping and import settings.

Note: On this screen you will see a field called Cell Separator. This is different from the Column Delimiter you selected on the upload screen. The Column Delimiter defines the overall file structure (e.g. CSV or TSV). The Cell Separator defines how multiple values within a single cell are split by the system. Choose a character that does not appear in your field content. If a comma appears in a Risk Description, for example, and the Cell Separator is also set to a comma, the system will split that description into two separate values. Use a pipe (|) or semicolon (;) as the Cell Separator when importing free-text fields to avoid this.
  1. The importer automatically tries to match your CSV columns to system fields. Columns it cannot match are shown with a grey background and will not be imported until manually mapped.
The field mapping screen showing columns with grey backgrounds that have not yet been matched to system fields.

Unmapped columns appear with a grey background and will be skipped unless manually mapped.

  1. To map a column manually, click its column heading. Select the appropriate system field from the dropdown and click Save. Leave Skip blank cells unticked for new imports (it is only relevant when updating existing records).
The column mapping dropdown open, showing a system field being selected for a CSV column.

Select the correct system field for the column and save the mapping.

  1. Once mapped, the column will display with a white background and show the name of the system field it is mapped to.
A column with a white background showing the system field name it has been successfully mapped to.

A successfully mapped column displays with a white background and the field name.

Handling Validation Errors

On the left side of the mapping screen you will see four system columns used to track and filter each row:

ColumnDescription
CheckboxSelect specific rows to import or update rather than processing all rows.
Row #The row number from your CSV file. This is not the system-generated ID that will be assigned to the record after import.
OperationUpdated after validation to show what action will be performed on that row (e.g. Create or Update).
StatusPending: Awaiting validation.

Valid: Passed validation and ready to import.

Invalid: Contains critical errors and cannot be imported.

Warning: Can be imported, but some fields contain issues and will be skipped.

Imported: Successfully imported into the system.

To validate and fix errors:

  1. Click the green Check button to run validation. The system checks every row and updates the Status column.
  2. Review the results. Hover over a status tag to see the detailed error message. Affected cells are highlighted in the grid.
The validation results screen with a status tag hovered to show the error detail, and affected cells highlighted.

Hover over a status tag to read the error detail. Affected cells are highlighted.

  1. To fix multiple rows at once, tick the checkboxes for the relevant rows and click the pencil icon next to the column heading. This lets you mass update the value across all selected rows.
Multiple rows selected with checkboxes and the pencil icon visible next to a column heading for mass update.

Select affected rows and use the pencil icon to mass update a value across all of them.

  1. Enter the correct values and click the green Check button again to re-validate.
The validation screen after corrections have been applied, showing rows now marked as valid.

After correcting values, re-run the check to confirm rows are now valid.

Importing Records

  1. Once validation is complete, switch from Check Mode to Import Mode using the toggle.
The Check Mode and Import Mode toggle, with Import Mode selected.

Switch to Import Mode before running the import.

  1. The button changes from green to blue and the label changes to Import. Click it to start the import.
Important: This action cannot be undone. Make sure all rows are valid before clicking Import.
The import action button shown in blue, indicating Import Mode is active and ready to run.

The Import button appears in blue once Import Mode is active.

  1. Successfully imported records will appear as hyperlinks labelled Create in the Operation column. Click a link to open the newly created record in the platform.
The import results with Create links in the Operation column for each successfully imported row.

Each imported row shows a Create link. Click it to open the record.

  1. Review the results. If clicking a link does not open the record, this usually means you do not have permission to view it. The import was still successful.
The import summary screen showing the number of rows imported successfully and the number that failed.

The results summary shows how many rows imported successfully and how many failed.

Updating Existing Records

Updating existing records follows the same process as creating new ones, with two key differences:

  • Your CSV file must include a unique identifier for each record (typically the system ID or Title) so the platform can match each row to the right existing record.
  • Mandatory fields are not required in the file. You only need the unique identifier and the specific fields you want to update. Make sure the identifier matches the existing record exactly to avoid update failures or unintended duplicates.

Steps to update existing records:

  1. Initiate a new import and upload the CSV file as described above.
  2. In the field mapping screen, confirm all columns are correctly mapped. The example below shows an update to the title, register, and review date of an existing risk.
The field mapping screen for an update import with title, register, and review date columns mapped.

Example update import with title, register, and review date columns mapped.

  1. Click the heading of the column you want to use as the unique identifier (e.g. ID or Title). Tick the Unique Identifier checkbox and click Save. A chain-link icon will appear on that column heading to confirm it has been set as the identifier.
A column heading displaying a chain-link icon to indicate it has been set as the unique identifier.

A chain-link icon on the column heading confirms it is set as the unique identifier.

  1. Click the green Check buttonto validate. Hover over each status tag to see the detail. The possible outcomes are:
    • Valid: Ready to import.
    • Warning: Will import, but the affected cell (highlighted yellow) will be skipped. Common causes include spelling errors or multiple values in a single-value field.
    • Invalid: Cannot be imported. This usually occurs when more than one matching record exists, or the record cannot be found and must be created with additional required fields.
Validation results for an update import showing rows with Valid, Warning, and Invalid statuses.

Validation results showing row statuses for an update import.

  1. Resolve all warnings and invalid rows, then re-run the check. Once all rows are valid, switch to Import Mode and click Import.
The import toggle switched to Import Mode with the blue Import button ready to run.

Switch to Import Mode and click Import once all rows are valid.

  1. Successfully updated records appear as Update links in the Operation column. Click a link to open the updated record and verify the changes.
The import results showing Update links in the Operation column for each successfully updated row.

Updated rows show an Update link in the Operation column. Click it to open the record and verify the changes.


5. Common Issues & Troubleshooting

IssueLikely CauseSolution
CSV Imports not visible in AdminThe feature has not been enabled for your organisationContact Clew support to request the CSV Import feature be enabled.
Columns showing grey after uploadThe importer could not auto-match those column headings to system fieldsClick each grey column heading and manually select the correct system field from the dropdown.
Rows marked as InvalidMissing required fields, typos, or unexpected characters in the dataHover over the status tag for the specific error. Common issues include missing Type, Register, or Title fields; spelling errors in lookup values; and leading or trailing spaces. Fix in the importer using the mass update tool, or correct the source file and re-upload.
Free-text fields splitting into multiple values unexpectedlyThe Cell Separator character appears inside the field contentChange the Cell Separator to a character that does not appear in your data, such as a pipe (|) or semicolon (;).
Update import row shows Invalid with no matching record foundThe unique identifier value does not exactly match an existing recordCheck for spelling differences, extra spaces, or case mismatches between the CSV value and the value stored in the platform. Correct the CSV file and re-upload.
Clicking a Create or Update link shows no recordThe current user does not have permission to view that recordThe import was still successful. Ask a user with the appropriate permissions to verify the record exists in the system.

Best practices:

  • Before importing, review your CSV file for completeness. Check that required fields are populated, values match the platform's expected format, and there are no extra spaces or special characters.
  • Always run the check pass and resolve all errors before switching to Import Mode. Imports cannot be undone.
  • For large imports, test with a small batch first to confirm the mapping and format are correct before importing the full file.
  • When importing nested records (e.g. Audits and Findings), always import the parent records first and use the platform-assigned IDs to link the child records in the second import.
  • Use descriptive import titles (e.g. Create - Strategic Risks - Q2 2025) so previous imports are easy to identify if you need to refer back to them.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article