--- sourceDocument: Australia Telecommunications Network Inventory sourceDocumentLink: https://www.servicenow.com/docs/r/australia/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 via JSON # Exporting hierarchy process via JSON {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Exporting hierarchy process via JSON This process enables ServiceNow customers to migrate models and inventory templates between instances by exporting them and all their dependencies as a single JSON file. The export maintains system ID continuity, ensuring that the records retain their relationships and references when imported into the target instance. This method is the recommended approach for cross-instance migration of models and templates. Show full answer Show less ## Key Features * **Complete Hierarchy Export:** The Export Hierarchy action creates a JSON file containing the selected record (model or template) and its entire hierarchy, including all dependent reference data required for proper functionality. * **Included Dependencies:** Exported data includes manufacturer details, product information, model classifications, currency/pricing data, and any referenced models when exporting templates, ensuring all dependencies are intact. * **Role-Based Access:** Export permissions depend on the record type: * **Models and their hierarchy:** Requires `snnicore.inventoryadmin` or `snnicore.telcoinventorycatalogmanage` roles. * **Inventory templates and their referenced models:** Requires `snnicore.inventoryadmin` or `snnicore.inventorytemplatemanager` roles. * **Inventory Admins** can perform both export actions; Catalog Managers export models; Template Managers export templates and referenced models. * **Export Process:** Initiated from a model or template record, the system compiles all related and referenced records into a JSON file attached to an Export request record. Once completed, the file can be downloaded. * **Import Capability:** The exported JSON file can be imported on the target instance using the JSON import feature in the Network Inventory Workspace, recreating the hierarchy with preserved system IDs. ## Key Outcomes * Enables seamless migration of models and templates across ServiceNow instances while maintaining data integrity and relationships. * Preserves system identifiers to ensure smooth integration and continuity between source and target instances. * Ensures all necessary reference data is included, preventing broken dependencies after import. * Simplifies the migration process to a single JSON file export and import action, improving manageability and reducing errors. 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 JSON overview {#exporting-hierarchy-process-via-json__section_xzk_v3t_bjc} The Export Hierarchy action produces a JSON file containing the selected record and its complete hierarchy. This includes the dependent reference data the records require. You can import the JSON file on a target ServiceNow instance to recreate the hierarchy. System ID continuity is preserved between source and target. ## Components in JSON file {#exporting-hierarchy-process-via-json__section_bwy_bjt_bjc} A JSON export packages the selected model or template along with everything it depends on: * Dependent reference data: Any records the model or template references, such as manufacturer details, product information, model classifications, and currency or pricing data. * Inventory templates and their referenced models: When you export a template, the models the template depends on are included automatically {#exporting-hierarchy-process-via-json__ul_btt_gjt_bjc} The dependent reference data is included because the models and templates can't function on the target instance without their references intact. For example, an exported equipment model for a Cisco router includes the Cisco manufacturer record. This verifies the imported model on the target instance keeps its manufacturer link. ## Roles required for Export Hierarchy {#exporting-hierarchy-process-via-json__roles-required-export-hierarchy} The role required for JSON export depends on what's being exported: {#exporting-hierarchy-process-via-json__roles-required-export-hierarchy__entry__3} | Action | Roles permitted | Result | |-|-|-| | Export a model and its hierarchy | sn_ni_core.inventory_admin or sn_ni_core.telco_inventory_catalog_manage | The exported JSON contains models, child records, referenced records and related records | | Export an inventory template and its hierarchy (including its referenced models) | sn_ni_core.inventory_admin or sn_ni_core.inventory_template_manager | The exported JSON contains the templates, the model it references and the related recorde of both. | [Table 1. Permitted roles and their corresponding actions] Inventory admin can perform either action. Catalog Manager can export models. Template Manager can export templates and the models those templates reference. ## How Export Hierarchy via JSON works {#exporting-hierarchy-process-via-json__exporting-hierarchy-process-via-json-how-it-works} The JSON export process operates as a single-stage interaction. When you initiate the Export Hierarchy function from a model or template record, the system identifies the selected record together with all its related and referenced records. The system packages them into a single JSON file. The JSON file is generated as an attachment on the Export request record. After the export status shows Completed, you can download the JSON file from the right sidebar. You can transfer the downloaded JSON file to the target instance. Load it using the JSON import feature in the Network Inventory Workspace. Importing the JSON on the target instance recreates the model or template along with its complete hierarchy. System ID continuity is preserved between the source and target. This is why JSON export is the recommended path for cross-instance migration. The file contains everything needed for the records to function on the target instance, not just the records themselves. To learn the step-by-step procedure for exporting a model or template hierarchy as JSON, see [Import models and templates in JSON format](https://www.servicenow.com/docs/_heaO9S96gQBJ3z6nSwvdg "Create an import request to import your collection of models and templates in JSON format, and streamline the workflow using the Telecommunications Network Inventory application."). **Related tasks** * [Export hierarchy of models and templates](https://www.servicenow.com/docs/4pMbmgCgCjL0~h5kO4FYjw "Export a hierarchy of models, inventory templates, and all related records efficiently using the application.")