> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups/legacy-preset-groups.md).

# Legacy preset groups

If your organization has **legacy preset groups**, they appear in the **v1 (Legacy)** tab. Updated preset groups appear in the **v2 (New)** tab.

Legacy preset groups use an earlier schema that is incompatible with current filtering infrastructure. Migrating them ensures compatibility and enables full use of the Presets tab.

**Legacy preset groups**:

* Can be [viewed](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#view-preset-group-contents) and [downloaded](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#download-a-preset-group).
* Cannot be [edited](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#edit-a-preset-group) or [hidden](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#hide-unhide-a-preset-group).
* **Cannot be used** in case review until migrated to v2 schema (the **Presets** tab is inactive when a legacy group is applied).

## Migrate a legacy preset group to v2 schema

{% stepper %}
{% step %}

### Download the legacy preset group configuration file

1. In **Organization Settings** → **Lab workflow** → **Preset groups** → **v1 (Legacy)** tab, locate the preset group you want to migrate.
2. Select the <i class="fa-arrow-down-from-line">:arrow-down-from-line:</i> **Download** icon on the right.

The file containing the preset group definition — including preset logic, preset names, and preset order — is downloaded in JSON format.
{% endstep %}

{% step %}

### Upload the file as a v2 preset group

1. In **Organization Settings** → **Lab workflow** → **Preset groups** → **v2 (New)** tab select **Add new**.
2. From the dropdown, select **From file**.
3. Upload the JSON file. The system validates JSON format and schema (structure, field names, field values, and file name). If validation succeeds, the preset group is created.
   {% endstep %}
   {% endstepper %}

**Result:**

* A new **v2 preset group** is added to the **preset groups** list in the **v2 (New)** tab. It becomes available during case creation and can be [viewed](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#view-preset-group-contents), [edited](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#edit-a-preset-group), [hidden](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#hide-unhide-a-preset-group), or [downloaded](/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups.md#download-a-preset-group).
* Any presets referenced in the JSON file that do not already exist in your organization are automatically added to the presets table.
* When the migrated preset group is active in a case, the **Presets tab** becomes active again.

## Revert a migration

To delete a v2 version of a legacy preset group:

1. In **Organization Settings** → **Lab workflow** → **Preset groups** → **v1 (Legacy)** tab, locate the migrated preset group you want to revert.
2. Select the <i class="fa-arrow-u-turn-down-left">:arrow-u-turn-down-left:</i> **Revert** icon on the right.

{% hint style="info" %}
**Note:** If a migrated v2 group is set as the default, it cannot be reverted.
{% endhint %}

**Result:** The corresponding **v2** version of the **legacy** preset group is removed from the **v2 (New)** tab.


---

# 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://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/settings/organization_settings_-330+/lab-workflow/preset-groups/legacy-preset-groups.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.