> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/archive/migration-process.md).

# Migration Process

Migrating from Launcher 3 to Launcher 4 equips your devices with the latest feature enhancements, new functionalities, and improved performance. This guide provides step-by-step instructions for both manual and automated methods to meet your deployment needs.\
\
The manual process follows a standard procedure including checksum validation to ensure APK integrity. The automated process leverages the Launcher Migration Tool, making the transition to the latest version.\
\
With this guide, you can confidently upgrade to the latest BlueFletch Launcher, keeping your devices optimized and operational. Whether managing a few devices, deploying at scale, or rolling out enterprise-wide, the migration process is designed to be straighforward and reliable.

### Manual Process

1. Navigate to your BlueFletch Portal and go to **Admin > Beta > Downloads**.
2. Download the latest version of Launcher 4 (or a desired previous version).
3. (Optional) Use an MD5 tool to generate a checksum for the downloaded APK and save it for future reference.
4. Retrieve the checksum from **Admin > Beta > Downloads** and compare it to the one generated in the previous step.
5. Install the downloaded application on a device currently running Launcher 3.
6. Uninstall the previous Launcher 3 version using the following command:

`adb uninstall com.bluefletch.launcher (or the relevant BlueFletch package name)`

6. Install the new Launcher 4 APK using the following command:

`adb install {EMS Launcher apk file path}`

### Automated Process

1. Navigate to your BlueFletch Portal and go to **Admin > Beta > Downloads**.
2. Download the latest Launcher 4 Migration Tool.
3. Install the Launcher 4 Migration Tool on the device.
4. Use the dropdown menu where you downloaded the APK and select Copy URL to retrieve the Launcher 4 download link. The copied url should look similar to this:

[`https://somewhere.com/services/apiv1/files/download/1eb3f73-cbe3-44f4-a1bf-83bf`](https://ems-services-portal-staging.bluefletch.com/services/apiv1/files/download/1eb3f73-cbe3-44f4-a1bf-83bfca3603bf)

5. Run the following command to initiate the migration process:

`adb shell am start-n com.bluefletch.upgradetool/com.bluefletch.upgradetool.ui.silent.SilentInitActivity --es url "PATH_TO_LAUNCHER4_DOWNLOAD" --es orgId "YOUR_BF_ORG_ID" --es checksum "CHECKSUM_FROM_PREVIOUS_STEP”`

* To obtain the **URL**, navigate to **Admin > Beta Downloads** in your BlueFletch Portal and click Copy URL.
* To obtain your **orgId**, navigate to **Admin > Organization** in your BlueFletch Portal.
* To obtain the **checksum value**, navigate to **Admin > Beta > Downloads** in your BlueFletch Portal and click Copy Checksum.

Refer to the [Getting Started](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/getting-started) page to set up the Launcher configuration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher/archive/migration-process.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.