Status

Owner

Gautier Todeschini, Dawn Lai

Stakeholders

James Kyndt, Frank Bolata, Boris Foiselle


Decision: Option 1: All labels to folder

Decision made by: Business Reps. (GBU/GBS/BSA)

Date:  

Online Meeting: Regular updates / Microsoft Transformation Program - GBU/GBS/BSA connection

Issue

Gmail uses a label-based system that supports multiple nested sublabels, while Microsoft 365 relies on a traditional folder hierarchy with different technical constraints.

The migration path is not a 1:1 and a choice has to be made on if/how to replicate this email categorization.

Recommendation

Adopt the Option 2 “No Labels” approach for the migration which will not create duplicates.

Users should be informed that their Gmail labels will not be preserved. 

Background & Context

Key Differences

Feature 

Labels (Gmail)

Folders (M365)

Location

One email stays in "All Mail".

Email moves to a specific folder.

Quantity

One email can have multiple labels.

One email resides in only one folder.

Archiving

Removes the "Inbox" label; the email remains in "All Mail".

Often moves the email to a separate Archive folder.

Visibility

Email is visible under every label applied to it.

Email is only visible in its designated folder.

Assumptions

Constraints

Impacts

Users will see changes in how their mail is organized after moving from labels to folders. This can cause confusion, slowdown in daily work and increase in support requests. 
Mailbox sizes may also increase, creating additional management overhead if storage limits are reached. Clear communication and guidance will be needed to ease the transition.

Options considered


Option 1 “All labels to folder"

For each label applied to an email in Gmail, one copy of the same email is created and stored in a corresponding folder in Outlook. The labels are all converted to Folders/subfolders and the mail is saved in all folder representing all labels. This means every mail will be duplicated by the number of labels attached.

Option 2 “No labels”

Emails are migrated without creating any folder in Outlook, and will all be in the inbox. Labels aren’t migrated at all. All mail lands in a simplified folder structure Inbox. Users lose their Gmail organization, but avoid duplication and hierarchy issues.


Option 3: Migrate labels to Categories (The technical team has determined that this option is not viable).

Some 3rd party tools try to transform labels to categories, but the functionality of categories is different from google labels. Categories are mainly a color coding system on items and do not provide a hierarchy as with google labels.

Evaluation


Option 1 “All labels to folder"

Option 2 “No labels”

Option 3: "Migrate labels to Categories"

Technical Feasibility

(minus) 124 mailboxes would reach the maximum storage capacity requiring cleaning and specific actions from their owners

(minus) More difficult to revert due to duplicates & hierarchy

(plus) Easy to implement and easy to revert.

(minus) 54 mailboxes would reach the maximum storage capacity requiring cleaning and specific actions from their owners

(minus) The mobile app has limitations compared to desktop and web versions in terms of Categories.

(minus) Users can assign but cannot create, rename or delete categories in the mobile app.

User Impact

(plus) The “organization” of the mailbox is preserved: employees will find folders

(minus) Outlook Folder hierarchy may conflict with the way Gmail labels are structured, resulting in a different folder structure than the initial label structure

Degraded search experience (multiple results)

Risk to create an “email multiverse” if “variations” of the same email loops are created by following-up on different copies of the same loop

(plus) Clean search experience (single emails, all in the inbox)

(plus) Rules can be applied by the users after migration to restructure their mailboxes, in a way that is native to Outlook

(minus) All mails will be in inbox and need to be restructured again in the new folder structure
Users will be educated to use rules to automate as much as possible.

(minus) To search or filter on categories you need to create a search folder which is not portable so needs to be created on all devices and is not available on mobile app.



 

Operational Complexity

(minus) Estimated overall growth of mailbox sized: +30-35% resulting in more recurrent cleaning activities required and more upcoming mailbox size issues to manage

(plus) Leaner approach as data will not be duplicated

(minus) Categories are mostly color coding and not transformed to a folder structure and colors are limited to 25 colors.

(minus) No tool can convert nested label hierarchy

GBU/BSA/GBS Feedback(plus) 7/11 votes(minus) 4/11 votes (November 25th "GBU connection" call)
Cost(minus) Storage costs could arise on the long term (on top of the operational complexity)(plus) Lower Cost and lower environmental impact

Cost of the tool needs to be considered,

Implementation time and governance needs to be considered

Champions and IT Pioneers were consulted and both groups voted in majority for Scenario 2,
which is also the project’s recommendation (leaner and less confusing).




See also

The following section describes relevant documentation:

Description

Repository

Workshop presentation
1.3 Teams & Collaboration Design
Workshop meeting minutes
Workshop meeting minutes
HLD:
6.Collaboration, page 99,
6.6Onedrive Sync page 103
1. SYENSQO-Microsoft365 High-Level Design v1.docx