GWMHN release notes

• Active and Provision buttons have been disabled.
• 3-legged OAuth has been removed.

• G Suite Migration for HCL Notes is now Google Workspace Migration for HCL Notes (GWMHN).
• Updated the UI to refer to Google Workspace instead of G Suite.
• Removed prompt allowing the user to choose between normal and quick setup.

• Improved handling of Calendar API 403 responses.
• Middle names that appear in the Notes Fullname and FirstName and/or LastName field(s) are no longer applied as middle names in G Suite to prevent duplicate name elements in Google Contacts.

• Added a report to show migration status for users across multiple migration servers.
• The Migrate Again action can now be performed with multiple users.
• The migration calculator now supports up to 60 servers.
• Added a new view to show users completed by completion date/time.

• Fixed an issue where some events fail to migrate when applying a calendar cutoff date to the migration profile.
• Fixed an issue where events migrated from a server in one time zone for a user in another time zone failed to migrate correctly if the user’s home time zone included a 30 minute offset (e.g. India Standard Time at +5:30 UTC).

• Values that control maximum message and thread size are now configurable.
• Authentication URLs are now configurable

GAMIN network settings are now applied during Service Account token requests.

• Upgraded resource provisioning to use the new Calendar Resource object in the Directory API.
• Made administrator authentication end points editable.

Fixed a latency issue that prevented a group ACL from being retrieved and updated immediately after the group was created in G Suite.

Updated end points used for administrator authentication.

Fixed an issue where messages were being rejected by the Gmail API if the From header didn't contain a valid SMTP address.

• Service Accounts and OAuth 2.0 tokens are now used for data migration.
• GAMIN now uses the Gmail API for mail migration and label creation replacing the Email Migration API v2 and Email Settings API respectively.
• Flattened and simplified architecture:
  • Deprecated the multiple site/replicated admin database deployment option.
  • Setup and Site profiles merged into a single System Setup profile.
  • It is no longer necessary to specify mail/database servers as part of the system setup
  • Added a 5 step Quick Setup wizard.
  • Option to auto-update Domino directory Server and Configuration document settings required for migration.

Reduced migrate agent frequency from 30 minutes to 15 minutes.

Moved Import from File registration action from Notes menu to GAMLN Register menu.

Improved error handling when authorizing the tool, if the migration log and log template can't be found on the migration server.

Label creation:

• Added label migration statistics to the migration administration database.

Contacts migration:

• Added support for the following Notes fields: Address 3 details, Personal 2 email; Assistant phone, Business 2 phone, Home 2 phone, Blog site, Custom 1 field, Custom 2 field, and Custom 3 field.
• Moved Other email 1, Other email 2, Other email 3, and Personal Cell phone values from the Notes section to additional email/phone entries.
• Label values are now migrated to G Suite with the following exceptions. The first email address continues to map to "Work", the first phone and mobile numbers map to "Work" and "Mobile" respectively, and the first address maps to "Work".

• Added new feature to allow the GAMLN configuration to be exported in text format. This feature is available from the Actions menu in the migration administration database.
• Improved performance of bulk registration routine.

Run time errors were not being exported correctly from the GAMLN log databases. Errors now export correctly.

Users with the same full name in the Domino directory can now be successfully registered using the Register by Server method. Previously users with the same name were skipped as duplicate entries were present in the Domino directory.

Personal contacts with Anniversary item were failing to migrate to G Suite.

Personal contacts with no first, last or full name value in Lotus Notes were showing as “Unknown” after migration to G Suite. G Suite now shows the contact’s company name in the contacts list.

Organizer and attendee details are now shown on an attendee's imported copy of a Notes event. Previously attendee information was only added once the organizer was migrated.

Fixed issue with calendar quota, where calendar quota was being consumed by the domain admin account instead of the calendar owner during event migration. This could cause the migration server to exceed daily limits and the customer would need to wait 24 hours before migrations could continue.

Fixed weekly repeating event issue. Where the event occurs on a different day of the week for an attendee than it does in the organizer's time zone, the event would appear incorrectly on the attendee's calendar until the organizer migrated. Imported copies of events now appear on the correct day of the week even if the day is different in the organizer's time zone.

Added support for Email migration API v2.

Upgraded provisioning services to use the Admin SDK API.

The system now checks for the presence of the users/group during profile activation. Note: The system now requires product authorization as part of the system setup process. This was optional in earlier releases of GAMLN.

