Exporting hierarchy process via JSON

  • Release version: Australia
  • Updated June 11, 2026
  • 2 minutes to read
    • Summarize
    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

    ServiceNow enables customers to migrate models and templates between instances by exporting their complete hierarchy and dependencies as a single JSON file. This export preserves system ID continuity between the source and target instances, ensuring seamless recreation of the hierarchy when imported.

    Show full answer Show less

    Key Features

    • Complete Hierarchy Export: The Export Hierarchy action generates a JSON file that includes the selected record (model or template) along with all dependent reference data and related records required for full functionality.
    • Included Components: Dependent reference data such as manufacturer details, product information, model classifications, currency, and pricing data are packaged. For templates, referenced models and their dependencies are also included automatically.
    • Role-Based Access: Export permissions depend on the record type:
      • Models: Roles with snnicore.inventoryadmin or snnicore.telcoinventorycatalogmanage can export models and their hierarchies.
      • Inventory Templates: Roles with snnicore.inventoryadmin or snnicore.inventorytemplatemanager can export templates along with their referenced models.
    • Single-Stage Export Process: Initiating the export from a model or template record triggers the system to gather all related and referenced records and package them into a JSON file, which becomes an attachment on the export request record.
    • Download and Import: Once the export completes, the JSON file can be downloaded and imported into the target instance using the JSON import feature within the Network Inventory Workspace.

    Key Outcomes

    • Preserved System ID Continuity: Maintains record identities between source and target instances, preventing issues with duplicate records or broken references.
    • Complete Dependency Transfer: Ensures all necessary reference data and related records accompany the models or templates, allowing them to function correctly after import.
    • Recommended for Cross-Instance Migration: This JSON export/import method is the recommended approach for migrating inventory models and templates between ServiceNow instances.

    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

    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

    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

    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 ensures the imported model on the target instance keeps its manufacturer link.

    Roles required for Export Hierarchy

    The role required for JSON export depends on what's being exported:

    Table 1. Permitted roles and their corresponding actions
    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.

    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

    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.