Considerations for migrating to Google Groups
Updated February 16, 2017
Most mailing lists can now be successfully migrated to Google Groups using the migration tool. Unless your list falls under one of the following categories, please visit the Migrate to Google Groups page now to begin the migration process.
Lists requiring review prior to migrating:
- Lists that want to preserve existing Sympa archives.
List archives kept in Sympa Mailing List Manager (Lists@CASE) cannot be moved to Google Groups. Your new Google Group will archive future messages by default in a feature-rich, user-friendly online forum. If you wish to preserve the Sympa archive, list owners or moderators may download the archives as a ZIP file and save them to Google Drive for sharing with others.
Once you have downloaded the Sympa archives, use the migration tool to convert your list to Google Groups.
- Lists that use the anonymous sender setting.
Google Groups does not have an equivalent to the anonymous sender setting in Sympa. Please review how anonymous sender is used for your mailing list before attempting to migrate to Google Groups.
- If you decide Google Groups will meet your needs without this functionality, please remove the anonymous sender setting from your list in Sympa, then use the migration tool to convert to Google Groups.
- If you decide your Group will still need this functionality, please open a help desk ticket with a detailed explanation as to how anonymous sender is currently used for your mailing list. UTech will work with you to try to find a supportable solution.
Lists that should not be migrated at this time:
University Technology, UTech is actively researching a possible solution for the following two scenarios and will announce progress updates in future communications of the migration project. Please do NOT migrate your list if it:
- Populates from Lightweight Directory Access Protocol (LDAP) or a database.
Some lists receive subscribers directly from LDAP or a database and should not be migrated at this time.
- Uses the “include_list” setting.
The “include_list” setting allows a parent list to be populated directly with the members of its child lists. This is different than nested lists. The “include_list” setting is commonly used to manage posting permissions for an entire list.
If your list does not fall into one of these four categories, please visit the Migrate to Google Groups page now to begin the migration process. For assistance with migrating to Groups, contact the UTech Service Desk at 216.368.HELP (4357) or email@example.com.