Import settings


To configure Content Hub, you must either be a superuser or have the necessary permissions granted to you through user group policies.

The Excel import settings define how Sitecore Content Hub handles data imported from Excel spreadsheets. When importing an Excel file, ensure that the name of each worksheet matches the name of the corresponding definition. For example, if a worksheet contains asset data, it must be named M.Asset, and if a worksheet contains data about a taxonomy named BasicTaxonomy, it must also be named BasicTaxonomy.

Importing data from an M.Asset or M.File Excel worksheet initiates an import job that creates one fetch job and one processing job for each row in the worksheet. If the Excel file contains a self relation such as an option list or a taxonomy, its rows are imported in concurrent batches to improve the import speed.


If an imported Excel file includes any empty column fields, Content Hub uses default values for those fields.

Import jobs can have the following states and conditions:










You can cancel, resume, or check the status of import jobs in Background processes.

To configure the import settings:

  1. On the menu bar, click Manage cog icon.

  2. On the Manage page, click Settings.

  3. On the Settings page, select ExcelImportExport > ExcelImport.

You can configure the following settings:




The number of rows included in each periodic report for import jobs. The default value is 20, and the minimum value is 1. We recommend you use the minimum value if your Excel import is slow, as it can help you identify the rows that are slow to process.


The maximum number of rows allowed per Excel import. For example, if a file has 125,000 rows and the maximum number of rows is set to 25,000, then the import will throw an exception and not process the file. The default is 50,000.


The number of rows imported per target. Whenever this number is reached, a new M.Target is created.


This determines what happens if an error occurs during an Excel import. When enabled, this setting works differently depending on whether the import process is concurrent (batched) or sequential:

  • Concurrent: If an error occurs, the job ends when the current batch is completed.

  • Sequential: If an error occurs, the job ends immediately.

In either case, if the setting is disabled, any errors that occur during an import are recorded in the periodic report, but the import job will continue.


This setting can speed up the import process by as much as 300ms per row, but it also has the following effects for you to consider before enabling it:

  • In process triggers are ignored during the import.

  • Conditional members are not validated during the import. A property value is set even if the corresponding check would have failed.

  • Required members are validated as normal. A property value is not set if the corresponding check fails.

  • If the lifecycle status is included as a column, it is assigned to the standard relation instead of going through the security framework.


To avoid issues with mass edit in table operations, turn off the rawImport flag when the import finishes.

Do you have some feedback for us?

If you have suggestions for improving this article,