> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/getting-started/how-to-export-sensor-data.md).
# How to export sensor data?
The Export Data feature in Data Explorer allows you to download all the historical data collected by your sensors directly from the MyMove servers. Follow the steps below to create your custom CSV export.
***
### 1. Navigate to the sensor page
From your project dashboard, open Data Explorer, then select the device of interest from the left-side menu.
***
### 2. Click “Export Data”
In the top-right corner of the interface, click the “Export Data” button. This will open a configuration panel on the right side of the screen.
***
### 3. Configure your export
Inside the Export Data panel:
* Name your file: Enter a custom name for your export file.
* Select the date range: Use the calendar selectors to define the time window you want to export.
* Choose your parameters: Tick the parameters you wish to include. Each parameter will appear as a column in the exported CSV.
* Order the columns *(optional)*: Drag and drop the selected parameters to define the desired order of columns in your CSV.
Export Data panel
{% hint style="info" %}
You can export any length of historical data without limitation. The system will automatically split the output into optimized CSV chunks for better performance.
{% endhint %}
***
### 4. Start the export
Click “Export data” at the bottom of the panel. The export process will begin immediately. Once ready, your download will start, or you’ll be notified via the interface.
***
You now have your full dataset downloaded in CSV format — ready for analysis in Excel, Python, or your preferred tool.
---
# 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://move-solutions.gitbook.io/untitled/getting-started/how-to-export-sensor-data.md?ask=&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.
