Skip to main content

Transformations that involve an application change

  • August 26, 2026
  • 3 replies
  • 44 views

Hi, we have a scenario where we create a transformation that involves decommissioning an existing application and moving to another application.  The existing application is in our CMDB and flows to LeanIX.  However, the to-be application is not yet in CMDB.  When the transformation runs it creates the new application, as expected.  Then later the new application gets created in CMDB and flows to LeanIX so now that application is duplicated.  Is there a way to “swap” the application that was created from the transformation with the one from CMDB?  Seems like the only way is to delete the app created by LeanIX but then all of the integrations, capabilities, etc. will be decoupled, then I have to re-create them.

3 replies

Giannis Antoniou
Forum|alt.badge.img+3

Hi,


What are you afraid it would happen if you moved the data from one fact sheet another then delete the one from the transformation?

I mean I am sure you are locating a potential problem but it’s a bit difficult to understand the possible problems this might cause without knowing your integrations and without knowing if your CMDB is OOTB with ServiceNow or something custom etc.

If you are anxious I suggest you open a ticket with support, since they will have the ability to move and set external IDs etc.

Stephan Hofmann
Community Manager
Forum|alt.badge.img+1

Hello ​@KSS,

Thank you for your question! As ​@GiannisAnt already rightly pointed out, it's difficult to know the best possible path forward for your unique case from the scenario alone, and currently there is no such functionality for merging or swapping fact sheets available in the product.

Feedback on this is always best placed directly on our Roadmap so the relevant team can see the gap and keep you informed as the idea progresses through the different stages.

In the meantime, if the CMDB sync hasn't yet created the duplicate, there may still be a window to set the External ID on the transformation-created fact sheet to match the CMDB identifier. Depending on your integration setup, this could allow the integration to recognise the existing fact sheet and update it rather than creating a new one.

As a preventative recommendation for the future, I'd also invite you to review our documentation on configuring Custom Matching Rules, which work in many of these cases to avoid unnecessary duplication between the two systems.

Wishing you a productive day ahead!

  • KSS
  • Author
  • Rookie
  • September 3, 2026

Hi ​@Stephan Hofmann, thank you for the suggestions and tips.  We are using the ServiceNow CMDB.  Currently we do not have the integration active and are manually adding/updating apps.  We will create the integration soon, so my question was more preemptive in nature.  ​@Giannis Antoniou, I am not afraid of moving the data from one fact sheet to another, but it’s a manual effort to do so.  The transformation essentially moves all fact sheet relationships automatically from the retired app to the new app for us, but then we have duplicated apps.  

Thank you both for the info!

    Terms & ConditionsAccessibility statement