Import applications from MECM server (formerly SCCM server)

Import applications from MECM server (formerly SCCM server)

The Robopack MECM migration tool can be used to read application information and content from a local MECM server, and upload the selected packages to Robopack, automatically converting them to IntuneWin so they can be imported to Intune.

The tool comes as a single executable, requires .NET Framework 4.7.2, and does not require installation.

You can run the tool with a user account that has access to the MECM server, or manually specify a user account and password with the necessary permissions.

Download the migration tool

Download the migration tool here: 

Run the .exe file to start the tool

Login to Robopack


Login with your Robopack username or password or with an associated Microsoft Entra ID account.

Enter the hostname of the MECM server


If the current Windows user account has access to the MECM server, you need only check the User current user account box and press Connect.
Otherwise, enter the username and password for the user account to use for connecting to the server.

Select the applications to import

Select the applications to import and decide if they should be imported as IntuneWin or converted to MSIX packages.


Start import to Robopack

Click the Start import to Robopack button to start the process of importing the selected applications to Robopack. The imported applications will be visible below on this page and also in the normal list of applications.

Translating broken content locations
In some cases the content locations specified for packages in the MECM may no longer be accessible, and the upload to Robopack will fail because the source files cannot be accessed.
If the content is present on another share or in a local folder, you can specify in Settings the content location(s) to be translated.

Example:
Entering \\server1.local\share and \\server12.domain\new_share will translate the content location of a application from \\server1.local\share\7-Zip 16.05 to \\server12.domain\new_share\7-Zip 16.05.

    • Related Articles

    • Robopack Trial Guide

      Robopack Trial Guide Welcome to the Robopack Trial! This form is designed to ensure you get the most out of your Robopack trial. By filling out this form and testing features listed in this guide, we can ensure that you experience the full range of ...

    • API Documentation

      Robopack v1 API documentation Overview Robopack provides versioned API access. This document describes the v1 API which is designed to be static even as features are added to Robopack. The v1 API supports a limited subset of Robopack functionality ...

    • How to Use Instant Apps in Robopack

      How to Use Instant Apps in Robopack Robopack’s Instant Apps feature makes it easy to find software, keep it automatically updated, and control how new versions are deployed across your organization. This guide walks you through searching, analyzing, ...

    • What permissions do Robopack require to work with Intune?

      Permissions needed for the Robopack graph integration, Connect Tenant (Admin Consent) Permission Required Purpose Graph User.Read Yes Authenticate users with their Microsoft account Graph openid/profile/offline_access Yes Graph Organization.Read.All ...

    • Rolebased Access Control and Permissions

      Robopack permissions and roles Overview Robopack supports limiting access to areas of the product and to Intune tenants. This document describes the ways in which users can sign in to Robopack and how their access can be managed. User account types ...