04. Migration project setup

Once you have configured all necessary settings (see chapter 03), you are ready to setup a migration project. The EBF Onboarder provides an easy to use interface for this.

This section will describe how to set up a migration project. During the setup you can select a source UEM system, a target UEM system and the devices from the source system which you want to include in the migration project.

To create a new migration, click on the button ‘+ New Migration’ at the top right of the dashboard:

NOTE:

• We recommend that you split the devices to be migrated into several projects and perform the migration in phases (so-called “waves”). You should start with a small test group and after successful testing, you should proceed with the other phases one by one. The recommended number of devices per wave is 500. The smaller the groups, the better you can organize and monitor your migration. This should also avoid issues with older and slower systems.
• The migration will not start when you save the migration project. After saving the project, you can first set up an invitation, reminders and a welcome email (see chapter 05) which will be sent to the selected devices to initiate the migration process and to remind the users of the migration if necessary. Please read chapter 08 to get to know how to launch your devices’ migration.
• In rare cases the browser shows a strange behavior when using the Migration Setup Wizard. Please clear the cache of the browser, restart the Migration Setup or use the browsers incognito mode.

04.1. Project naming

Enter a name for your migration project:

04.2. Source system selection

Select the source system you want to migrate from:

NOTE:

• Depending on your source system, there are specific prerequisites which the Service Account which sets up the migration project needs to fulfill. Please read chapter 03.1.1 to make sure that you have made all necessary settings.
• When entering the source server name for ‘Host’, you must provide the server name without any further strings or suffix like /API.

04.3. Target system selection

Select the target system you want to migrate to:

NOTE:

• Some UEM environments may have restrictions on incoming connections (IP filters, firewall). Please check with your target system administrator that the needed ports are open and that the EBF Onboarder IP address is whitelisted (see chapter 03.2).
• When entering the target server name for ‘Host’, you must provide the server name without any further string or suffix like /API.

ATTENTION for JamfPro/School, MaaS360, Microsoft Intune, MobileIron and VMware Workspace ONE as a target system: Please read the separate documentation in addition to this one to learn more about the necessary settings. You can find them here.

04.3.1. Enrollment Program device migration

You can also select ‘Managed Enrollment’ to perform a migration for devices which belong to Apple DEP, Android Zero-Touch Enrollment or Samsung Knox Mobile Enrollment. They can be wiped by the EBF Onboarder, but they have to be enrolled with the specific programs:

ATTENTION: Usually the devices will be reset to factory settings when the user starts the migration and all custom data will get lost on that device. For Apple DEP devices, there is a way to avoid this (see chapter 04.3.2).

04.3.2. Apple DEP device migration

The EBF Onboarder can migrate Apple DEP devices without resetting them to factory settings and without losing all custom data on that device. Instead, the devices are only retired, with  all company data and applications which have been managed through the source UEM system being deleted from the device. But the status ‘Supervised’ which provides comprehensive management functions remains and the UEM system will have full functionality afterwards. Company data and applications can be pushed to the device through the target system.

ATTENTION: Once a device is retired, it will lose the DEP flag and will only keep the ‘Supervised’ flag. As a consequence, the user has the possibility to delete the MDM profile from the device which is normally not possible with a DEP device. It is possible to a certain extend to monitor if a user deletes the MDM profile, but if you don’t want your users to have the possibility to delete the MDM profile, you should proceed with a full reset of your device and re-enroll it in your target UEM system via DEP (see chapter 04.3.1). In this case all custom data on the device will get lost during the DEP re-enrollment.

04.4. Device selection

Select the devices you want to migrate. This happens in two steps:

1. Select a group of devices (see chapter 4.4.1)
2. Make a final device selection (see chapter 4.4.2)

04.4.1. Group of devices

Select the group of devices to be migrated from your source system:

NOTE: The groups need to exist in your source system already. The maximum size per group is 6,000 devices.

Adding devices with a whitelist

You can use a whitelist in a CSV format to add only selected devices from a group to the migration project:

1. 1. Prepare a CSV file in Excel with a column for the user email address or device serial numbers, e.g.:

1. Save the Excel file in the format CSV UTF-8 (comma-delimited).
2. Select a group of devices.
3. Upload the CSV file by clicking on the empty box under Black/Whitelist.
4. Click on ‘Find Devices’. You will be notified about the number of devices which has been added to the migration project.

Removing devices with a blacklist

You can also use a blacklist in a CSV format to define devices which should be removed from the group of devices you have selected. You can do this, for example, if you know that these devices are obsolete (no need to migrate them) or if the user is a VIP person whose device will be migrated separately.

To do this, you can proceed in the same way as described in chapter 04.4.1.1. The only difference is the content of the CSV file. Here, you need to add a ‘false’ in a second row, e.g.:

When you upload the file, the devices associated with these email addresses will not appear in the final selection of devices (see chapter 04.4.2).

04.4.2. Final device list

After selecting the group of devices, a device list is populated. By default, all devices of your group are selected to be included in your migration project:

You can unselect devices by removing the checkmark in the row of the respective devices if they don’t need to be migrated for some reason (e.g. because the device is obsolete, is replaced by another device or is not supposed to migrate at that time).

You can also select a group of devices by their operating system in the list ‘Target OS’. EBF Onboarder will then make a pre-selection of devices with a certain OS:

ATTENTION for Jamf Pro/School, Maas360, Microsoft Intune, MobileIron and VMware Workspace ONE as a target system: Please read the separate documentation in addition to this one to learn more about the possibility to choose to which group the devices should be added. You can find them here.

NOTE: In the device list you can find devices showing an icon illustrating a person. Devices with this symbol are private devices according to the source MDM. Devices without this symbol are company owned devices.

04.5. Project saving

Click on the ‘Save Migration’ button:

NOTE:

• The migration won’t start when you do that. It will only create a selection of devices (a ‘wave’) which you will come back to later.
• Once you click on ‘Save Migration’ you will be forwarded to the Email Content Tool which is used to set up an invitation email, reminders and a welcome email (see chapter 05). These messages are important to initiate the migration process and to remind the users of the migration if necessary.

04.6. Refreshing devices in a project

The EBF Onboarder adds devices from a selected group to the migration project at the time when the project is created and saved. If devices are added to the selected group on the source system afterwards, they are not integrated in the migration project automatically.

To retrieve new devices from the source system you can use the ‘Refresh’ feature. To do so, go to the EBF Onboarder dashboard and click on ‘Migration Details’ to access the migration project dashboard:

1. Click on ‘Refresh’:
   

   NOTE:

   • If the ‘Refresh’ button is not available, the migration was created at a time when the feature was not implemented. Thus, you cannot update the device list. In this case you need to create a new migration project.
   • This feature is available for the source systems BlackBerry UEM v12, MobileIron, Microsoft Intune and VMware Workspace ONE.

2. Confirm that you want to reload members of the group:
   
3. After confirmation you get back to step 4 of the initial project creation menu (see chapter 04.4) to refresh the devices from the same group that was used initially. Changing the group is not possible.
   

   NOTE: Here you can also add new black and whitelists if required.

4. Click on ‘Find Devices’.
5. The EBF Onboarder will check the source group again and show all devices found. Click on ‘Save Migration’ to confirm the refresh.

NOTE:

• If a device was removed from the source group and no invite was sent, the device will be removed from the migration project.
• If a device was removed from the source group, but an invite was sent already, it will remain in the migration project. The status of these devices will remain the same.