LeanIX

nav.hidden, nav ul [x-cloak], nav ul li ul { display: block !important; } This website requires Javascript for some parts to function properly. Your experience may vary.

Cookie Settings

This site uses cookies that need consent.

Functional First party cookies are needed for the website to function. These can't be turned off.

Products / LeanIX

SAP LeanIX allows organisations to manage and optimise the enterprise architecture. It helps align IT infrastructure and systems with business strategy and goals. LeanIX can help to show the full scope of application assets within your organization.

The CI Sync LeanIX connector allows organisations to synchronize business capabilities and applications from LeanIX to equivalent record types in your ServiceNow CMDB. This allows your investment in LeanIX to be leveraged as the authoritative source for application service mapping by populating the top layers of the application services hierarchy in ServiceNow.

SAP LeanIX is a new edition to CI Sync connector portfolio. Syncfish are keen for more customer use cases to expand the connector and the benefits it can provide to your ServiceNow platform.

Leverage LeanIX as the source of truth

The CI Sync LeanIX connector can elicit multiple records types from LeanIX to create equivalent CMDB CI records in your ServiceNow platform. This allows organizations to maintain LeanIX as the source of truth for enterprise architecture and enterprise application definitions while at the same time providing a rich and automated source of data into your ServiceNow CMDB.

Underpins Application Service Mapping including dynamic linking to infrastructure CIs

CI Sync uses converts LeanIX Business Capabilities and Applications into the appropriate ServiceNow application service record types allowing CI Sync to automatically seed the top layer of the ServiceNow application services hierarchy. By combining this capability with CI Sync Application Service Mapping functionality organisations can sync IT assets and IT resources discovered and sync from other CI Sync connectors (such as Lansweeper, Azure, SCCM, etc) into the CMDB and automatically link these recordsets to achieve application service maps in ServiceNow.

Relationships

Roadmap Connectors

AirWatch (Workspace ONE)

Lansweeper Cloud (Native)

Meraki

Microsoft Defender

SentinelOne

Tanium

Frequently Asked Questions

CI Synchronizer Professional Edition provides a streamlined, out-of-the-box solution for businesses looking for efficient, hassle-free CMDB synchronisation without the need for extensive customisation.

CI Synchronizer Enterprise Edition offers advanced customisation and high-volume data handling capabilities, perfect for organisations with complex synchronisation needs and custom configuration requirements.

Compare CI Synchronizer editions

Many! Check out each source connector page for details of the supported assets and other records.

Yes. CI Synchronizer can detect which source records have changed since the previous synchronisation job and only sync the newly changed source data.

Throughput is affected by factors outside of the control of CI Synchronizer, however we see a typical throughput of between 200,000 and 400,000 records per hour (and even higher rates are possible).

Yes. CI Synchronizer has a highly customisable rules engine. Amendment of some Standard (simple) default Data Sync Rules can be performed via the CI Sync Web User Interface and supported with Knowledge Base articles. Amendment of Advanced Data Sync Rules or creation of Custom Data Sync Rules requires an “Extended Implementation and Ongoing Support Plan” available at an additional cost to your CI Sync Subscription Plan.

Visit the Support page for details on amending the Default CI Sync Data Sync Rules relative to the support plan (including no plan) offered by Syncfish.

Yes. Please fill and submit the Book a Demo form to set up a time to meet with one of the Syncfish team.

No. Each customer is provisioned with a dedicated CI Synchronizer instance.

Ultimately the customer decides, however Syncfish recommends hosting each customer instance physically close to the location of their ServiceNow instance (for best performance). It can be hosted in most/all Azure Regions globally (it is still hosted/managed/maintained by Syncfish, but the customer decides which geography it is physically located in).

No. The source asset data (read from the relevant source system by one of the CI Synchronizer connectors) is transited through your dedicated CI Synchronizer instance then deleted after it’s been processed into ServiceNow.