Deprecated automatic registration, provisioning and invitation options. These tasks are now performed manually from the migration administration database.

The event organizer name is added to event title on an attendee’s private ‘imported’ copy of an event. This is removed via fan-out once the organizer’s copy of an event is migrated.

External attendees are stripped from events when calendar migration test mode is enabled.

Added support for changes to metadata at the repeating event instance level. In addition to date/time changes, cancellations, and resource changes support offered in prior versions, R4.0.3 adds support for updates to event title, description, location, attendees (including status), availability, visibility, and notifications. 

Added support for Notes weekend rules. Notes events with weekend rules applied are treated as custom events and each instance is migrated as a separate single instance event. 

Added support for roaming users. Personal contacts and groups will now be migrated from a roaming user's personal address book on the server specified in the user's Person document. 

Fan-out support in calendar migration test mode. 

Issue: Incorrect Gmail username could be applied during registration if there is more than one user with the same name in the organization. Issue applied to single user registration, import from file and register by server. 

Resolution: Where duplicate names exist the administrator is now advised to register users from Domino directory to ensure the correct Gmail username is applied.

Issue: Contacts with fields larger than 1024 characters causes migration to stop for the user.

Resolution: These contacts are marked as errors but the migration is allowed to continue. 

Issue: Message IDs containing spaces or not bound with < and > were rejected during migration to a Groups Archive. 

Resolution: This issue has been resolved.

Issue: The requests per second/per user limit allowed for calendar migrations was being applied to the migration server's IP address and not the user account. 

Resolution: This issue has been resolved.

FYI attendees in Notes are added to the optional attendees list in Google Calendar.

Issue: A Notes custom event that could not be identified as a custom event (i.e. missing or empty RepeatUnit item) continued to be treated as a normal daily repeating event.

Resolution: These events are now marked as a Build error.

Issue: The From header in a migrated message was not being populated correctly where the Principal item on the Notes message was empty.

Resolution: This issue has been resolved.

Issue: Cancelled repeating meetings in Notes were not always marked correctly as Migrated\Cancelled in Notes.

Resolution: This issue has been resolved.

Notes custom events are no longer migrated as daily repeating events. For performance reasons each selected date on a custom event is now migrated a separate single instance event.

No attempt is made to migrate an event if it already exists on the user's calendar.

Individual Notes emails, events and personal contacts/groups can be excluded by the migration administrator from a new "Exclude Source Document" action that can be found in the feeder logs database.

Issue: Some instance cancellations that returned a successful HTTP response code from the API were not being passed to calendar correctly. This bug would leave cancelled instances on some attendees calendars until such time as the organizer's copy migrates.

Resolution: This issue has been resolved.

Issue: Handling of v3 API 403 errors generated by API during event migration.

Resolution: This issue has been resolved.

Support for migration of Notes discussion databases and document libraries to a Google Group. Mail-in databases can also be migrated to a Google Group or an Apps account as before.

Vault Support. Customers can now choose to migrate directly into Vault, bypassing the Gmail inbox.

Calendar migrations upgraded to use API version 3.0.

Use of OAuth 2.0 tokens for user, group, and resource provisioning.

New log database design: Events grouped by user/database. Ability to export events to a text file.

Merged detailed event logging and recording of migration exceptions into one feature.

Improved support for the display of names on delegated emails in Gmail.

Added support for middle names during contacts migration; the system will now migrate a contact that has no FullName item in Notes.

General UI cleanup.

Deprecated the following: Attachment repository, Migration error threshold, Generate XML admin feature, Current activity view, Maximum mail size setting - now matches Gmail maximum mail size.

Issue: Notes statistics could not be gathered for mail files 2Gb or larger.

Resolution: This issue has been resolved.

Issue: Calendar cutoff date now applies to event date not the event's creation date.

Resolution: This issue has been resolved.

Issue: A change to an instance of a recurring meeting that adjusts to midnight on the GAMLN server failed with a 404 Not found error.

Resolution: This issue has been resolved.

Issue: Notes stationery was migrated to Gmail.

Resolution: This issue has been resolved.

Issue: Exponential back-off not working when receiving a 500 response during calendar migration.

Resolution: This issue has been resolved.

Issue: Incorrectly setting familyName element in contacts when last name does not exist in Notes and FullName contains more than 2 words.

Resolution: This issue has been resolved.

