Bulk import of your enterprise models and assets

  • Release version: Zurich
  • Updated July 31, 2025
  • 4 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 Bulk import of your enterprise models and assets

    ServiceNow’s bulk import capability enables you to transfer multiple enterprise models and assets simultaneously into your instance using a subflow. This process supports both creation and update operations for models and assets, streamlining the migration or synchronization of data from external databases into ServiceNow.

    Show full answer Show less

    To start, you create an import record by downloading a spreadsheet template, fill in mandatory fields with valid data, and upload the completed template. The import triggers the EAM Bulk Import subflow, which copies data into staging tables, validates it, and then creates or updates records in ServiceNow.

    Modes and Templates

    The import supports several modes depending on your needs:

    • Create or update models only
    • Create or update assets only
    • Create or update both models and assets together

    Each mode corresponds to a specific downloadable spreadsheet template tailored for the data type(s) being imported:

    • Model template for model operations
    • Asset template for asset operations
    • Model and asset template for combined operations

    From the Yokohama release onward, the templates for asset-related modes include a MAC address field that populates the MAC address [macaddr] field in the Asset table upon successful import.

    Support for OT Asset Management

    When the OT Asset Management application is activated, you can bulk import hardware assets and models in both the Enterprise Asset and OT Asset Workspaces, but only if the OT entity column in the template is marked as TRUE. The Zurich release introduced columns for OT entity and Parent asset attribute (which lets you identify parent assets by asset tag, serial number, or MAC address) to assist in properly associating OT assets.

    Customization and Instructions

    You can customize bulk import templates by adding columns through:

    • Extending the staging tables to include new fields
    • Modifying the list view on the Database view table (sneamimporttemplate) to display new columns
    • Updating field mappings in the Model or Asset transform maps

    Instructions for bulk importing assets are accessible via the Bulk import instructions icon in the Enterprise Asset Workspace sidebar.

    Scheduled Jobs and Processing Flow

    The import process leverages scheduled jobs within the EAM Bulk Import subflow:

    • EAM Bulk Import - Upload File: Executes for all import modes to upload spreadsheet data to staging tables.
    • EAM Bulk Import - Transform Model: Executes for model creation or update modes, transforming model data.
    • EAM Bulk Import - Transform Asset: Executes for asset creation or update modes, transforming asset data.

    If you choose combined model and asset modes, the transform jobs for both run sequentially after upload.

    Staging Tables

    Data from the spreadsheet is staged in specific tables before final import:

    • Model Import Staging [sneammodelimportrow]
    • Model Component Import Staging [sneammcimportrow]
    • Asset Import Staging [sneamassetimportrow]

    This ensures data validation and structured transformation before creating or updating enterprise model and asset records in the ServiceNow instance.

    Use a subflow to import enterprise models and assets of multiple types to your ServiceNow instance at one go. You can also perform a bulk update on existing models and assets.

    Overview of Bulk import

    Use the Enterprise Asset workspace to do a bulk transfer of all your enterprise models and asset from a different database to the ServiceNow instance.

    Create an import record by downloading a template in the form of a spreadsheet (.xlsx). Ensure that you enter valid values in all the mandatory fields before uploading the template. Attach the template to the import record and select Import to begin the import process.

    After you select Import, the EAM Bulk Import subflow gets triggered. Scheduled jobs are initiated and data in the spreadsheet is copied to the appropriate staging tables. The staging tables are validated and records are created in the ServiceNow instance.

    Modes

    Modes refer to the type of import that you want to process. There are modes for only importing models, assets, and a combined mode for both models and assets. You can choose from the following available modes:
    • Create models
    • Update models
    • Create assets
    • Update assets
    • Create models and assets
    • Update models and assets

    Templates

    Based on the mode you select in the import record, you can download the corresponding template.
    Note:
    Ensure that you enter valid values in all the mandatory fields for the import process to run effectively. For a list of all the mandatory fields, see Mandatory fields in the bulk import spreadsheets.
    Table 1. Modes and templates
    Modes Corresponding template
    • Create models
    • Update models
    		 Model template
    • Create assets
    • Update assets
    		 Asset template
    • Create models and assets
    • Update models and assets
    		 Model and asset template
    Note:
    From the Yokohama release onward, the MAC address field is available in the Download template of the following Bulk import modes:
    • Create assets
    • Update assets
    • Create models and assets

    After a successful import, the MAC address that you provided in the template is added to the MAC address [mac_addr] field in the Asset [alm_asset] table.

    When the OT Asset Management application is activated, you can bulk import hardware assets and models in both the Enterprise Asset Workspace and the OT Asset Workspace only if the OT entity column is marked as TRUE.

    Starting with the Zurich release, the bulk import templates include OT entity and Parent asset attribute columns. When the OT Asset Management application is activated, you can bulk import hardware assets and models in both the Enterprise Asset Workspace and the OT Asset Workspace only if the OT entity column is marked as TRUE. With theParent asset attribute field, you can choose to identify the parent of a child asset using either the asset tag, serial number, or MAC address.

    To view instructions for bulk importing assets, select the Bulk import instructions icon on the contextual side bar.

    You can customize the templates to add more columns. Make the following modifications to add more columns:
    1. Add the new columns to the staging tables.
    2. Modify the list view on the Database view table [sn_eam_import_template] to include the columns you want to display in the spreadsheet. Enter the string sn_eam_import_template.list in the filter field on your instance's navigation bar.
    3. Add field mappings in the Model or Asset transform map.

    Scheduled jobs

    The following scheduled jobs execute as part of the EAM Bulk Import subflow.

    Scheduled jobs for bulk import

    The scheduled jobs execute based on the mode that you select.

    The EAM Bulk Import - Upload File job is executed for all modes. For the Create Model or Update Model modes, the EAM Bulk Import - Transform Asset doesn't execute. Similarly, for the Create asset or Update asset modes, the EAM Bulk Import - Transform Model doesn't execute.

    For example, if you select the Create models and assets mode, the scheduled job, EAM Bulk Import - Upload file uploads the data from the spreadsheet to the three staging tables. Then the Scheduled job, EAM Bulk Import - Transform Model executes the model and model component transform maps. After the model transform maps are complete, the EAM Bulk Import -Transform Asset scheduled job executes the asset transform map.

    Staging tables

    The data that you enter in the spreadsheet is copied to one or more of the following staging tables:
    • Model Import Staging [sn_eam_model_import_row]​
    • Model Component Import Staging [sn_eam_mc_import_row]​
    • Asset Import Staging [sn_eam_asset_import_row]​