> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/inventory/software-assets/export-software-assets.md).

# Export and import software assets

The **Export** option on the **Software Assets** page enables you to download your software asset inventory in various formats.&#x20;

You can use these exports to create quick reports and organize your data in the commonly configured format (including column names and order) compatible with several Software Asset Management (SAM) tools, such as Aspera, Miss Marple, Snow, Flexera, and others.

To export software assets:

1. Go to **Inventory** > **Software Assets**.
2. Hover over the **Export** option.
3. Select your preferred export format.
4. In **Create New Report**, fill out the required fields.
5. Select **Run** to initiate the export.

{% hint style="info" %}
Depending on your SAM Tool setup, the standard reporting templates might require some adjustments. To learn about the reporting templates, see [Reports](/modules-and-features/other-tools/reports.md).
{% endhint %}

### Import software assets

Our entitlement services allow you to import your software assets into the Marketplace Platform, even those not purchased through SoftwareOne.

For information on entitlement services and how to import your assets, [contact support](/help-and-support/contact-support.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/modules-and-features/inventory/software-assets/export-software-assets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
