Share This:

Hello Remedyforce CMDB 1.0 users! As the Summer season (in the US of course) begins to wind down and Pumpkin Spice lattes will be available soon, it’s time for a change for you folks as well. As of our upcoming Spring 16 release of Remedyforce, CMDB 1.0 will be going end of life. As a recap, CMDB 1.0 going end of life means:


  • No further development from Remedyforce Product Management will be done on CMDB 1.0
  • No defects will be addressed going forward by the Remedyforce Engineering team
  • There are a multitude of benefits to realize with migration to CMDB 2.0 so we want you to take advantage of all the benefits!


We first introduced and released CMDB 2.0 in our Remedyforce Winter 14 release back in March of 2014. In CMDB 2.0 all Configuration Items are now saved in the Base Element object meaning the CMDB was flattened in Winter 14 release and all the classes in CMDB are implemented as fields sets of the Base Element object and attributes are the fields. So what does this mean for you and what are the benefits of this?


  • Less storage space is required to store a CI record
  • Import and export of data is much faster
  • Adding custom fields to a CI is much easier
  • Reports can be created which access more than a single CI type
  • Any field of any CI type can be tracked which makes auditing tasks much easier
  • Any field of any CI type can be searched
    • CMDB 1.0 search was restricted to the field of either BE or Business Services
  • Fields shown on the General and Specification tabs within the CI instance editor can be customized
  • New Pentaho packages were introduced to allow for importing data from other products (appended with 2.0)


Included in this blog is a Remedyforce Value Enablement Kit that provides an overview of the straight-forward migration steps, and provides you with a screen by screen walk through of the migration process thanks to Haritha Kodali!


The intention of the Kit is not to guide you to configuring the CMDB, but rather, how to migrate to CMDB 2.0; some planning that should be reviewed first and then the actual steps to migrate.


I recommend reviewing the Winter 14 Upgrade Guide documentation for more details on CMDB 2.0 prior to the migration.

As always, please don’t hesitate to reach out to if you have questions or require additional assistance. Happy migrating!