New calendar migration test mode. Migrate events with full attendee details, but with no attendee fan-out. Events migrated using test mode are clearly identified as such in Google Calendar.

Reduced size and life span of Migration Status view indexes to offer better performance in the user's mailbox.

Miscellaneous UI improvements

Authorization

Issue: "Access denied" errors were occurring during authorization routines used for provisioning groups and resources.

Resolution: This issue has been resolved.

User Interface

Issue: Times were represented in minutes instead of hours in the Migration Statistics view.

Resolution: This issue has been resolved.

Migration

Issue: During label creation, an internal Notes 4005 error might be encountered for certain folder types. This was causing the routine to exit early, and the current user was marked as a 'Processing Failure'.

Resolution: Notes 4005 errors are now handled gracefully. The error is logged and the system proceeds to the next folder.

Resources

Issue: Duplicate resources were not resolved properly when resources were loaded into GAMLN multiple times.

Resolution: This issue has been resolved.

Empty folders in Notes are now created as labels in Apps.

Calendar migration performance is improved (as much as 50% faster in R3.1.3).

Added algorithms to compute values for missing fields on calendar events to improve calendar migration success rates. Previously, if a missing field meant that a valid recurrence rule could not be derived for an event, this would result in a migration failure.

Added support for old and alternate Notes names in Calendar migration.

Attachment repository URLs in migrated events now include web and Notes links.

Events with no subject are now migrated.

Mail migration now uses the original Message ID from Notes, where available. Previously, the apps domain name would be appended to the message ID value at migration time.

Resource email addresses are now editable in GAMLN. This is useful if resources were not created by GAMLN.

Phrase parts of email addresses are now removed during contacts migration.

Deprecated the ability to toggle the Folders Processed flag for one or more users. If this process needs to be run more than once for a single user, the admin must remove and re-register that user.

Calendar UID suffix field is now hidden.

Miscellaneous UI changes

Calendar

Issue: Free/busy status was not being displayed correctly for Notes imported holidays.

Resolution: This issue has been resolved.

Issue: Fully canceled recurring events retained in the Notes meetings view caused a build error in GAMLN.

Resolution: This issue has been resolved.

Issue: Canceled single-instance events retained in the Notes meetings view were being migrated from the organizer's calendar.

Resolution: This issue has been resolved.

Mail Archiving

Issue: Grouping of archived mail under "Archive" meant that labels could not be edited after migration, because "Archive" is a reserved name.

Resolution: Archived mail is now grouped under "Notes Archive".

Ability to disable out of office checks (for GSA Calendar migration).

Added calendar uid suffix field to address some coexistence issues.

Note: If you have already migrated some calendars with an earlier release of GAMLN, do not use GAMLN R3.1.2 for calendar migration; doing so can lead to duplicate events in your domain.

Migrating Groups

Issue: Domino groups wouldn't migrate if created in Notes R4 or R5.

Resolution: This issue has been resolved.

Configurable password length for user provisioning.

Unique feeder names. Site creation now checks the Domino directory for feeders with the same name to prevent multiple instances of GAMLN from using the same feeders.

Loading groups and resources prior to migration now sends detailed events to the administration log.

Web authorization page now sends detailed events to the administration log.

Provisioning Resources

Issue: A scope issue prevented resources from being provisioned.

Resolution: This issue has been resolved.

Migration Calculator

Issue: The "Total time to migrate" field was not being presented.

Resolution: This issue has been resolved.

Resource provisioning from Domino rooms and resources.

Resource calendar migration.

New user registration methods: 'Pick users from Domino Directory' and 'Import from file'.

Live migrations view. See real time migration activity by site.

Integrated migration calculator. Determine time and bandwidth requirements for selected users.

Connection test feature. Checks GAMLN and Google domain configuration. Also identifies any firewalls or proxy restrictions between the Domino server and the web.

Personal contacts now appear under 'My Contacts' after migration.

No dependency on operating system settings when migrating Notes calendars. A single GAMLN server can now migrate calendars across any number of time zones in a single migration run.

Google calendars no longer need to be initialized prior to Notes calendar migration.

User and group provisioning now uses three-legged OAuth. ClientLogin has been fully deprecated.

Recurring Events

Issue: Recurring events with large recurrence rules would generate an "RDATA Too Large" error during migration.

Resolution: These events can now be migrated properly.

Group Migration

Issue: A manager who is also the member of a Notes group would appear only as a member of the corresponding G Suite group following migration.

