Skip to content
  • There are no suggestions because the search field is empty.

Tree structure export- and importmodule

By exporting the tree structure to Excel, you can easily modify it by making changes, adding new folders and/or objects, or removing rows. This allows you to efficiently update the tree structure.

The tree structure can easily be built using this Excel file. The layout of the Excel file largely follows the logic of the actual tree structure. Just like in ControlOffice, the Excel can contain both folders and objects. Whether a row represents a folder or an object is determined by column A—if column A contains a unique object code, the importer knows to create a link to that object instead of creating a folder.

The tree structure is built visually, starting from cell B2. Each deeper level of the tree should be placed on a new row, with only one column filled per row.

Example:

  • The root folder is “Company X” on B2

  • Inside that is a folder “Department A” on C3.

  • Inside “Department A” is an object with object code “L01” on D4 (this code is entered in column A4)

  • “L01” contains 9 sub-objects (E5 to E13), each with their own object code in column A5 to A13

This setup allows the Excel to represent the visual and functional layout of the tree.

If a row is removed in the Excel file, that row will also be removed from the tree structure in ControlOffice after the import. The Excel must remain structurally consistent — you cannot skip a level or create an invalid hierarchy, such as jumping from column C in row 3 to column E in row 4 and skipping column D.

Basic rules for importing:

  • Do not modify the format of the Excel file:
    Do not change column titles, remove columns, rename or delete tabs, or otherwise alter the structure of the file.

  • Required fields in ControlOffice are also required in the Excel file.
    For example, uploading a cost center without a code will result in an error. Required fields are marked with a red background.

First create a small part of the tree manually in ControlOffice with a few objects and folders.Then export it to Excel to generate example rows you can build on.

The import runs as a background task, so you can continue working in ControlOffice. Depending on the data volume, it may take some time. If desired, a notification can be sent via email when the import starts and finishes. Any errors during the import will be listed in the email.