A Configuration Management Governance team is transitioning from utilizinglegacy CMDB status fieldstoCSDM lifecycle status fields.

When organizations transition from legacy CMDB status fields (such as custom install status or operational status values) toCSDM-aligned lifecycle status fields, the goal is tomap old values to standardized lifecycle stageswithout disrupting existing processes. InServiceNow, this is achieved through theLife Cycle Mappingtable.

TheLife Cycle Mappingtable is specifically designed to translatelegacy or custom status valuesintoCSDM lifecycle stages and statuses. This allows organizations to preserve historical data and integrations while progressively adopting CSDM standards. By modifying this table, administrators can define how existing status values correspond to CSDM lifecycle stages such asPlan, Build, Deploy, Operate, and Retire.

TheLife Cycle Stagestable (Option A) defines the standard stages themselves and should not be modified, as these are core to CSDM governance.Life Cycle Stage Status(Option C) defines valid statuses within a stage and is also part of the standardized model.Life Cycle Controls(Option D) enforce governance rules but do not perform value translation.

Therefore, to safely transition from legacy status fields to CSDM lifecycle statuses, the correct and supported approach is to modify theLife Cycle Mappingtable, makingOption Bthe correct answer.