Resolution: This issue has been resolved.

Usernames

Issue: GAMLN did not support apostrophes in Gmail usernames.

Resolution: This issue has been resolved.

OAuth Support. GAMLN now supports OAuth authentication for migrating mail, calendars, and personal contacts.

Separate User Provisioning. User provisioning now runs separately from migrations, so users can be provisioned prior to migration.

Change password on login. Users provisioned by GAMLN are now forced to change that password when they first log in to Apps.

Enhanced logging mechanism. All migration events for individual users are now stored on the user's GAMLN profile. Agents that run in the GAMLN administration database such as Check Feeders and Migrate Directory now log events to a Notes Log database.

Improved Views. Views have been rationalized to make the system simpler to navigate. A new User View "Processing Failures," lists users who cannot be processed by GAMLN by reason type (such as "Unable to access mail database.")

Group Owners. Domino Directory group migration now supports Group owners.

The Restrict Access following migration feature has been deprecated.

Recurring Events

Issue: Many recurring events could not be modified after migration

Resolution: These events can now be migrated properly

Feeders build up queued mail for non-existence Apps users

Issue: Feeders would build up queued mail for non-existent Apps users.

Resolution: Accounts are now checked in G Suite prior to feeder population so that feeders do not build up queued mail for non-existence Apps users.

New Notes Statistics view. Allows administrators to gather migration document counts and sizes from user's mail files to help estimate migration times.

Error threshold. A new site-level value has been added that allows an Active user to move to Complete status if the number of migration errors in the user's mail file is equal to or less than the value specified. In earlier releases, any migration errors would keep the user at Active status and the administrator would need to change status manually to move the user out of the active queue.

Deprecated site-level migration end date. Customers can still specify a start date for migrations for each site. If they want migrations to end on a particular date, they must now disable migrations at the site level.

Removed option to disable the application of folder references prior to migration from the site level. This is now enabled for all registered users but can still be disabled using the "Toggle folder references" action against selected user profiles.

Migration would stop early if user's domain name was invalid

Issue: If the domain name for a user was invalid, the entire migration stopped.

Resolution: If the system encounters an invalid domain name for a user, it records the response as an authorization failure on the user profile, and then moves on to the next user.

Duplicate mail in database documents in the Domino Directory

Issue: Under some circumstances, there could be duplicate mail in database documents in the Domino Directory.

Resolution: The Check Feeders agent has been revised to eliminate the potential for duplicate mail.

Support for multi-domain management across all APIs.

Migration of Domino Directory data, beginning with groups.

Broader support for using date ranges. You can migrate mail from a specific date forward (start date), up to a specific date (end date), or between two dates. The end-date option is especially useful for companies who implement dual delivery as it lets you migrate mail up to the point of dual delivery, and then have the appropriate body of mail in each system.

Enhanced user provisioning that provides for the automatic generation of G Suite passwords when accounts are created. Passwords are included in the email notification to new users.

Active and Complete user views show the following detailed migration statistics for each user:

• Mail migrated
• Mail pending (new mail waiting to migrate)
• Mail unprocessed (mail that falls outside date ranges set for the migration)
• Migration errors (data rejected by the Google servers)
• Feeder errors (mail that could not be transferred to the feeders prior to migration)
• Excluded (mail excluded by things like folder rules or the junk-handling rule)
• Oversize email (mail not migrated because it exceeds the Google size limit of 25 MB)
• Encrypted mail (mail not migrated because it is encrypted in Lotus Notes)
• Calendar entries migrated
• Calendar entries unprocessed (entries that fall outside date ranges set for the migration)
• Calendar entry errors (data rejected by the Google servers)
• Contacts migrated
• Contacts errors (data rejected by the Google servers)
• Groups migrated
• Groups errors (data rejected by the Google servers)

The size column in the user views shows the actual amount of content in MB that is posted to Google. Previously, this value showed only the Notes mail-database size, which was misleading when verifying migration results.

Notification system enhanced to support the inclusion of tags to extract field values from System Setup and User profiles, in addition to Site profile.

Site- and User-level options to have the migration process include/exclude mail in the Lotus Notes Junk folder.

Site- and User-level controls to have mail from Notes archive databases grouped beneath an Archive label in Gmail.

Calendar, contacts, and groups are now migrated before email. Feeders still populate prior to migration, but mail is only migrated to G Suite after the calendar, contacts, and groups data have been processed.

