What's New in Assets Data Manager – September 2026

[#1]

Hi Atlassian Community! 👋

We're excited to share what's new in Assets Data Manager for September 2026. This release brings a significant set of improvements to the new admin journey, and a new wave of capability additions covering Lansweeper, bulk operations, saved search, default attribute mapping, and a new cloud-enabled data source → for flat files.

Here's everything that will be shipped in the coming weeks. 🚀

September 2026 Changes

📁 New Cloud-Enabled Data Source: Flat File

A Flat File data source is now available as a cloud-enabled import method in Data Manager. Upload structured files directly as a data source — no on-premise Data Manager clients required. This is the next step in our journey to bring more data sources to the cloud.

The files must be publicly available, that is; authentication credentials can’t be catered for.

⚡ Bulk Cleanse and Bulk Merge

You can now perform bulk cleanse and bulk merge operations directly in Data Manager. Select multiple records and apply cleanse or merge actions in a single step — a huge time-saver when managing large datasets.

📤 Export to Assets from Saved Search

A new Export to Assets action is now available from the Saved Search page. Run a saved search, select your results, and export them directly into Assets — no need to download and re-import data manually.

🔌 Lansweeper Data source – Improvements

Two significant updates for Lansweeper hardware customers:

• Multi-site access fix — Lansweeper jobs previously failed entirely if an API token was scoped to fewer sites than the account had access to. Jobs now gracefully skip inaccessible sites and succeed with a warning, rather than failing completely.

• New fields — The adapter now retrieves additional fields from the Lansweeper API including cloud discovery data (cloudProvider, cloudRegion, cloudTags), additional asset identifiers, scanner type, CPU core count, RAM size, and storage size.

The Lansweeper data source now supports Software as a selectable data type alongside Hardware. When configuring a Lansweeper data source, you can now choose:

• Hardware (default — fully backward compatible with existing data sources)

• Software — retrieves software inventory data including name, publisher, version, category, installation type, install date, architecture, and more, mapped directly into Assets' Software object schema.

Separate Hardware and Software jobs can run independently from a single Lansweeper source. The software data type is only available for API calls, not SQL.

🗂️ Default Attribute Mapping and Atlassian Vendor Mappings

Data Manager now automatically suggests Atlassian vendor mappings for some data source columns using a curated, data source-specific lookup — reducing the manual effort of mapping fields when setting up a new data source.

• Supported adapters: Active Directory, Microsoft Intune, Lansweeper, ServiceNow, Qualys, CrowdStrike Falcon, SCCM, Flexera One/FNMS, Microsoft Defender, Tenable

• The curated mappings override the previous name-match heuristic when an explicit product-confirmed mapping exists for your adapter and source column.

You can still save any mapping for any data source to become the default attribute mapping; which will take precedence over any other mapping suggestions.

All mapping suggestions can be overwritten as desired.

Smaller improvements

• Clear all mappings restored for flat file data sources.

• Cancel a stuck data source - Where a data source is not completing, Admins can go to merge now cancel their stuck data source.

• Data source name restored in Audit Log — Admins can once again see which data source giving better traceability for data ingestion issues.

• Data Dictionary issues now have search capability, making it easier to find the dictionaries you need to assign to a group.

• Total object count restored when filtering — The count at the top of the Object List page was is back.

• Delete confirmation prompt restored when deleting a cleansing rule — The confirmation step is back after a safety regression for cleansing and transforms.

• Transform failure reason now visible — Admins can now see the error message on the data source configuration screen when a transform fails.

• Cleansed data reason codes now display in plain language — e.g. "Forced clean" instead of a raw reason code.

[Gary Blower]

Great news and features. Well done team. Can't wait to see these updates in action.

[Dirk Ronsmans]

Great work @Karyn Findlay !

Especially liking the Lansweeper improvements! (Software hooray!). A bit sad that the flat file doensn't support an authenticated source. It would be great to be able to use Onedrive (or any other file service) to store the file. 

Have you considered building a small file hosting app with authentication that can be deployed by the company itself? Doesn't need to be much, even with a simple token based authentication that would already greatly improve the flat file implementation. I don't think any company will put their Asset data on a publicly available source.

Any more details on the "Export to Assets" functionality? How does it differ from adding a "Data Manager Saved Search" import direclty in a schema import?