Transformations define high-level changes in your landscape as groups of pre-defined & customized impacts.

If your LeanIX edition contains the BTM module, you can decide at your own pace, when to activate the new features, whether to activate only Milestones should you want to start with simple planning, or directly get transformations and milestones together.

Module activation

In the "Optional features and early access" menu, select “Activate” on the item BTM: Transformations & Milestones of the list.

Then click “Activate” on the modal.


Admin menu to get BTM functionalities

Features included

  • Milestones
    Refer to the documentation

  • Transformations
    To help you define high-level changes on your landscape as groups of pre-defined & customized impacts.
    We introduce templates that guide you through the creation of your initiatives without requiring you to be intimately familiar with the LeanIX data model.

Transformations can be created, projected, and executed. Are available in the inventory, search, and filters, so now your Projects (and Transformation Items) are directly related to all other Fact Sheets on the workspace.

  • Reports
    For those workspaces based on Transformation Items, it's possible to use the roadmap based on the lifecycle. The one that has the same functionalities as the roadmap reports for other Fact Sheets + drill down for impacts.

Transformation roadmap using lifecycle

The Landscape, Matrix & Portfolio reports allow the selection of multiple items (Transformation Items or Projects) as sources of transformations. Thus, changes in the workspace’s IT Landscape coming from multiple initiatives can be visualized at the same time.

The timeline will be generated based on the earliest start date and the latest end date (among the multiple selected items). And if there are any milestones created, they will also be visible.


Plan and Model Scenarios to Transform IT

  • Model changes to the IT architecture as transformations

  • Select the Transformation Item or Project Fact Sheet that will alter the current architecture

  • Go to the transformation tab and add a new one.


Transformation selector

  • A list of available out-of-the-box transformations is ready to use and start documenting changes to architectural artifacts

  • The form provides enough data to guide you. You only need a name to start the creation. In addition, for each transformation, you can define a completion date, either an exact date or use a milestone.

Break-down of all Impacts Modelling options


1️⃣ Set lifecycle phase Sets the life cycle of a Fact Sheet (e.g., An Application will be active when the transformation is completed).
2️⃣ Set/copy field to Sets or copy(from another Fact Sheet) a field on a particular Fact Sheet(e.g., A Business Capability will change its maturity when the transformation is completed).
3️⃣ Set relation validity The validity refers to the active from/until fields on the relations of every Fact Sheet; when using this impact you don't need to create the relation first, as the impact does it by default.
4️⃣ Set relation field to Set any field that is maintained in a relation level, as the technical fit; when using this impact you don't need to create the relation first, as the impact does it by default.
5️⃣ Create/ remove relations Creates or removes relations of one type (User groups, children, etc) from one source Fact Sheet to a target one
6️⃣ Create/ remove relation constrains Creates or removes constraining relations of one type (User groups, BC, etc) from one source Fact Sheet to a target one
7️⃣ Copy /move all relations Copies or moves ALL relations of one type (User groups, children, etc) from one source Fact Sheet to a target one
8️⃣ Remove all relations Removes ALL relations of one type (User groups, children, etc) from one Fact Sheet type
9️⃣ Add/replace /remove tags Impacts the tags of the selected Fact Sheet


Application changes

We offer predefined templates with the most common changes for applications. The system will automatically aggregate the impacts of each transformation if the forms are completed.
Each template can be customized by adding more impacts, but this is not mandatory


Example: Implement a new Application

By entering the name of the application, you will automatically create the application in your workspace (don't worry, it remains in planned status and will not be included in the price of your edition until you decide to execute the transformation).

Check the implied impacts and also add more impacts to the Fact Sheets in the scope. By default, all implied impacts use the direct relation as a way of modeling changes but it's also possible to change this mode to use the “active from/until” field on the relation.


New Application template

All transformations create a direct relation in the Fact Sheets


Direct relations created - view in relation explorer

To see all the transformations affecting your Application, or any other Fact Sheet type, go directly to the Fact Sheet (transformation tab) and understand the initiatives that are in place. Execute and edit the transformation directly on this side as well!


Impacted Fact Sheet view

Upgrade a technology

By entering the name of the application, only the current IT components related to it will be displayed as a way to replace it. For the replacement, you can either select an ITC from the workspace or create a new one on the fly.


New technology template

Custom transformation

Define your own transformation by adding as many impacts to the selected scope.

Why selecting a scope is important?
Normally, when planning transformations, not everything is figured out. But you always start with defined scope which over time and with less uncertainty makes it possible to refine. That's the moment to define, the custom impacts and completion date.

Planned applications

❓ How to recognize applications or other Fact Sheet types that have been planned using transformations?

New Fact Sheets generated from a transformation, are created in a "planned" state, this is a new field in all Fact Sheets that by default is hidden, but can be used as a filter. (use the Meta model configuration to add it to any section of your Fact Sheet)

1383 1068

❓ How to correctly delete a Fact Sheet created by a transformation?
Delete it in the same transformation, this will remove it directly from the inventory and all relations that have been created.