Required-rooms-and-resources references are added to the body of the Google calendar event when that information is in the Notes event.

Active-users-by-site view.

Simplified design of user-profile form.

Batch mail-migration method fully deprecated.

Removed cutoff-date option from contacts/groups migration.

Updated location list to match web locations in Google Calendar.

Calendar and contacts migration-status views are no longer added to Archive databases (these views are redundant).

Invalid participants list was not showing

Issue: The invalid participants list was not showing where the body of the calendar entry was empty.

Resolution: The invalid participants list is displayed as expected.

Special characters were not supported in passwords

Issue: The provisioning system did not support some non-alphanumeric characters in passwords during account creation.

Resolution: Non-alphanumeric characters are supported in passwords as expected.

GAMLN agents would not run if server names did not match exactly

Issue: When server names did not match in the Domino Directory and Domino console due to differences in letter case, agents would not run.

Resolution: Case-sensitivity checks have been removed to allow agents to run when server names match letter for letter but do not match in terms of case.

Links to the attachment repository were not working

Issue: Attachment links in calendar events were not working.

Resolution: Attachment links in calendar events work as expected.

Personal Contacts Names appeared in G Suite in the same format as in Lotus Notes

Issue: Personal Contacts Names would appear in G Suite in the same format as in Lotus Notes, which could be common, abbreviated, or hierarchical.

Resolution: The personal-contact FullName field is checked during migration, and the name is displayed in G Suite in common form.

Folder references were not applied to archive databases

Issue: Folder references were not applied to archive databases when the status of those databases changed from Complete to Active following an earlier migration.

Resolution: Folder references are applied as expected.

Following are the issues fixed in this release.

Migration servers rejected messages with accented characters in Notes names

Issue: Migration servers were rejecting messages that had accented characters in the Notes names.

Resolution: Accented characters are now replaced with the nearest allowable characters from the ASCII code set. In addition, if GAMLN cannot convert a Notes name to an Internet address for the purposes of migration (for example, when a person has left the company and the related Person document has been removed from the Domino directory), then GAMLN replaces spaces in the original Notes name with underscores before adding that value to the To, From, CC, and BCC fields. In this case, a Notes name like Tiboldi Mária/RINGIER-H is converted to Tiboldi_Maria/RINGIER-H.

Some migrated messages were not displayed properly in Gmail

Issue: Extra carriage returns in multipart mail messages caused Gmail to display some messages incorrectly, and prevented attachments from opening after migration.

Resolution: Extra carriage returns have been eliminated. Messages are displayed as expected, and attachments are opened as expected.

Hide-when formulas for form actions were improved

Migration-status views were optimized

The site form (Site Profile > Advanced tab) now includes the option to Check and remove mail quotas before migration. Where mail quotas are used and a user's quota is nearly reached or has been exceeded, the system may not able to write the migration-status values back to migrated content. This can cause the system to repeat the migration multiple times for affected users and duplicate content will appear in the G Suite account. Enabling this option lets the system remove quotas as part of its preprocessing checks.

For users who no longer use the Notes client for Notes mail, the system now provides a web form that lets them migrate personal contacts and groups. In this scenario, they migrate personal contacts and groups from the Notes mail file directly, and there is no need to enter the G Suite password into GAMLN.

Auto-zipped attachments were rejected as bad attachments

Issue: The Domino plug-in ZipMail automatically creates a zip file of attachments as they are added to a Notes message sent from a Notes client. These zipped attachments were being rejected by G Suite as bad attachments.

Resolution: Auto-zipped attachments are now migrated as expected.

The time stamps for some messages were one off by one hour

Issue: On rare occasion, in some time zones, the time stamps for messages were off by one hour. The issue was related to the offset of Daylight Savings Time. Depending on the time zone in which the message originated and on which side of the International Date Line on the message originated, the time stamp could be one hour ahead or one hour behind the correct local time and date.

Resolution: Messages now have the correct time stamps.

Error generated for migrations over 32,768 messages

Issue: The system keeps track of the number of messages migrated for each user. Previously, there was a system limit of 32,768 messages. The system would continue to successfully migrate beyond the 32,768 limit, but if that limit were exceeded, an error was generated.

Resolution: The system limit has been increased to allow for large migrations without generating spurious errors.

Calendars are now migrated using administrator credentials, obviating the need to capture user passwords.

Users can migrate contacts themselves when you send them a Contacts Migration form.

