Group preservation during move to teams

Regardless of the group management experience you are currently on, you will soon be moved from Groups (Sharing) to teams. For more information about Groups (Sharing), refer to the following resources depending on your group management experience:

• Legacy group management experience
• Organizational group management experience
   

Lucid accounts are moving on a cohort basis. You will receive an email specifying your scheduled move date; no action is required on your end, as the transition will happen automatically on that day.

This change improves how your teams collaborate by moving your account to a single, unified standard – Lucid teams. This transition is designed to simplify your administrative workflow and improve the end-user experience:

• Reduced Administrative Load: Manage your organization with ease—admins no longer have to navigate complex hierarchies of Teams, Groups, and Repositories.
• Seamless Transition: Users retain all document access and sharing settings through ID-based migration; all permissions remain identical.
• Unified Experience: Collaborators can focus on sharing with the right people without needing to distinguish between different entity types.

Here are the main points to know:

1. Legacy Groups (Sharing) will be moved to teams
2. End users will be placed in corresponding team hubs

Move to teams
Your existing sharing groups will be moved over to teams in the admin panel.

Please note the following:

• Any duplicate names (i.e. if a team already exists with the same name as the legacy sharing group) will be moved in with a number at the end of the name. For example, if a “R&D” team already exists, if there is a legacy group called “R&D” it will be renamed to “R&D [1]” when it is moved to teams.
• Team hubs do not support nested sub-teams. Because of this, any child groups from the legacy experience will be converted into standalone team hubs, and their original parent/child relationships will be removed. For example, a legacy parent group named “Product” with child groups “Product Team 1” and “Product Team 2” will be reorganized into three separate, equal team hubs: one for the parent and one for each child group.

Team hub permission and roles
The existing users and their associated permissions will be preserved and placed into corresponding team hubs. Team hubs provide a unified experience for accessing team spaces, adding team members, and opening team documents. To learn more, check out our Use team hubs in Lucid to collaborate and stay organized article.