> 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/package-store/package-migration.md).

# Package Migration

Packages can be migrated to "Managed" if previously deployed as "Basic".

{% hint style="warning" %}
Package migration is only available for **RealmJoin** packages
{% endhint %}

## Identifying Packages

Currently only RealmJoin packages can be migrated from Basic to Managed deployment. This can be identified from the Packages table:<br>

<figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FlwCxNzo8vWbyzYTGSVPL%2Fimage.png?alt=media&amp;token=634e3140-c165-418a-b787-3c4289e9101d" alt=""><figcaption></figcaption></figure>

## Migration

1. Select a Basic RealmJoin package
2. Under Group Assignments, select More -> Convert to managed app (This process happens immediately).
   * Old groups are nested into the new Managed RealmJoin Groups. Settings made to the Basic groups will be adopted by the Managed groups.<br>

     <figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FObw0jcTQ0A7FtnKDHtAk%2Fimage.png?alt=media&amp;token=f3dc43b2-7b19-49d5-95e2-13ba2d462bae" alt=""><figcaption><p>Before Migration</p></figcaption></figure>

     <figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FSQIb1asGXoiG1bcMSJZV%2Fimage.png?alt=media&amp;token=6d872b0f-a838-48bc-9a6f-30a3b54f0564" alt=""><figcaption><p>After Migration</p></figcaption></figure>
   * Users are added to the most relevant group

     <figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FjrlZD00dlMlARzfZelV5%2Fimage.png?alt=media&amp;token=155d3309-95c0-4ccd-8945-3a99f7dae226" alt=""><figcaption><p>Before Migration</p></figcaption></figure>

     <figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FDX3jFnHgwXvMCKQleXN0%2Fimage.png?alt=media&amp;token=54daa930-a2fd-4005-a26a-e7d1de9d7862" alt=""><figcaption><p>After Migration</p></figcaption></figure>
3. (Optional) Pull members from nested groups directly into the RealmJoin managed groups. This setting migrates users directly to the RealmJoin managed group and optionally removes the nested group from the Managed group.
   1. Select relevant group -> More -> "Pull members up".
   2. Select the ![](https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FjgdAOi6MqRIwr9ej7kIE%2Fimage.png?alt=media\&token=a5796714-3845-4abf-b817-fda639e421c0) on the desired nested group
   3. Choose "Remove Assignment" to remove the nested group or "Keep Assignment" to keep the nested group in the RealmJoin managed group
   4. Click Execute to begin the operation<br>

      <figure><img src="https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FHCS9QnvLCQiN4Yc2uMxM%2Fimage.png?alt=media&amp;token=8da99fb2-2903-4487-84a0-b6163f15ccaa" alt=""><figcaption></figcaption></figure>


---

# 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/package-store/package-migration.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.
