> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/admin/device-management/transfer-device.md).
# Transfer Device
**Overview**
The Transfer feature provides a streamlined way to reassign a temperature sensor from one dashboard (or work area) to another. This is especially useful in operational environments where cold storage units, fridges, or freezers are physically relocated from one site, zone, or department to another. Rather than detaching and reconfiguring the sensor manually, the system allows you to perform a digital transfer, preserving all historical data and configuration.
***
#### When to Use
Use the Transfer function when:
* A unit (e.g. fridge or cold room) has physically moved to a different location.
* You want to reassign a sensor to another department, kitchen, or work area within the same site.
* You are reorganizing the structure of dashboards to reflect operational changes.
***
#### How to Transfer a Device
1. Access the Transfer Menu:
* From the administration dashboard, locate the sensor you wish to move.
* Click on the Transfer icon/link associated with that sensor.
2. Select Destination Work Area:
* A list of available work areas (grouped by Site and Department) will be displayed.
* You can search or scroll through the options to find the appropriate destination.
3. Initiate Transfer:
* Click the Transfer Here button for the desired work area.
* The system will automatically transfer the sensor and all associated configurations.
***
#### What is Transferred
* Sensor association: The sensor is linked to the new dashboard.
* Historical data: All past telemetry and alert logs remain intact.
* Configuration settings: Alert templates, compliance rules, and tags are preserved unless manually changed after the transfer.
***
#### Key Benefits
* Efficiency: Avoids the need to delete and re-add devices.
* Continuity: Maintains audit trail and data integrity across dashboards.
* Flexibility: Supports dynamic operational environments with movable equipment.
***
---
# 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.didge.io/home/foodcore-sensors/admin/device-management/transfer-device.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.
