Atlassian’s New Data Manager feature with the Lansweeper Adapter

Pro Tips #73

Atlassian Data Manager is Atlassian’s new approach to solving Configuration Management Data Quality, a common issue for more mature JSM customers using Assets as their CMDB. Jira Service Management Assets provides a flexible structure for storing and managing configuration items but the real world challenge is how to get clean and accurate data into the system.

Data Manager acts as the usher for incoming data. It allows you to define cleansing rules, normalization rules, and mapping policies before data is imported into JSM Assets. This prevents your CMDB from being overwhelmed by duplicates, inconsistent naming conventions, or attributes that don’t map correctly. Instead of pushing in raw data from Lansweeper, you’re building a curated dataset aligned to your business needs and existing CMDB structure.

The Lansweeper Adapter

As a Lansweeper user, you already know the value of having complete visibility across IT, OT, and IoT devices. The challenge isn’t discovery, it’s what happens after discovery. Raw data can be overwhelming, inconsistent, and hard to map into existing Jira Service Management Assets Schemas.

That’s where the Lansweeper adapter for Atlassian Data Manager comes in. The adapter creates a controlled pipeline between Lansweeper and JSM Assets, letting you apply cleansing and normalization rules before the data is imported into your CMDB. Instead of pushing raw scan results directly into Assets, you can:

• Prioritize the attributes that matter most (like warranty expiry, last logged in user, or Asset Type).
• Exclude the noise by filtering out irrelevant devices such as unmanaged or guest machines.
• Map clean relationships into your existing schemas and object types in Assets.

With the adapter in place, Lansweeper’s discovery data can be better structured, turning your CMDB into a trusted foundation for ITSM and ESM processes rather than just a repository of raw inventory data.

Data Manager or Lansweeper Marketplace App?

Why Choose Data Manager w/ Lansweeper Adapter Over the Existing JSM Assets Integration

If you’re already using Lansweeper with Jira Service Management, you might be familiar with the existing Lansweeper JSM Assets Integration APP. That APP extracts Lansweeper data, transforms it into a predefined Lansweeper schema, and loads it into Jira Assets. For many customers, this is quick to set up and provides an immediate way to get discovery data into Jira.

Lansweeper Assets Integration APP

• hard coded Asset Schema
• like for like asset type to object type mapping

Atlassian Data Manager

• Flexible, allowing for import of lansweeper data to 1 or more existing Schemas
• Allows multiple discovery tool sources to be normalized into 1 Asset Object, helping eliminate duplicate objects

But there are important trade offs to consider:

• Data Quality vs. Speed
  • Lansweeper Assets Integration: Data flows automatically on a schedule you define, but what you get is like for like asset/object creation in JSM Assets. This often results in duplicates, inconsistent naming, and attributes that might not be relevant.
  • Data Manager + Adapter: You gain the ability to cleanse and normalize the data before it enters Assets, but it’s not automatic. Each sync requires manual intervention to review and approve data imports, which slows the process but ensures higher quality.
• Schema Control
  • Lansweeper Assets Integration: Lansweeper data is mapped into a predefined asset schema in Assets with predefined object types. This works well for standard ITSM use cases but can be rigid if your organization wants different object structures or custom attributes.
  • Data Manager + Adapter: You decide exactly how Lansweeper attributes should be structured, filtered, or merged into Assets. More upfront effort, but greater long term flexibility.
• Noise vs. Precision
  • Lansweeper Assets Integration: Everything Lansweeper finds in a selected Asset Type gets synced with assets, which can overwhelm your CMDB with unmanaged devices or irrelevant endpoints.
  • Data Manager + Adapter: You choose what’s important.
• Operational Effort
  • Lansweeper Assets Integration: Once configured, it runs with little oversight, which is ideal for teams with limited resources or low data quality concerns.
  • Data Manager + Adapter: Requires ongoing manual review of sync jobs. This can be a burden for smaller teams, but it ensures that every record in Assets has been vetted and mapped properly.

Things to Consider when choosing the best approach:

• If you value speed and automation, the existing Lansweeper Asset integration APP could be the better choice.
• If you value flexibility and control, Data Manager with the Lansweeper adapter could be the better choice, keeping in mind it demands more manual oversight per sync.