EBF Onboarder is a vendor neutral migration tool for moving mobile devices from one UEM system to another. It is not a permanent management platform: it sits between your source system and your target system, guides each device through re-enrollment, and then steps out of the way once the migration is done.

Companies switch UEM systems for many reasons: a newer platform may better fit their requirements or integrate better with other software, a cheaper alternative may offer the same features, a merger or acquisition may leave a company running more than one UEM and needing to consolidate, or a vendor may discontinue a product entirely. Whatever the reason, migrating devices by hand is a lot of manual effort, and this is the problem the Onboarder solves.

Onboarder supports more than 20 source systems and 7 target systems in total, so wherever your specific migration is headed, whether from MaaS360, Ivanti EPMM, or SOTI, onto Microsoft Intune, Jamf, or Workspace ONE, the same tool and the same workflow apply.

The dashboard gives an overview of every migration project, its source and target hosts, device counts, and completion status, all in one place.

Onboarder is used by four kinds of people, often on the same project:

• Project Managers get a single dashboard across every migration project, so status reporting does not require checking multiple UEM consoles. A tenant wide statistics view rolls all active projects into one report, exportable as CSV, Excel, or PDF for stakeholder updates.
• IT Managers get control over security and compliance behavior before any device moves. Multi factor options (PIN by mail, OTP, PassKey), language enforcement, and platform specific behavior toggles are all configured centrally, once, for every project in the tenant.
• MDM Admins get a live, per project view of exactly where each device stands: how many are done, compliant, noncompliant, or still waiting on communication. Source and target connections are shown side by side, so a broken connection or a stuck device is easy to spot.
• Resellers and Partners get a multi-tenant setup where the enrollment screens end users see during migration can be branded per customer, without touching code.

A single project view: source system, target system, connection status of both systems and a live migration status broken into a migration ring or (informed, not invited, done, compliant, non-compliant) and a communication ring (info, invited, reminded, welcome).

Every tenant wide setting, from authentication requirements, platform specific behavior, mail server settings and more is managed from a single settings screen, so nothing needs to be repeated per migration project.

General Settings for the complete tenant, special migrations behavior, authentication and security settings for admins, mail server settings, etc all live under Tenant Settings, active automatically to every project.

This documentation provides you with information about the EBF Onboarder, its prerequisites and the whole migration project. It describes how you can set up a migration project, how you can set up invitation emails and reminders which guide your users through the migration, and it also tells you how to initiate the migration process and how to track the migration status.

ATTENTION:

• For the target systems Ivanti (MobileIron), Jamf Pro/School, MaaS360, Microsoft Intune and Omnissa Workspace ONE there are separate documentations available which are important to read in addition to this one. You can find them here.
• For the source systems BlackBerry UEM v12 onPrem, BlackBerry UEM Cloud, Ivanti (MobileIron), Jamf Pro/School, MaaS360, Microsoft Intune, Omnissa Workspace ONE and Baramundi bMS there are separate documentations available which are important to read in addition to this one. You can find them here.