Custom Inventory Importer

Custom Inventory Importer is a command-line interface (CLI) tool that allows you to upload custom inventory data into Flexera One IT Visibility for processing, just like any other data source. This tool allows you to test out ideas or demonstrate the platform's capabilities.

How to use the Custom Inventory Importer

To use Custom Inventory Importer, you'll need: 

• Access to the Flexera One organization that you intend to import custom inventory into

• A valid Flexera IAM Refresh Token for API authentication and authorization

• A custom inventory file that conforms to Flexera One common ingest format

• A Windows or Linux machine that can connect to your Flexera One organization UI

Obtain a Flexera IAM Refresh token for use with the CLI

1. Log into Flexera One and navigate to User Settings / API Credentials.

2. Select the Create API Refresh Token button.

3. Copy the token and note it for later use.

 

Get a copy of the Custom Inventory Importer

• For Windows, see attachment ciImporterSigned-2026-07-16.zip
• For Linux, see attachment ciImporter4Linux-2026-07-16.zip

You'll use a different executable depending on your environment, but the same parameters are supported in both. For example, the following two commands will do the same thing, but you'll need to substitute the path parameters for those in your chosen environment.

• Windows

  ciImporterSigned.exe import template --out c:\imports\template

• Linux

  ./ciImporter4Linux import template --out ./imports/template

Get a CSV Template to populate

You can use the tool to build a CSV template that the importer supports to convert from. Execute the tool with the following CLI parameters:

  import template --out <folder or new zip file to create>

Depending on what you specify, this action will either create a folder, populate an empty folder, or create a zip file. The folder will contain a series of expected CSV files, with the first row in each specifying the type of data it expects.

• See the attached file SampleCSVs-2025-08-05.zip for some examples of the expected CSV files.
• For the description and data format of each CSV field, see the attached file CSV Fields Descpription-2026-07-16.pdf.

IMPORTANT: Including the following file types is essential when preparing the CSV files. However, only the "Computer" related CSV files require mandatory data. In contrast, non-computer-related CSV files do not need data but must contain their respective field headers.

• BusinessService

• Computer

• InstallerEvidence

• OSEvidence

• Virtualization

Convert the CSV to the Common Ingest format

To convert your CSV data into the Common Ingest format, prepare the source CSV files in a folder or ZIP archive and run the following command:

/path/to/importer import convert  --in <input folder or ZIP containing the CSV files> --connectionName <source name> --orgId <organization ID> --out <output ZIP file>

The conversion process automatically validates the input files for:

• Required (mandatory) fields
• Duplicate or non-unique records

If validation fails, review and correct the reported issues in the source CSV files, then rerun the command. Once validation completes successfully, a ZIP file containing the Common Ingest–formatted files will be generated at the location specified by the --out parameter, ready for import.

Upload the generated package

Once the Common Ingest ZIP file has been generated, upload it using the following command:

/path/to/importer upload --connectionName <connectionName> --file <CommonIngest ZIP file> --orgId <orgId> --refreshToken "<my-token>" --region <account region>

After the upload completes successfully, please note the following:

• The imported data will not appear under External Inventory Connections in the UI.
• It may take up to 24 hours for the imported data to become visible in IT Visibility (ITV).
• Retain the Trace ID, connection name, and the uploaded ZIP file for troubleshooting purposes. These details will be helpful if you need to contact Support regarding the import.

Parameters supported:

Current Limitations

It's recommended to use the same connectionName for the same org so that the newer uploads overwrite the old. 

Upcoming Features

• Upload straight from CSV source (avoid conversion step)
• Simpler CLI