Optimizely uses the Optimizely asset system by default. To enable the _legacy_ asset management system, set the UseLegacyAssetSystem configuration setting to _true_ in the _web.config_ files of both the Commerce Manager and the front-end sites. Be aware that the legacy asset system is not available in Commerce version 11 and up. Also, Optimizely recommends using the [Service API](🔗) instead of Asset importer to import assets and link them to products.
## Download Asset Importer
The Asset importer is available on GitHub.
Browse to <https://github.com/episerver/AssetImporter>.
Clone the repository.
## Use Asset Importer
### Syntax of AssetImporter command
The command parameters
**mapping\_asset\_file**. A CSV file that contains mapping between products/variants and assets.
**asset\_folder**. The folder that contains assets to be imported.
**commerce\_core\_site\_path**. The physical path to the Commerce site.
**asset\_root \***(optional)\_: The name of the asset folder to which assets will be imported. If not provided, the default is \_Catalogs\*.
**-uselegacy \***(optional)\*. Indicates whether the AssetImporter uses the legacy asset system.
**-byasset \***(optional)\*. Indicates that the file structure from the asset\_folder is kept intact for the import. The default when importing is to create a structure with the products, groups and, finally, assets.
**-verbose \***(optional)\*. Enables detailed logging of the asset import process.
### Structure of CSV asset file
The first row of the file contains headers.
There are at least 2 columns in the file: the Catalog Node/Entry code and the asset file name. The first column is the Catalog Node/Entry code that the asset is associated with. But if the first header contains the word _asset_, the content of the first column is interpreted as the asset file name.
The third column is optional. It is the asset sort order if the Catalog Node/Entry has more than one asset.
**CSV file example**
If you have multiple groups in the asset folder, you only need to have one line in the CSV file. The import automatically imports files with the same name from the existing asset groups.
## Import assets as CMS-based content
Optimizely Customized Commerce can use the Optimizely asset system. To import using Asset Management as CMS-based content, use the following command:
If the CMS already has asset-based content, use the **-mappingonly** parameter to associate asset content with Catalog Node/Entry.
## Import assets as legacy ECF assets
Optimizely Customized Commerce can use the ECF BLOB Provider to manage the asset files and adding the asset to Catalog Node/Entry through the Asset tab in Catalog Management.
To import using the legacy Asset Management system, use the **uselegacy** parameter: