# Import your network topology

For on-premises customers, OneSite allows you to import your complete topology—including Locations, IP ranges, hierarchy, and types—using an Excel file.

You can download our sample files to use as templates for your topology import:

* [Sample-Input-Network-Topology-Import-Workflow.xlsx](https://adaptiva.com/hubfs/Docs/Sample-Input-Network-Topology-Import-Workflow.xlsx)
* [Sample-Input-Network-Topology-Import-Workflow-CIDR.xlsx](https://adaptiva.com/hubfs/Docs/Sample-Input-Network-Topology-Import-Workflow-CIDR.xlsx)

Modify the sample spreadsheet and store it on the Adaptiva server. In this example, the file name will be `C:\Adaptiva\NetworkTopology.xlsx`.

1. Navigate to **Workflows > Workflow Designer** in the Admin portal.
2. Select the **Utility Workflows** folder.
3. Right-click the **Import Network Topology From Spreadsheet** workflow and select **Launch**.

   ![](/files/8szLr6reHG6Z5hEy6dYW)
4. Enter the following values:

   **Excel File Location**

   ![](/files/agP9t5EGAY51SZSh6zHv)

   * **File path** -- Enter the path and filename for the .XLSX file which contains the network topology.
   * **Number Of Initial Header Rows To Be Ignored** - Enter the number of rows which should be ignored. Typically, this in only the first row that is used for column headers in the Excel file.
   * **Default Input**

   **Office Name and Description**

   ![](/files/KBeZyC8EW2KvrBnAGKhs)

   * **Column Number Which Contains Office Names** - Enter the column number that contains the office name and description that will be populated for each office in the Network Topology Perspective.
   * (Optional) **Add all the IP Address Ranges to the Description Field of Each Office** - Toggle **ON** to include the IP address range for each office in the office description.

   **Office Hierarchy**

   ![](/files/U7MPZkeK6Jlp1oLOvNqh)

   * **Column number which contains name of the parent office** - Enter the column number.
     * The row in the spreadsheet which represents the name of the Parent office should **match exactly** what is in the Network Topology Perspective, or a child office will be created.
   * **Automatically Delete Empty Offices Which Don't Have Child Offices** - Toggle **ON** if it is possible that the import results in empty offices.

   **IP Address Information**

   ![](/files/VqwQHO9nW6TuBKYir2Jl)

   * Select one of the following options:
     * **Spreadsheet contains IP Address Ranges**
     * **Spreadsheet contains Subnet Addresses and subnet masks**
     * **Spreadsheet contains CIDR**
   * Next, enter the column numbers which contain the information for each of the items.

   **Office Type Settings**

   ![](/files/e6KKsdbr5x4ugTzCirMI)

   * Enter the column numbers which contain VPN, WiFi, and Metered information.
5. Click **OK** to begin the import. Depending on the amount of data, the import may take time. Open the Network Topology Perspective to view your changes.

After importing a Network Topology from a spreadsheet, it is recommended that you review the logs for overlapping ranges. Some may have been removed from an office in favor of another due to the same range being incorrectly identified in the spreadsheet or associated with more than one office.

The log can be found in `<AdaptivaServerInstallPath>\Logs\Workflowlogs`. The log file name will start with Import Network Topology From Spreadsheet. When you open the log, simply search for `Removed Overlapping Range` to identify which offices and ranges require follow up.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.adaptiva.com/platform-guide/platform-management/network-topology/network-topology-import.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.