Migrate CI Attributes

Migrate CI Attributes

Migrating CMDB Attributes to Asset Additional Fields 

In earlier versions of ServiceDesk Plus (before version 15100) and AssetExplorer (before version 7700), all assets created in the Assets module were automatically treated as Configuration Items (CIs) in the CMDB, and vice versa. This included assets added manually, through scanning, or via file import. As a result, the same set of Asset additional fields and CI attributes appeared in both assets and CIs.
Starting from ServiceDesk Plus version 15100 and AssetExplorer version 7700, this behavior has been updated:
  1. Not all assets, users, or services are treated as CIs by default. Only the ones you configure as CIs will be listed in the CMDB.
  2. Asset additional fields will now be displayed only for assets in the Assets module.
  3. CI attributes will be displayed only for CIs in the CMDB module.
 
This change helps organizations manage only the assets and entities they choose to track as Configuration Items (CIs) in the CMDB.
 

Post-Migration Process

After you upgrade to the latest version, a post-migration process is required. This process:
  1. Creates a CI sync rule that syncs the child CI types under the Product Type. For example, child CI types under Router will be copied under the Product Type Router.
  2. Copies CI attributes from the child CI types as asset additional fields under the relevant Product Type.
 
This post-migration process ensures that existing information in the CMDB is properly copied to the Assets module.
Info
This post-migration process is a one-time activity. Once completed, it cannot be undone.

Steps After Migration 

After upgrading to ServiceDesk Plus version 15100 or AssetExplorer version 7700, the CMDB and Product Type pages under Admin will be temporarily locked until you complete the post-migration activity.
A banner will appear at the top of the screen, prompting you to start the post-migration process.
To complete the migration, follow these steps:
  1. Click Go for It on the banner. A post-migration pop-up window will open.
  2. Click Proceed to continue.  
 
  1. You will be asked to choose how the CI Attributes should be copied to the Asset module. Pick one of the following:
Please review your configuration carefully before proceeding with the migration. This process is permanent and can be done only once. Once completed, the changes cannot be undone. 

Choice 1: Migrate Entire Structure  

  1. All child CI types under the selected parent CI Type will be created as child product types.
  2. The attributes of each child CI Type will be copied as additional fields under the corresponding child Product Type.

Choice 2: Migrate Only Selected Attributes

  1. Child CI types will not be created as separate product types.
  2. Only the selected attributes from specific child CI types will be added as additional fields under the parent Product Type.
 

UI  Content

1. POP-UP

Migrating CMDB Attributes to Asset Additional Fields

In earlier versions of ServiceDesk Plus (before version 15100) and AssetExplorer (before version 7700), all assets created in the Assets module were automatically treated as Configuration Items (CIs) in the CMDB, and vice versa. This included assets added manually, through scanning, or via file import. As a result, the same set of Asset additional fields and CI attributes appeared in both Assets and CIs.
Starting from ServiceDesk Plus version 15100 and AssetExplorer version 7700, this behavior has been updated:
  1. Not all assets, users, or services are treated as CIs by default. Only the ones you configure as CIs will be listed in the CMDB.
  2. Asset additional fields will now be displayed only for assets in the Assets module.
  3. CI attributes will be displayed only for CIs in the CMDB module.
 
After you upgrade to the latest version, a post-migration process is required. This process:
  1. Creates a CI sync rule that syncs the child CI types under the Product Type. For example, child CI types under Router will be copied under the Product Type Router.
  2. Copies CI attributes from the child CI types as asset additional fields under the relevant Product Type.
 
This post-migration process ensures that existing information in the CMDB is properly copied to the Assets module.

This post-migration process is a one-time activity. Once completed, it cannot be undone. Kindly proceed with careful consideration. 

CHOICE ONE

Choice 1: Migrate Entire Hierarchy

  1. All child CI types under the selected parent CI Type will be created as child product types.
  2. The attributes of each child CI Type will be copied as additional fields under the corresponding child product type.
 
 
Let's assume you select the parent CI Type Router,
  1. It has child CI types Cisco Router and Netgear Router:
  2. These child types will be created as child product types under the Product Type Router.
  3. The child CI Type attributes will be synced as additional fields under the respective product types.
  4. A CI sync rule will be automatically created to associate each child CI Type with its corresponding child product type and map the CI attributes to asset fields.

CHOICE TWO

Choice 2: Migrate Only Selected Attributes

  1. Child CI types will not be created as separate product types.
  2. Only the selected attributes from specific child CI types will be added as additional fields under the parent Product Type.
 
In the above image,
  1. Let's assume ATM Router and Bank Router are under the parent CI type Router.
  2. ATM Router has an attribute called Flash Size, and Bank Router has an attribute called DRAM Size.
  3. If these attributes are selected, only these attributes (along with their data) will be added as additional fields under the Product Type Router.
  4. A CI Sync Rule will be automatically created to link the parent CI Type Router with the Product Type Router, and to map the child CI attributes to asset fields.

WARNING MESSAGES
Once you proceed, the configuration cannot be reversed, as the attributes will be copied to the respective modules.
 
In version 15 of ServiceDesk Plus, not all assets created in the Assets module will be categorized as CIs in the CMDB, and vice versa. Asset additional fields will now appear only for assets, and CI Attributes will appear only for CIs.
This migration process will assist you in moving CI Attributes to asset additional fields. Click here for more details.
This migration is a one-time process. If you skip it now, you won't be able to access it later.
 
 

    • Related Articles

    • CI Relationships

      CI relationships are a critical component of the CMDB. Without relationships, a CMDB is simply a collection of CIs added through scans, imports, or manual entries. With relationships in place, the CMDB provides valuable insights into how CIs are ...

    • CI Status

      CI Status CI status denotes the current state of a CI in an organization. Admins can monitor the health and other attributes of CIs by configuring CI Status. AssetExplorer comes with certain default statuses such as Clear, Not Monitored, Attention, ...

    • CI Relationship Map

      A relationship map helps you visualize relationships between a base CI and other (related) CIs. The relationships between the CIs are discovered automatically when they are populated into the CMDB. Using the map, you can view the number of pending ...

    • Create CI Type

      Create CI Type You can define new CI types to match your business needs. On the configuration item type list view, click New. Provide the following information under the Details tab on the New CI Type form. Enter a unique display name and display ...

    • Modify Software CI Type

      You can modify the CI type of software applications directly from the list view. Role Required: SDAdmin, Technicians with Complete Access to Assets. Go to Software > Scanned Software. Select the software application(s) whose CI type should be ...