> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/how-to-export-all-raw-data-from-claimlane.md).
# How to Export All Raw Data From Claimlane
A lot of data is collected in Claimlane, and all raw data can be exported, giving you full flexibility to do anything you like.
There are two options:
1. Manual Excel export
2. Raw Data API
#### Guide to Excel export
1\. From your inbox, click the square icon in the top right corner.
2\. Select “Manage Company” from the dropdown menu.
3\. In the bottom-left of the menu, click on “Data Export”.
4\. Choose the organization you want to export data from (if you have multiple accounts or brands in Claimlane).
Once you’ve made your selection and clicked “Export Data”, a report will be sent to the email address associated with your login.
See the video below for an example.
### Guide to the Raw Data API
Documentation can be found here:
The API allows you to export all of the same data as in the manual export.
### Explanation of the data you can extract
Below is a list of all the data you can extract from Claimlane, and what the data shows. Please note, that this list may not reflect the export 100%, as there are constantly added new data fields, and you may have custom tags as well.
1. ticketNumber
1. `ex:` 1003183
2. `Description:` The ticket number in Claimlane\
2. createdDate
1. `ex:` 2025-04-24T09:17:00Z
2. `Description:` Timestamp for ticket created by the customer\
3. firstResponse
1. `ex:` 2025-04-24T09:17:17Z
2. `Description:` Time from submitted to first reply or action on the ticket\
4. archiveTime
1. `Description:`Timestamp for ticket archived. This can help you calculate the resolution time\
5. archiveAssigned
1. `ex:` Michael
2. `Description:` Assigned user when the ticket was archived. Allows you to do agent analytics.\
6. tileName
1. `ex:` Faulty outside 30 days
2. `Description:` What type of issue was selected in the self-service flow from the front page\
7. b2cChannel
1. `ex:` web
2. `Description:` Each self-service flow has a channel. It can we web or store\
8. selfServicePortal
1. `ex:` claimlanetest-claim
2. `Description:` Shows the name of the self-service flow in which the ticket is created\
9. market
1. `ex:` gb
2. `Description:` From what country has the customer submitted the ticket\
10. status
1. `ex:` Completed
2. `Description:` What is the current status of the ticket in Claimlane\
11. productName
1. `ex:` Maxi Travel System
2. `Description:` Name of the product pulled from API\
12. currency
1. `ex:` USD
2. `Description:` Show currency when applicable\
13. productSupplier
1. `ex:` Acme corp
2. `Description:` Name of supplier on the product (if applicable)\
14. productSku
1. `ex:` R2-SP
2. `Description:` Product SKU pulled from the product/order integration\
15. ean
1. `ex:` 123455999999
2. `Description:` Product EAN pulled from the product/order integration
16. email
1. `ex:`
2. `Description:` The customers name. This allow you to sort on specific customers\
17. phoneNumber
1. `ex:` +449998887777
2. `Description:` The customers phone number\
18. courierName
1. `ex:` DHL
2. `Description:` Courier connected to the order (from order integration)\
19. orderDate
1. `ex:` 2025-01-01T08:57:00Z
2. `Description:` Order date (from order integration)
20. description
1. `ex:` I have been having on going difficulties with the latching of the buggy going up and down.
2. `Description:` Customers description of the problem\
21. unitPrice
1. `ex:` 695
2. `Description:` Shows cost of the product (from order integration)\
22. quantity
1. `ex:` 1
2. `Description:` Shows how many units of the product was affected\
23. ticketType
1. `ex:` claim
2. `Description:` The ticket-type is a setting in the self-service flows. Often the tile-name will be easier to use.\
24. organizationName
1. `ex:` Nike
2. `Description:` Your account name\
25. linkToConsumerClaim
1. `ex:` [https://app.claimlane.com/home/supplier/](https://app.claimlane.com/home/supplier/62725cd5630d501bf978c1a7/consumer-ticket?dialogConsumerClaimId=680a018c3d0d283f54c1e7ab)...
2. `Description:` Show the direct link to the ticket. This can help you quickly analyse and understand a problem more in detail.\
26. transferredToOrganization
1. `ex:` Not transferred
2. `Description:` Some organisations have multiple accounts where tickets can be transferred from one to another. This shows if the ticket has been transferred and to which one.\
27. selectedSupplier
1. `ex:` Adidas
2. `Description:` A retailer can forward a ticket to a supplier. This shows if the Ticket has been transferred and to which supplier.\
28. statusChanges
1. `ex:` 29-04-2025: Status changed to Completed
2. `Description:` This shows the date when the ticket status was last changed, and to which status. This can help you track how long a ticket stays in one status, when they leave, etc.\
29. Is the product in its original packaging?
1. `ex:` Yes
2. `Description:` This is an example of a flow tag. All flow tags and internal tags are specific to your business, and will be shown in the export.\
30. Internal issue tag
1. `ex:` Broken in Seam
2. `Description:` This is an example of an internal tag. All flow tags and internal tags are specific to your business, and will be shown in the export.