> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iru.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Moving Devices Between Blueprints

> Move one or more devices between Blueprints in Iru Endpoint. Reassign devices individually or in bulk to apply different management policies.

<Callout icon="earth-americas" color="#B84A7A" iconType="regular">This guide applies to all device platforms</Callout>

### About Moving Devices Between Blueprints

Moving devices between Blueprints reassigns them from one Blueprint to another in Iru Endpoint. The destination Blueprint controls which Library Items and Parameters apply going forward.

<Callout icon="triangle-exclamation" color="#EAB308" iconType="regular">As of April 1, 2026, all legacy Classic Blueprints were automatically converted to Assignment Maps, which are the default, improved version of Blueprints.</Callout>

### When to Move Devices

Common reasons to move devices include:

* **Role changes** — the device should follow a different user role or department configuration.
* **Location changes** — the device moved to an office or network that uses another Blueprint.
* **Compliance** — the device needs different security or compliance settings.
* **Testing** — you want to validate a Blueprint on a device before wider rollout.
* **Temporary assignments** — short-term configuration for a project or pilot.

### How It Works

After a move, the device is assigned to the new Blueprint’s policies and Library Items. Some changes apply right away in Iru Endpoint; full enforcement on the device often depends on the next **Iru Agent** or **MDM** check-in (see [Device Check-In](/en/endpoint/devices/device-check-in/device-check-in)). Device history is retained across Blueprints. Blueprint reassignments also appear on the [Activity Page](/en/endpoint/devices/activity-page).

<Warning>
  Moving devices changes configuration and can affect the user experience. When possible, plan moves during a maintenance window and tell people what to expect.
</Warning>

### Before You Move

* Confirm the **destination Blueprint** has the right Library Items, Parameters, and policies for that device and user.
* Check for **conflicts** between the old and new Blueprint (for example overlapping policies or app assignments) so you are not surprised by remediation behavior.
* For large or sensitive changes, **test** on a small set of devices first and **document** moves for audits and support.

### Move One Device from Its Device Record

<Steps>
  <Step title="Access Device Record">
    Sign in to Iru Endpoint and open the **device record** for the device you want to move.
  </Step>

  <Step title="Edit device details">
    Click **Edit device details**, then select **Edit Blueprint**.
  </Step>

  <Step title="Select new Blueprint">
    Choose the destination Blueprint, then click **Change**.
  </Step>
</Steps>

For the same single-device flow in a shorter Device Record Management article, see [Move device to a different Blueprint](/en/endpoint/devices/device-record-management/move-device-to-different-blueprint).

### Move One or More Devices from the Devices Page

<Steps>
  <Step title="Open Devices">
    Open **Devices** in the left navigation.
  </Step>

  <Step title="Select devices">
    Click the checkmark next to one or more devices you want to move.
  </Step>

  <Step title="Change Blueprint">
    Click **Change Blueprint** near the bottom of the page.
  </Step>

  <Step title="Choose destination and confirm">
    Select the new Blueprint from the dropdown, then click **Change**.
  </Step>
</Steps>

<Note>
  Bulk moves can be processed in the background. Completion time depends on how many devices you selected and whether they are online and checking in.
</Note>

### What Happens After Moving a Device

<Tabs>
  <Tab title="macOS" icon="apple" iconType="brands">
    Mac computers will enforce **Parameters** and other agent-driven **Library Items** (for example **Passport**) the next time the Mac checks in via the Iru Agent. Parameters that were enforced on the previous Blueprint will change from their current state unless a new parameter enforces a different behavior. **Auto Apps** and **Custom Apps** that were enforced in the previous Blueprint will **not** be removed, but **Profiles** and **Apps and Books** apps will be added or removed as soon as possible during the next MDM check-in. More information about the differences in MDM and Agent check-in types can be found in our [Device Check-In support article](/en/endpoint/devices/device-check-in/device-check-in).
  </Tab>

  <Tab title="Windows" icon="microsoft" iconType="brands">
    Apps already on the device **remain** installed. Settings **stay as they are** unless the destination Blueprint’s policies **change** them. **New** apps and policies you target on the new Blueprint are **enforced**. Apps that were only **available in Self Service** on the previous Blueprint and are **no longer** targeted **do not appear** in Self Service anymore. For how quickly the Agent and MDM apply changes, see [Device Check-In](/en/endpoint/devices/device-check-in/device-check-in).
  </Tab>

  <Tab title="iOS, iPadOS, tvOS, and visionOS" icon="mobile-phone" iconType="solid">
    All Library Items, including apps and profiles, will be added or removed during the next MDM check-in as soon as possible. More information about device check-in can be found in our [Device Check-In support article](/en/endpoint/devices/device-check-in/device-check-in).
  </Tab>

  <Tab title="Android" icon="android" iconType="brands">
    **Library Items** on the destination Blueprint (including **Managed Google Play** apps and work-profile **policies**) apply when assignments change, and items that were only on the previous Blueprint are updated or removed when they are no longer assigned. Iru Endpoint sends policy updates to the **Android Management API**, and the device applies them through Google’s management channel; changes usually take effect **quickly** because Android management is event-driven. See [Device Check-In](/en/endpoint/devices/device-check-in/device-check-in).
  </Tab>
</Tabs>

### After You Move

On the admin side, it helps to:

* **Verify** the device record shows the new Blueprint and that assignments look correct.
* **Monitor compliance** and key apps or services on a sample of moved devices.
* **Confirm with users** that anything business-critical still works after check-ins complete.
* **Update** internal inventory or CMDB records if your team tracks Blueprint per device.

### Troubleshooting

<AccordionGroup>
  <Accordion title="Device not receiving the new configuration">
    **Possible causes:** Device is offline or not checking in, network issues, or the Blueprint assignment did not apply as expected.

    **What to try:** Confirm the device is online, [force a check-in](/en/endpoint/devices/device-check-in/device-check-in) if your workflow supports it, and verify the assignment on the device record.
  </Accordion>

  <Accordion title="Configuration or policy conflicts">
    **Possible causes:** Overlapping or conflicting policies between the previous and new Blueprint, or app installation order.

    **What to try:** Compare Library Items and policies on both Blueprints, resolve duplicates or contradictions, and communicate setting changes to users if their experience shifts.
  </Accordion>

  <Accordion title="Expected apps not installing">
    **Possible causes:** The app is not assigned on the new Blueprint, deployment scope, storage or compatibility limits, or the device has not checked in yet.

    **What to try:** Confirm the app is targeted on the destination Blueprint, review device storage and OS compatibility, and allow time for the next Agent or MDM check-in.
  </Accordion>
</AccordionGroup>

### Best Practices

<CardGroup cols={2}>
  <Card title="Plan" icon="calendar">
    Schedule larger moves for maintenance windows when you can.
  </Card>

  <Card title="Pilot" icon="flask">
    Try Blueprint changes on a small group before a wide rollout.
  </Card>

  <Card title="Document" icon="file-text">
    Record who moved which devices and when, for support and audits.
  </Card>

  <Card title="Watch" icon="eye">
    Follow moved devices afterward for compliance and user-reported issues.
  </Card>
</CardGroup>

For more detailed information about taking action on devices, see the [Devices](/en/endpoint/devices/) section of our Knowledge Base.