Migrate CI Attributes to Asset Additional Fields - 15100
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:
- 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.
- Asset additional fields will now be displayed only for assets in the Assets module.
- 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:
- 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.
- 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.
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:
- Click Go for It on the banner. A post-migration pop-up window will open.
- Click Proceed to continue.
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
- All child CI types under the selected parent CI Type will be created as child product types.
- 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
- Child CI types will not be created as separate product types.
- Only the selected attributes from specific child CI types will be added as additional fields under the parent Product Type.
