Migrating a device from Legacy Provisioning Templates to Blueprints 2.0 via "Upgrade Now"

Android

When a device was provisioned using a Legacy Provisioning Template, it shows a Template Provisioning management status in the Esper Console and cannot be managed through Blueprints until it is explicitly migrated.

Why this happens

Blueprints and Legacy Provisioning Templates are separate management systems. Devices provisioned before your tenant adopted Blueprints remain bound to their original template and must be individually upgraded to come under Blueprint management. The upgrade does not happen automatically.

Before you begin

• Confirm the device is online and visible in Devices & Groups.
• Confirm the Esper Agent on the device is running a version that supports Blueprints. You can check the agent version on the device detail page under Devices & Groups → [Device Name] → Device Info.
• Identify the blueprint you want to apply. Review its policies and confirm they are compatible with the device's Android version and OEM before proceeding — the migration replaces the legacy template configuration and cannot be automatically rolled back.

Steps

1. Open the device detail page. In the Esper Console, go to Devices & Groups, then select the device that shows Template Provisioning as its management status.
2. Locate the Upgrade Now option. On the device detail page, find the management status indicator showing Template Provisioning. An Upgrade Now button appears alongside this status. If the button is not visible, verify the device is online — the option does not display reliably for offline devices.
3. Select the blueprint to apply. Click Upgrade Now. When prompted, choose the blueprint you want to apply to this device. Take a moment to confirm your selection — once the migration completes, the legacy template configuration is replaced by the blueprint.
4. Confirm the upgrade. Confirm the action in the prompt. The Esper Console will begin migrating the device to Blueprint management.

Verify: Within a few minutes, the device detail page should no longer show Template Provisioning. The name of the applied blueprint should appear as the active management configuration, and the blueprint status should show as In Sync. If the status shows a conflict or error, review the blueprint's policies for incompatibilities with the device's Android version or OEM.

If this doesn't resolve it

Before contacting support, collect the following:

• The device serial number or Esper Device ID (visible on the device detail page).
• The Esper Agent version installed on the device.
• The name of the blueprint you attempted to apply.
• A screenshot of the management status shown on the device detail page.
• The Activity Feed entries for the device at the time of the attempted upgrade (Devices & Groups → [Device Name] → Activity Feed).

Common situations that require support assistance:

• The Upgrade Now button remains missing after confirming the device is online and the Esper Agent is up to date.
• The device reverts to Template Provisioning status after the upgrade appears to complete.
• Blueprints do not appear anywhere in the Esper Console navigation.

Contact Esper Support with the information above.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.