---
sourceDocument: Australia Telecommunications Network Inventory
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/telecom-network-inventory

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecommunications Network Inventory

ft:clusterId :

    - telninv

bundleId :

    - telninv

workflow :

    - Customer and Industry


---

# Export hierarchy of models and templates

# Exporting hierarchy of models and templates {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Export equipment models, inventory templates, and related records to support development-to-production migration of network inventory data.

## Exporting hierarchy of models and templates {#exporting-hierarchy-of-templates-and-models__section_ms4_kft_bjc}

The Export Hierarchy feature lets you export network equipment models, inventory templates, and their related records from a ServiceNow instance, in a format suited to your purpose. Use this feature to promote validated configurations from a lower environment to production, to share model catalogs with partners or
stakeholders, or to extract specific records for analysis.
{#exporting-hierarchy-of-templates-and-models__table_mll_sht_bjc__entry__2}

| Your scenario | Use this method |
|-|-|
| You need to preserve the relationship records as a single package. | Exporting hierarchy via JSON |
| You need to export specific related records of a model or template in a chosen format. For example, exporting equipment data as CSV for analysis, as PDF for a stakeholder review, or as XML for selective re-import. | Exporting hierarchy via XML (or other selected format) |
[Table 1. Choosing an export method]

{#exporting-hierarchy-of-templates-and-models__table_mll_sht_bjc}

Both methods are launched from the Export Hierarchy action on a model or template record. The method you use depends on whether you select Export Hierarchy directly from a record's context menu (JSON method) or use the
related-records list (XML or other-format method).
{#exporting-hierarchy-of-templates-and-models__table_ghg_lgt_bjc__entry__2}

| Role | Action performed on "Export Hierarchy" initiation |
|-|-|
| sn_ni_core.inventory_admin | Generates a JSON file packaging the hierarchy |
| sn_ni_core.telco_inventory_catalog_manager | Generates a JSON file packaging the hierarchy |
| sn_ni_core.inventory_template_manager | Generates a JSON file packaging the hierarchy |
| Platform admin (no TNI roles) | Shows the related-records list is export as XML. Multiple records are exported as one single XML. |
[Table 2. Export Hierarchy behavior by role]

{#exporting-hierarchy-of-templates-and-models__table_ghg_lgt_bjc}
**Related concepts**   

* [Exporting hierarchy process via JSON](https://servicenow-prod.fluidtopics.net/oqWHwiD_YYWaDNpFb1rBLg "Learn how to migrate models and templates between ServiceNow instances by exporting them with all their dependencies as a single JSON file. The export preserve system ID continuity between source and target.")
* [Exporting hierarchy via XML](https://servicenow-prod.fluidtopics.net/sF_HeAuJ8~T4zcPlyE6krA "Learn how to export a model or template and its related records as XML files for transfer to another ServiceNow instance.")