Let’s face it: migrations can be a lot of work. However, there are tools available for you to help ease your journey in this migration. This guide is designed to help you navigate small and large migrations with best practices, tips, and even a few gotchas.
But first: why should you upgrade your devices to Blueprints?
- Security: Blueprints take a multi-factored approach to security. Set a variety of features, such as adb access directly from the blueprint, and change it at any time. Wi-Fi and apps can also be synced according to your preferences and use cases.
- Better Workflows: No need to apply a compliance policy every time you want to make a change. Blueprints can be updated at any time. And you can choose when to apply those changes to your devices.
- New Features: Going forward, only blueprints will receive new features and updates to existing ones.
Yes, Blueprints come with their own set of quirks, but the good news is that it’s much easier to backtrack with a blueprint than a template. Added the wrong app to the blueprint? That’s fine, just upload the correct one. Blueprints are “editable”.
This guide is broken down into steps.
- Identify a test group: Before beginning, we recommend choosing a few devices of each type to migrate. These test devices will validate compatibility with the Esper agent and Blueprints service.
- Copy over information: Copy template and policy information to ease the transition.
- Upgrade the test group: Upgrade your test group to Blueprints and conduct tests to determine Blueprint compatibility.
- Upgrade your fleet: After validation, upgrade your fleet to the latest Blueprints experience.