Life cycle mapping / install base items

[Tanja Holm]

Hi, 

struggling with Life cycle mapping and investigating how it is intended to be used. OOTB the only life cycle mapping available for legacy state in use is Install Base Item - Operational - In Use. However, I want the customer to be able to update the lifecycle status to "in warehouse", the legacy state still being "in use". It seems that it's not possible to have one legacy state corresponding to more than one lifecycle statuses. 

What is the best practice here? I see that it's possible to create new legacy states, but is that really the way to go here? Thankful for pointers, references to information sources etc.

Best regards

Tanja

[pr8172510]

Hi @Tanja Holm,

Lifecycle Stage and Lifecycle Status are the preferred asset state model, while legacy states are maintained for backward compatibility.

Creating additional legacy states is generally not necessary unless required by a specific business process.

Best practice is to:

Use Lifecycle Statuses (for example, In Warehouse, In Use) for operational tracking.

Keep legacy states as generic as possible.

Use Lifecycle Stage/Status as the primary state model.

ServiceNow's recommendation is to manage asset progression through Lifecycle Stage and Lifecycle Status, rather than extending legacy states to represent every business state.

[Tanushree Maiti]

Hi @Tanja Holm 

refer :

Synchronizing the install base life cycle fields with the state and status fields 

Clarification on CSDM Lifecycle Mapping : LifeCycle Stage & Lifecycle Status 

CSDM 4.0: (any) Status attribute vs. Life cycle

[Venky Kshatriy2]

Hi @Tanja Holm 

• Don’t create new legacy states (install_status) unless absolutely required, as they impact core platform logic.
• Best practice is to extend Lifecycle Status/Substatus and map them appropriately.
• One legacy state (e.g., In Use) can map to multiple lifecycle substatuses (e.g., Active, In Warehouse).
• However, align business meaning—“In Warehouse” is usually better mapped to “In Stock”, not “In Use”.
• Focus on keeping legacy state stable and use lifecycle fields for flexible business representation.
  
  If this response addressed your question, please mark it as Helpful and accept it as the solution.

[Tanja Holm]

Hi, thanks for taking the time to answer. I see you're writing that one legacy state can map to multiple lifecycle substatuses. That's what we're not getting to work, it seems blocked by an OOTB business rule preventing more than one mapping entry from one legacy state.