Skip to main content


Import is an efficient method when you have a lot of information that needs to be registered in Snow License Manager, for example, license purchases.

Data can be imported manually on an occasional basis, or automatically on a regular basis. Manual imports are performed in Snow Management and Configuration Center or in Snow License Manager, while automated imports are scheduled via the Web Configurator tool.

Manual imports

The import functionality in Snow Management and Configuration Center is wizard-based and allows for import of new objects as well as update of existing objects in the Snow License Manager database. You can import information to the standard fields in Snow License Manager and to most custom fields applicable to the category. The exception is custom fields of the type currency.

There is also a dedicated wizard for import of agreements and licenses from Microsoft License Statements (MLS). For more information, see Microsoft License Statements.

Source files

The source file of the import can be in Excel format or CSV format. You can use import files both with and without a file header.

The names of the columns in the header of the import file do not have to match the names of the destination fields in Snow License Manager. Mapping of source and target fields is done in the Field mapping step of the import wizard.

For a successful import of new or updated information in Snow License Manager, certain information must be provided in the import file. For detailed information on the required data and where the data can be found in the user interface of Snow License Manager after the import, see Data Import Field Description.

Mapping of source and destination fields

In one of the steps of the data import, you map the column names in the import file to the corresponding destination fields in the user interface of Snow License Manager. If the import file has no header, you can use index mapping instead. This means that you map each column by its position in the source file (0, 1, 2, etc.) instead of its name.

Validation of data

The preview step of the import validates the data before you import it. This is to verify that only allowed data types and values are included in the import file. Errors, like conflicts or invalid values, are highlighted in red and you can point to the fields to see more information on the errors.


  • If you run an import of data for existing objects, for example, computers or users, these objects must already exist in Snow License Manager.

  • Any errors and conflicts that are highlighted in red in the preview step will prevent the import.

If the basic setting ALLOW_INCOMPLETE_LICENSES is enabled, fields that are missing the required license information are highlighted in yellow.

For licenses, the import also verifies that the Stock-keeping unit (SKU) matches the entered license settings. Data that differs from what is expected is highlighted in yellow.

Example 19.

The metric of an application is defined by its SKU. If the import data does not match the expected metric, there will be a warning and you are given a chance to change the unexpected value in the source file before continuing with the import. It is possible to continue with the import even without changing, but note that there will be a mismatch in the database.

Automated imports

For automated and regular imports of data to Snow License Manager, you can use the File Import Service. The service is configured in the Web Configurator tool. For more information on the Web Configurator, see Appendix A – Web Configurator.

You need to configure one import folder for each type of import, and the settings will apply to all imports of the same type.

When you have configured the import folders, the Import Service will automatically look for and import data from files dropped in these folders. The files will be processed according to rules defined in the configuration.

For successful data imports, certain information must be provided in the import files. Required fields depend on the type of import. For more information, see Data Import Field Description.