com.sec.android.easyMover Copy

"Smart Switch", the user-facing Samsung app for moving content onto a new Galaxy device. Samsung describes it as transferring all your content from an old phone to a new Galaxy phone, states plainly that it only works in that direction ("You may only transfer content from a non-Galaxy phone to a Galaxy phone with Smart Switch; it does not work the other way around"), and notes it can also back a device up to external storage. Its background helpers, the Smart Switch Agent (com.sec.android.easyMover.Agent) and Smart Switch Assistant, are documented separately on this site; this entry is the app itself, recorded as user-facing in 36 of our 52 observations and signed with Samsung's platform key. For Android Enterprise, EMM and kiosk work this is the one Samsung has actually written enterprise policy for, and the default is not what most admins expect. Samsung's knowledge base for fully managed (device owner) devices states that Smart Switch is not enabled on fully managed devices by default, because it was not designed for enterprise environments, and that a user who tries sees "Security policy restricts use of Smart Switch". That article gives its environment as Knox Platform for Enterprise on fully managed devices running Android 9 and 10, and was last updated in July 2023, so read its scope as stated rather than assuming it covers every release. An administrator re-enables it deliberately. Samsung's documented route is managed app configuration: find the "Samsung Smart Switch Mobile" app in the EMM and turn on the "Allow SmartSwitch Run" option. Samsung attaches two caveats to that workaround, both worth knowing before you plan around it: it is intended for devices running Android 9 and above and may not work on earlier versions, and it cannot be used to enable Smart Switch on fully managed with work profile (DO plus PO) devices, because the managed app configuration cannot be applied in the device owner space. Knox Service Plugin exposes the same control device-wide as Device Restrictions > Allow Smart Switch, set to True to allow it, and setting it to False is the documented way to prevent its use. Version note, and it is pinned to the app rather than to Android. Samsung documents the app as disabled by default on fully managed devices starting with Smart Switch version 3.7.05.8. That statement is made in the Android 9 and 10 context described above, and Samsung does not say whether the same default still applies on newer Android releases, so verify against your own firmware rather than assuming it carries forward. Our sample spans both sides of the version line (Smart Switch 1.0.00.7 through 3.7.72.6, on devices from API 33 to API 37), so a mixed fleet will be carrying app builds either side of it. Because Samsung ships an explicit, reversible policy for it, prefer the policy over disabling the package: it is documented, and it leaves a migration path you can turn back on. On a dedicated or kiosk device that will never be migrated, blocking the app outright is reasonable, but test on one device first, as a data transfer or restore flow can depend on it.

• Smart Switch frequently asked questions - Samsung Support →
• How to enable Smart Switch on Fully Managed (DO) devices (KBA-298) - Samsung Knox Documentation →
• Enable Smart Switch with Knox Service Plugin (KBA-1387) - Samsung Knox Documentation →
• Device restrictions - Knox Service Plugin, Samsung Knox Documentation →
• Package provenance for com.sec.android.easyMover - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, and that single certificate is consistent across all 19 device profiles. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 234 permissions: 15 runtime (user-granted), 35 signature or system-level, 24 install-time and 160 vendor or uncatalogued.
• APK size ranges from 0.3 MB to 41.7 MB across the reporting device profiles, so the build differs substantially between them.
• Reported as an updated system app on 28 of 19 profiles - a newer build is installed over the one in the system image there.