> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/device/moving-devices.md).

# Moving Devices

Moving hands devices over to another workspace for good. The devices leave your workspace and become the receiving workspace's devices, including the billing for them.

Nothing happens right away. A move is a request first, and the devices stay exactly where they are until an administrator in the target workspace accepts it.

{% hint style="warning" %}
Moving is permanent. Once a move has been accepted, only the receiving workspace can move the devices back — you cannot undo it from your side.
{% endhint %}

## Moving or Claiming?

Use claiming if you want another workspace to have access to devices that stay yours. Use moving if the devices should stop being yours altogether.

{% content-ref url="/pages/-M-JQQctuXfCo26MgDFn" %}
[Claiming](/device/claiming.md)
{% endcontent-ref %}

## Sending a Move Request

1. Navigate to your fleet view (Fleet / All Devices) and select the devices you want to move.
2. In the action bar that appears, select "Advanced" and then "Move to workspace".
3. Choose the target workspace.
4. Optionally tick "Copy integration settings" and add a message for the receiving workspace.
5. Confirm with "Send move request".

You need the device permission in your workspace to send a request.

### Choosing the Target Workspace

Search the field by name to find the workspaces you are a member of.

To move devices to a workspace you are not a member of — a customer's workspace, for example — paste its workspace ID into the same field and select the "Use workspace ID" entry that appears. Ask an administrator of that workspace for the ID.

### What Is Not Moved

Rules, webhooks and reports stay with your workspace. They are not moved and not copied, so recreate them in the target workspace if they are still needed there.

Integration settings, such as network server or MQTT credentials and secrets, are only handed over if you tick "Copy integration settings" before sending the request.

{% hint style="warning" %}
**If you use the MQTT broker, your topics change.** The devices join a copy of their product in the target workspace, and that copy gets its own product slug — the part of the MQTT topic that identifies the product. Data still sent to the old topics no longer arrives, and anything subscribed to them stops receiving. Point both at the new topics after the move.
{% endhint %}

## Reviewing an Incoming Request

When another workspace wants to move devices to you, a banner appears above your device list. You can also open the list directly under Administration, in "Device move requests".

On the "Incoming" tab, select "Review" to see who sent the request, which devices it covers and any message that came with it. Choose the plan the incoming devices should get in your workspace, then accept or reject.

{% hint style="warning" %}
Accepting a request means your workspace takes on the billing for those devices from that moment on. The accept button states how many devices that is.
{% endhint %}

Rejecting leaves the devices in the sending workspace.

## Tracking Requests You Sent

The "Outgoing" tab lists the requests your workspace has sent. While a request is still pending you can withdraw it with "Cancel".

By default only pending requests are shown. Select "Show all" to include the ones that have already been resolved — accepted, rejected, expired or failed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.datacake.de/device/moving-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.