Console Guide

Token Pool

On the Dashboard, the Instance Tokens label indicates the number of Tokens assigned to the Instance and their relative states:

Available for a device to migrate.
Reserved assigned to a device in transit.
Consumed by a device succesfully migrated.

Exports

On the Dashboard, the Exports button allow you to generate and download the following reports:

Migrations Report: list the ongoing Migrations, with their details and the devices count for each statuses.
Devices Report: list all the devices with their details and timestamped statuses.

Creating a new Migration

You can create a new Migration from the Dashboard:

Click on the blue "New Migration" button, located on the top right corner.
Migration Name: give your Migration a name and a quick description, then click on "Next".
Source: provide the following details about your Source Tenant:
- The EMM server type.
- A list of specific fields which depends on the EMM server type chosen above.
- If you have any iOS devices registered in Apple's Device Enrollment Program (or DEP), you must choose whether you want to initiate a Full Device Wipe on those devices (Apple's Official workflow) or not (Exodus's Legacy workflow).
- If you wish to migrate your compatible Android devices (i.e. Android 6+) toward Google's Android Enterprise as Fully Managed by triggering a Full Device Wipe or not.
- Click on "Next"

Hint

For further information about the required Source Tenant's fields, please read Required environment’s information.

For further information about the DEP related options, please read the Apple's DEP Workflows section.

For further information about the Android Enterprise options, please read the Google's Android Enterprise Workflows section.

Target: provide the following details about your Target Tenant:
- The EMM server type.
- A list of specific fields which depends on the EMM server type chosen above.
- Click on "Next"

Hint

For further information about the required Target Tenant's fields, please read Required environment’s information.

Summary: you can see the name of the Migration, the date it was created, information about the host source and information about the host target, as well as the provided description.

Caution

Please pay attention to those details and make sure they are correct.

Click Save. Exodus will then:
- Look up for the list of users and devices in the Source Tenant.
- Look up for the users in the Target Tenant.
- Create the Device List.

Note

It may take a bit of time, depending on the number of devices you’re about to migrate.

If your Migration includes any DEP devices, you'll need to do some additional steps before you can start the migration of those devices. See the Apple's DEP Worflows section for more details.

Your migration is now ready to begin and you have the option to either:
- Click on the "Start all ready devices" button to start the migration of all your devices in a Ready state at once.
- Click on the ⋮ Group Device Action button to trigger an action on the filtered devices.
- Click on the ⋮ Device Action button to trigger an action on the related device.

Hint

For more details on the various device actions you can trigger please read the Device List & Actions below.

Required environment's information

These instructions depend on the type of EMM you're using. Please choose the appropriate one in the list below:

Credentials error

If the credentials of the EMM administrator happen to become invalid, Exodus will no longer be able to execute the required commands on the EMM server, thus preventing devices from updating their status and progressing through the migration. When Exodus detects that EMM credentials have become invalid, the faulty Migration is highlighted in red in the Dashboard. In the Migration details, you can renew the credentials by clicking on the red "Credentials" button below the EMM icon.
All the Instance Administrators will be notified by email.

Hint

If you use credentials with a set expiration date, do not hesitate to renew these pre-emptively to avoid any service interruption.

Hint

Beware that a credential error may be triggered for a variety of reasons, such as insufficient permissions to perform a specific command or the EMM server's authentication service being temporarily unavailable. Therefore a Migration marked as having invalid credentials may still be able to proceed normally. Exodus tries to avoid reporting false negatives by ignoring errors that occur for less than 30 seconds.

Device Statuses

The device migration statuses are shown in the Status column of the Device List.

In order to keep the interface as clear as possible, some statuses are grouped and further details are only visible as tooltips (by moving your mouse cursor over the statuses).

Note

The statuses order follows the migration process. Which means the more you go down the list, the more you'll see devices getting closer to being fully migrated.

Here is the list of all the statuses with their tooltips.

Column	Tooltip	Description
Failed	{Error description}	The tooltip describes the failure reason. See Failed sub-statuses below.
Getting ready	Looking for User on Target Tenant	The device was found on the Source Tenant. Exodus is now searching for an associated user on the Target Tenant.
	DEP sync ready	The device is enrolled through Apple DEP and is waiting to be synced on Target Tenant. See DEP Workflow for more information.
	DEP sync started	The device is enrolled through Apple DEP and is currently being synced on Target Tenant. See DEP Workflow for more information.
Ready	–	The device is ready to start its migration: it has a valid user on the Target Tenant and, if it's a DEP device, it has been synced on the Target Tenant.
Started	User notified	The user has been notified by email to install and open the Companion App.
	Companion App installed	The installation of the Companion App has been detected on the device (iOS only).
	Companion App launched	The user has opened the Companion App at least once but has not initiated their device migration yet.
Un-enrolling	–	The device is being un-enrolled from the Source Tenant.
Un-enrolled	–	The device has been un-enrolled from the Source Tenant.
Re-enrolling	–	The device is re-enrolling on the Target Tenant.
Re-enrolled	–	Congratulations! The device is re-enrolled on the Target Tenant.

Failed sub-statuses

Target user not found: The listed user in the Source Tenant can not be found in the Target Tenant therefore Exodus does not authorise the device migration.
Duplicate device: The device has already been listed in an existing Migration. As Exodus does not support duplicate devices, you must delete that device record using the Device Action and let the device migrate via the previously created Migration.
Unsupported device: The device is not supported by Exodus. See Support Matrix for compatibilities.

Device List & Actions

An "Export" button will generate and let you download a .csv file of the Device List. The export follow the filters parameters.

There are some actions you can perform on a device using the ⋮ button available at the end of the device's row.

Note

Some of those actions can be performed on multiple devices at a time, using the same ⋮ button available in the header of the Devices List. Those actions are performed on the eligible filtered devices.

Start migration

This action starts the migration process of a device. It is only available on devices with Ready status. After performing this action, the status changes to Started.

Resend email

This action resends the migration notification email to the user associated to the device. It is only available if the user has already received the original email and has not pushed the Start Migration button on the Companion App yet (status Started).

Send notification

This action sends a notification to the device. It is only available during an ongoing migration, the Companion App must have been installed and started at least once on the device. Depending on the migration state of the device, the content of the notification can change.

Note

On iOS, the user must allow the Companion App to display notifications.

Note

This feature is not available for the macOS platform.

Notification content

Status	Notification title	Notification content
Started	Start your migration	Launch the Exodus Companion app to start migrating your device to your new EMM.
Un-enrolling	Continue your migration	Launch the Exodus Companion app to continue migrating your device to your new EMM.
Un-enrolled	Finish your migration	Launch the Exodus Companion app to finish migrating your device to your new EMM.
Re-enrolling	Finish your migration

Automatic notification

Independently from any admin triggered notifications, the Companion App has a built-in timer which initiate these same notifications automatically on both Android and iOS.

Automatic notifications schedule is as follows:

Notification 1: t0 + 6 hours
Notification 2: t0 + 18 hours
Notification 3: t0 + 42 hours
Notification 4: t0 + 90 hours

Timer will reset for each status change or at the last triggered notification from the Console Send Notification Device Action.

Remove device

This action delete the device record from the Migration. This action does not trigger the device un-enrollment, it is used to remove portential duplicate devices or help the Administrators trim the Device List.