Skip to main content
This guide applies to all device platforms

​
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.
As of April 1, 2026, all legacy Classic Blueprints were automatically converted to Assignment Maps, which are the default, improved version of Blueprints.

​
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). Device history is retained across Blueprints.
Moving devices changes configuration and can affect the user experience. When possible, plan moves during a maintenance window and tell people what to expect.

​
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

1

Access Device Record

Sign in to Iru Endpoint and open the device record for the device you want to move.
2

Edit device details

Click Edit device details, then select Edit Blueprint.
3

Select new Blueprint

Choose the destination Blueprint, then click Change.
For the same single-device flow in a shorter Device Record Management article, see Move device to a different Blueprint.

​
Move one or more devices from the Devices page

1

Open Devices

Open Devices in the left navigation.
2

Select devices

Click the checkmark next to one or more devices you want to move.
3

Change Blueprint

Click Change Blueprint near the bottom of the page.
4

Choose destination and confirm

Select the new Blueprint from the dropdown, then click Change.
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.

​
What happens after moving a device

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.

​
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

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 if your workflow supports it, and verify the assignment on the device record.
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.
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.

​
Best practices

Plan

Schedule larger moves for maintenance windows when you can.

Pilot

Try Blueprint changes on a small group before a wide rollout.

Document

Record who moved which devices and when, for support and audits.

Watch

Follow moved devices afterward for compliance and user-reported issues.
For more detailed information about taking action on devices, see the Devices section of our Knowledge Base.