> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/application-management/packages/migration-guide-realmjoin-to-intune-managed-packages.md).

# Migration Guide: RealmJoin to Intune Managed Packages

This document outlines the best practices for transitioning package management from RealmJoin managed packages to Intune managed packages.

{% hint style="warning" %}
We recommend staying with RealmJoin managed packages. Several package options are only available with the RealmJoin Agent, see [Deployment Methods](https://docs.realmjoin.com/application-management/deployment-methods.md#feature-comparison). Do not run RealmJoin and Intune managed packages in parallel for the same package or package family; use one deployment method per package to avoid conflicting installations.

Consult your RealmJoin solution architect before starting this migration.
{% endhint %}

### Key Concept

The RealmJoin and the Intune version of a package use the same detection fingerprint. The Intune package therefore detects installations made by the RealmJoin package as installed:

* Detection rules do not need to be reconfigured.
* Devices that already have the software are not reinstalled.
* Inventory and reporting continue across the switch.

### Migration Process

#### Step 1: Rename the RealmJoin Managed Package

Begin by renaming the existing RealmJoin managed package to free up the package name for reuse. This step is essential as Intune managed packages will use the same or similar naming convention.

**Actions:**

* Access the RealmJoin management portal
* Locate the package in the package management section
* Rename the package with a deprecation indicator (for example, append "\_legacy" or "\_deprecated" to the original name)
* Document the new name for reference

#### Step 2: Subscribe to the Intune Managed Package

After the RealmJoin package has been renamed, proceed with subscribing to the equivalent Intune managed package.

**Actions:**

* Navigate to the RealmJoin store
* Locate and select the package you wish to migrate to
* Complete the subscription process as Intune managed
* Verify that the package is properly registered in your Intune environment

**Note:** Use the original package name (now available after renaming the legacy package) to maintain consistency in your package naming schema.

#### Step 3: Transfer Users Using Bulk Operations (optional)

Transfer users from the RealmJoin managed package to the Intune managed package using the bulk operation function available in RealmJoin.

**Actions:**

* Access the managed groups of the Intune package
* Under the *More* section, select *Bulk Operations*
* Execute the bulk reassignment to the new Intune managed package
* Monitor the operation progress and verify successful transfers

<div><figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FxvLsc4jc7prpTB742zcn%2F25-10-21-11_28_41_msedge.png?alt=media&amp;token=adc6536d-1a9f-4b69-aeaa-a93ac1d9fa18" alt="Selecting the bulk operation feature to copy all users from a existing group"><figcaption><p>Selecting the bulk operation feature to copy all users from a existing group</p></figcaption></figure> <figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FzqPvdxgt5MWWDkzAr61P%2F25-10-21-11_28_58_msedge.png?alt=media&amp;token=bf7f9953-6606-42fc-99b0-b18aa9e70a23" alt="Execution of the bulk operation. Users are added to the new group, a log is available for your reference."><figcaption><p>Execution of the bulk operation. Users are added to the new group, a log is available for your reference.</p></figcaption></figure></div>

### Post-Migration Verification

After completing the migration, perform the following verification steps:

* Verify all users have been successfully transferred to the Intune managed package
* Confirm that package detection is functioning correctly on client devices
* Check that no users remain assigned to the legacy RealmJoin package
* Review deployment status and ensure packages are installing correctly
* Validate that inventory and reporting data reflects the new Intune managed package

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FclyM1rk12TUpDtUdFDZZ%2F25-10-21-09_24_05_vmconnect.png?alt=media&amp;token=26413ec4-93d0-4531-8d1c-6b20df2a1b6b" alt=""><figcaption><p>Available package is installed / updated via the company portal.</p></figcaption></figure>

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FMC4hQh3Xom2WCb5QNxFN%2F25-10-21-09_25_52_vmconnect.png?alt=media&amp;token=84fc9128-b8ee-44d6-bfd4-8006d8c34cc5" alt=""><figcaption><p>Mandatory assigned Intune package is updated.</p></figcaption></figure>

### Rollback Considerations

Should issues arise during migration:

* Retain the renamed RealmJoin package for a minimum grace period to enable potential rollback
* Document all migration steps and timestamps for troubleshooting
* Have a clear rollback procedure in place before beginning the migration
* Test rollback procedures in a non-production environment first
* Provide all information including full log files in any support ticket


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/application-management/packages/migration-guide-realmjoin-to-intune-managed-packages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
