Importing Clients

To import Clients using the Inventory import, please select one of your Rollouts and go to Inventory -> Import then click on "New Import". Only users who are at least Rollout Manager can access and manage imports.

The import process is divided into three steps:

1. File and Inventory selection

2. Assigning the columns of the file to the Custom Fields of the Inventory

3. Summary and approval

---

1. File and Inventory selection

In the first step, please select the Inventory you want to import Clients into and the file that contains your Clients. The importer supports Excel and CSV:

Please be aware that active filters or hidden rows/columns inside of your Excel file as well as uncommon CSV delimiters might cause problems during the import. In case you are uncertain, please ask your Key Account Manager to review your file.

In case you are unsatisfied with the result of your import, you can duplicate your Inventory to keep the settings (Workflow and Custom Fields), delete the old one and repeat the import.

---

2. Column-Field assignment

In the second step you assign the columns of your file to the Custom Fields of the Inventory. Like this, the importer is able to create each row (Client) together with its Custom Field values:

To the left of the arrow, you will see the name of the column which should be defined in the first row of your file. To the right of the arrow you can select a default or Custom Field you want the importer to assign the values to while the Clients (rows) are being created.

Here is how the Excel file looked liked for the example above:

The first row must always contain the name/description of the column. The importer will not consider the first row as a Client.

Importing Default Fields

Every option that is above the gray line represents a default field. Some of them have certain requirements to be considered while importing them:

Default Field	Description	Requirements
Status	The Workflow status of the Client.	The value inside of your file must exactly match the name of one of your Workflow statuses for the import to succeed.
Assignee	The user (technician) to be assigned to the Client.	The user must successfully be found by Name, Email or Rollouter user ID for the import to succeed:
Client User	The end user owning the Client.	The user must successfully be found by Name, Email or Rollouter user ID for the import to succeed:
Name	The name of the Client.	A Client name can only occur once per Rollout.
Description	The description of the Client.	-
Client flag	A red note that is displayed on top of the Client.	-

Importing Multi-Selection fields / Client Groups

For Custom Fields of type Multi-Selection or Client Groups, the importer can interpret multiple values in one cell if you separate them with a comma.

Example: Client Group 1, Client Group 2

Updating existing Clients

When enabling the Update existing clients setting, the importer behaves differently:

• No errors are thrown anymore for rows where the Name already exists

  • The Custom Field Values of these Clients are then updated

• Clients that do not exist are still being created

To identify which Clients to update, the importer always uses the default field Name.

In this example we are updating the Client Groups of all existing Clients or create new ones.

Advanced Client Links

In case you are updating Clients with active Advanced Client Links, the importer takes care of two possible scenarios:

Scenario	Behaviour
There are conflicts between the file to import and your existing Inventory	✅ The values to import always have priority and the linked Clients will be updated
There are conflicts between multiple Clients withing the import file and the values are not equal	❌ The import fails with error feedback for each row of the linked Clients

3. Summary and approval

The third step summarizes your import:

Approval

Imports require an approval from another Rollouter Manager+ based on a 4 eyed principle. In case you are Administrator or the only Rollout Manager of the Rollout, you can approve the import yourself.

Import statuses

Imports have four different statuses which are explained below:

Status	Description
Incomplete	The second step (Column-Field assignment) is empty. It is required to import at least the names of the Clients.
Waiting for Approval	The import is ready to be started. After an approval, your file is processed based on your Column-Field assignment.
In Progress	Your file is being processed. Depending on the amount of rows, this step can take some time.
Failed	One or more rows could not be imported. The import was cancelled and no Clients have been created. Please read Resolving import errors below.
Completed	The processing was successfully completed and all Clients have been created.

Resolving import errors

After an import has Failed, you can make adjustments on your Column-Field assignment to resolve them and restart the import through another approval. If you made changes to your file or decide to select another Inventory, you need to create a new import.

In the summary of your import, all the failing rows are displayed together with the name of the column which caused the error:

Here, the column "Hostname" which was assigned to the default field "Name" was causing an error for rows 2, 3, 4, 11, 12 and 16.

The row number does not exclude the first row with the names of the columns. So the first Client row would be row number 2.

Reasons why importing a row can fail:

Field	Fail reasons
Status	The status to import does not match any of the Workflow statuses of the Inventory.
Assignee	The user was not found using the selected attribute (Name, Email or user ID) for the search.
Client User	The user was not found using the selected attribute (Name, Email or user ID) for the search.
Name	The Client name already exists inside of the Rollout project. ℹ️ In case it is appropriate, this can be resolved by enabling "Update existing clients".
Description	-
Client flag	-
Custom Field (selection or multi-selection)	The value you are trying to import does not exist in the corresponding Custom Fields' options. ℹ️ To resolve it, you can either add the value to the options of the Custom Field or check off the checkbox "Create option if not exists".
Shared Custom Fields (of Advanced Client Links)	Your file to import contains multiple Custom Field value updates for Custom Fields that are shared by an active Advanced Client Link. The import fails because each shared Custom Field to import needs to have the same value (applies only to directly linked Clients).