The exclusion folder has been replaced by the option to explicitly include or exclude folders in your migration

Administrators can now reset migrations with a single click from the Administration database, rather than having to open individual mail files and perform resets there.

Logging has been improved: each Feeder database now manages its own detailed event log, rather than having a single log per site.

If you are configuring the system to provision accounts in G Suite, then your users need to update their profiles by setting their Google passwords.

We recommend a maximum of 9 feeder databases so that at least one agent thread remains available.

Some password characters were not correctly encoded in URLs

Issue: When passwords were encoded in URLs, some characters were not correctly encoded, which led to log in errors and CAPTCHA challenges.

Resolution: Characters are correctly encoded in URLs, and passwords are transmitted as expected.

When Out of Office was enabled, the agent sent emails in response to status updates

Issue: When Out of Office was enabled, the Out-of-Office agent was sending emails in response to GAMLN status updates.

Resolution: The system now checks the status of the agent before processing each mail file. If the agent is enabled, the system moves to the next user. The user whose Out-of-Office agent was enabled is processed later when the agent has been disabled.

12-hour AM/PM times/dates for migrated mail were displayed in Gmail as GMT/UTC times/dates.

Issue: Migrated mail that used the 12-hour AM/PM time-and-date format appeared in Gmail with GMT/UTC times and dates.

Resolution: The system now uses a 24-hour time/date format, and migrated messages are displayed with the correct local times and dates.

File locks occurred when Feeder databases simultaneously processed exceptions

Issue: If two or more Feeder databases were simultaneously processing exceptions, file locks would occur.

Resolution: File locks no longer occur when Feeder databases are simultaneously processing exceptions.

Following are limitations and issues in this release. Each issue includes a brief description, and workaround (if applicable).

The time stamps for some messages are one off by hour

Issue: On rare occasion, in some time zones, the time stamps for messages are off by one hour. The issue is related to the offset of Daylight Savings Time. Depending on the time zone in which the message originated and on which side of the International Date Line on the message originated, the time stamp can be one hour ahead or one hour behind the correct local time and date.

Status: This issue will be addressed in a future release.

A new mail header has been applied for use by third party applications. This mail header, X-Notes-Message-ID, contains the original Notes Message ID taken from the $MessageID field on the memo/reply.

A new log view has been added that shows all migration activity categorised by user (Administration database > Logs > By User).

Following are the issues fixed in this release.

Some birthdays and anniversaries did not migrate with the correct dates

Issue: Birthdays and anniversaries shown in Notes that had a time component but not a date component migrated with the date of 31 December, 1899.

Resolution: Birthdays and anniversaries now migrate with the correct dates.

Zip codes and telephone numbers did not migrate

Issue: Zip codes and telephone numbers not migrating. Notes defines these field types as text on the Person form, but in a small number of cases contact documents were storing these values as Number fields.

Resolution: Zip codes and telephone numbers are migrated as expected.

Notes Prefix and Suffix fields where -None- was selected in Notes were migrated

Issue: Prefix and Suffix fields that had a value of -None- should not have been migrated.

Resolution: If you select -None- as the value for a Prefix or Suffix field, that field will not be migrated.

If a mail file was migrated more than once, duplicate system-generated contacts were created

Issue: GAMLN generates a contact when it finds an email address in a personal group but no corresponding contact document exists in Notes. when a mail file was migrated more than once, contacts created previously by the system were not recognized, and the new migration would create a new contact document, causing duplicate entries in both Notes and G Suite.

Resolution: System-generated contacts are no longer duplicated.

Following are limitations and issues in this release. Each issue includes a brief description, and workaround (if applicable).

The following Notes rich-text elements are not supported:

• Buttons
• Action Hotspots
• Collapsible/Expandable sections. Section title and content are migrated as expanded.

Advanced table styles, such as tabbed or animated tables, are converted to simple two-dimensional tables in Gmail.

Only default table properties are supported. For example, formatting properties like border color and width, and cell padding and spacing are reset to default values.

Messages that include the following attachment types are not migrated: BAT, CHM, CMD, COM, DLL, EXE, PIF, VB.

Messages that have unread marks in Notes appear as read after migration.

If you empty the date field in a Notes document and make no other changes to the document, and then click Exit or press the Escape key, the "Do you want to save your changes?" message is not displayed as expected. This is a known Notes client bug. Be sure to always click Save or Save and Exit if you want to save these this type of change to a document.