Each tool in the integrated toolchain has its own data or meta model, which can be adapted to fit organizational needs.
Each product manages its data repository differently:
SAP LeanIX: Uses a standard meta model with 12 fact sheets to store and manage architectural objects and information.
SAP Signavio: Attributes and dictionary object types are defined and maintained within the dictionary of SAP Signavio Process Manager.
SAP Cloud ALM: Maintains projects, scopes, processes, and related implementation data.
The following illustration provides an overview of the repositories in the three tools, with commonly used data objects outlined in blue:

Aligning these data models before integration ensures interoperability and consistent data across platforms, helping stakeholders get the most value from the toolchain with integrated insights.
It allows stakeholders to answer critical questions, such as:
Which applications currently support a particular process?
How many processes rely on applications that are being phased out?
Which critical data objects are processed at each step of the process?
How many applications are used in processes that lack proper governance or ownership?
How many interfaces are associated with each process or application in the landscape?
What is the status and progress of my high-level initiatives?
Such insights empower transformation teams to make informed decisions, optimize architectures, and manage risk proactively.
Best Practices for Setting Up the Overarching Meta Model
Each product serves as the leading system for specific data attributes. Updates from the leading system are then pushed to the others, keeping data synchronized and accurate.
Note that:
Each of the three integrations is independent, and
Synchronization can be one-directional or bidirectional, depending on the configuration.
This modular setup allows organizations to tailor data governance and integration flows to their specific transformation needs.
The following table shows the synchronization direction for each integration and the source of truth for each data type:
| Integration | Direction of Sync | Leading System |
|---|---|---|
| SAP LeanIX and SAP Signavio | Bidirectional |
|
| SAP LeanIX and SAP Cloud ALM (for managing projects) |
| SAP Cloud ALM |
| SAP LeanIX and SAP Cloud ALM (for SAP landscape discovery) | One-directional sync from SAP Cloud ALM to SAP LeanIX. | SAP Cloud ALM |
| SAP Cloud ALM and SAP Signavio | One-directional sync from SAP Cloud ALM to SAP Signavio. | SAP Cloud ALM |
The following illustration gives an overview of the default attributes from the data models of SAP LeanIX, SAP Signavio, and SAP Cloud ALM, along with the most relevant custom attributes that we recommend as part of a basic setup for valuable insights:

Technical Setup and Configuration
Before starting the integration, each product must be set up individually. Refer to the getting-started guides of each product:
- https://help.sap.com/docs/signavio-process-manager/user-guide/intro
- https://help.sap.com/docs/leanix/ea/getting-started?locale=en-US
- https://help.sap.com/docs/cloud-alm/setup-administration/about
Note
For customers currently using SAP Solution Manager, for a detailed step-by-step migration guide to SAP Cloud ALM, see Transition from SAP Solution Manager to SAP Cloud ALM.
The following documentation offers high-level guidance for integrating SAP LeanIX, SAP Signavio, and SAP Cloud ALM, along with valuable tips and best practices:
Lesson Summary
- Data model alignment across SAP LeanIX, SAP Signavio, and SAP Cloud ALM is crucial for interoperability and consistent data.
- Establishing a leading system for specific data attributes ensures accurate synchronization.
- Understanding the synchronization direction between systems is essential for effective data governance.
- Leveraging default and custom attributes enhances the value derived from integrated insights.
- Proper technical setup and configuration of each product are prerequisites for successful integration.