Skip to main content
This guide applies to all device platforms

​
About Moving Devices Between Blueprints

Moving a device to a different Blueprint allows you to change its configuration, policy assignments, and management settings. This is useful when devices need different configurations based on their role, location, or user requirements.

​
How It Works

When you move a device to a different Blueprint, the system immediately assigns the device to the new Blueprint’s policies and configuration profiles. The device receives new application assignments and configuration updates during its next check-in with the MDM server.

​
When to Move Devices

Common scenarios for moving devices between Blueprints include:
  • Role Changes: Device assigned to different user role or department
  • Location Changes: Device moved to different office or network environment
  • Compliance Requirements: Device needs different security or compliance settings
  • Testing: Moving device to test Blueprint for configuration validation
  • Temporary Assignments: Short-term configuration changes for specific projects

​
How to Move a Device

1

Access device record

Navigate to the Devices section in the Iru web app and locate the device you want to move.
2

Open device actions

Click on the device to open its record, then access the Device Actions menu (three-dot menu).
3

Select move option

Choose Move to Different Blueprint from the available actions.
4

Choose target Blueprint

Select the destination Blueprint from the dropdown list of available Blueprints.
5

Confirm the move

Review the changes that will be applied and confirm the move operation.

​
What Happens During a Move

When you move a device to a different Blueprint, the following changes occur:

​
Immediate Changes

  • Policy Assignment: Device is assigned to the new Blueprint’s policies
  • Configuration Updates: New configuration profiles are applied
  • Application Assignments: Apps assigned to the new Blueprint are deployed

​
Gradual Changes

  • Policy Enforcement: New policies are enforced during the next device check-in
  • Application Deployment: New applications are installed based on the new Blueprint
  • Configuration Remediation: Existing settings are updated to match new requirements

​
Considerations

Moving a device to a different Blueprint will change its configuration and may affect user experience. Consider notifying users before making changes.

​
Before Moving a Device

1

Review target Blueprint

Ensure the destination Blueprint has the appropriate configuration for the device and user.
2

Check for conflicts

Verify that the new Blueprint doesn’t conflict with existing device configurations.
3

Plan timing

Consider moving devices during maintenance windows to minimize user disruption.
4

Notify users

Inform users about the upcoming configuration changes and any impact on their workflow.

​
After Moving a Device

1

Verify configuration

Check that the device has received the new Blueprint configuration correctly.
2

Monitor compliance

Ensure the device remains compliant with the new Blueprint requirements.
3

Test functionality

Verify that applications and services work correctly with the new configuration.
4

Update documentation

Update any device inventory or assignment records to reflect the new Blueprint.

​
Troubleshooting

Possible causes:
  • Device offline or not checking in
  • Network connectivity issues
  • Blueprint assignment not applied
Solutions:
  • Check device online status and connectivity
  • Force a device check-in from the Iru web app
  • Verify Blueprint assignment in device record
Possible causes:
  • Conflicting policies between old and new Blueprint
  • Application installation conflicts
  • User settings conflicts
Solutions:
  • Review policy assignments in both Blueprints
  • Check for application conflicts
  • Consider user notification about setting changes
Possible causes:
  • Application deployment policies not applied
  • Device storage or compatibility issues
  • Network connectivity problems
Solutions:
  • Verify application assignments in the new Blueprint
  • Check device storage and compatibility
  • Ensure network connectivity for application downloads

​
Best Practices

Plan Changes

Plan Blueprint moves during maintenance windows to minimize user disruption.

Test First

Test Blueprint configurations on a small group of devices before broad deployment.

Document Changes

Keep records of Blueprint moves for audit and troubleshooting purposes.

Monitor Impact

Monitor devices after Blueprint moves to ensure proper configuration and user satisfaction.

​
Bulk Device Moves

For moving multiple devices to the same Blueprint:
1

Select Multiple Devices

Use the device list to select multiple devices.
2

Choose Bulk Actions

Choose the bulk move action from the available options.
3

Select Target Blueprint

Choose the destination Blueprint for all selected devices.
4

Confirm Operation

Review and confirm the bulk move operation.
Bulk moves are processed in the background and may take time to complete depending on the number of devices and their current status.