> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/admin-corner/account-and-endpoint-management/new-groups-and-settings-management-experience-explainer/migration.md).

# Migration

### Migrating to the new groups experience is a wizard-assisted process with pre-migration conflict testing

#### <mark style="color:blue;">Enablement status varies by account type and existing group count</mark>

The new groups and settings management experience is being rolled out based on account type and the number of existing groups on the account as of January 10, 2026. New accounts created after that date default to the new experience automatically. Existing accounts with zero or one group as of January 10, 2026 were automatically updated to the new experience.

Existing accounts with two or more groups must request access to the self-service migration flow by creating a support ticket through [Zoom Support](https://support.zoom.com/).

### The migration wizard guides administrators through four steps: Select groups, rank priority, test, and confirm

For accounts with two or more groups, the migration is completed through a wizard-assisted process in the Admin console. The wizard walks administrators through four steps:

{% stepper %}
{% step %} <mark style="color:blue;">**The administrator selects which existing groups should retain their settings configurations**</mark>

Unselected groups are migrated as settingless groups and default to account-level settings. The wizard automatically identifies groups that have settings differing from the account level and pre-selects them.
{% endstep %}

{% step %} <mark style="color:blue;">**The administrator ranks the selected groups by priority order**</mark>

By default, groups with the fewest members are assigned the highest priority based on the assumption that smaller groups are typically exception groups that should take precedence in the new experience. Groups with more members receive lower priority, and groups with no members are given the lowest priority. Administrators should review and adjust these default assignments to align with their organization's structure.
{% endstep %}

{% step %} <mark style="color:blue;">**The administrator runs a migration simulation that generates a CSV conflict report**</mark>

This report compares before-and-after settings values for all affected users, identifying any settings that would change as a result of the new priority assignments. If conflicts are detected, the administrator can return to the previous step, adjust priorities, and re-run the simulation.
{% endstep %}

{% step %} <mark style="color:blue;">**The administrator reviews the final priority order and confirms the migration**</mark>

Generating the CSV conflict report can take anywhere from 10 minutes to 12 hours, depending on the number of users and groups in the account. The final confirmation step is immediate.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Zoom Recommendation:**

Zoom recommends testing the migration on a sandbox account before migrating to production, as well as running the production migration after business hours.
{% endhint %}

For step-by-step procedural details, see the Zoom Support article [Using the new groups and settings management experience](https://support.zoom.com/hc/en/article?id=zm_kb\&sysparm_article=KB0076377).

### Migration preserves all existing group settings and lock values and only adds the priority attribute

Migrating to the new experience does not reset or modify any existing group settings or lock values. All groups retain their current configurations exactly as they were before migration. The migration process adds the priority attribute to existing groups and enables the new modular group configuration capabilities. Group UUIDs are also unchanged by the migration, so any existing API integrations or automations that reference groups by UUID continue to work without modification.

### The migration process is non-destructive but final

Administrators can cancel the migration at any point before the final confirmation step without making changes to the account. Once the migration is confirmed, it is final and cannot be undone.

Administrators should use the simulation and conflict report referenced in [step three above](#the-administrator-runs-a-migration-simulation-that-generates-a-csv-conflict-report) to verify that the new priority assignments produce the expected results before confirming.


---

# 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://library.zoom.com/admin-corner/account-and-endpoint-management/new-groups-and-settings-management-experience-explainer/migration.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.
