Other Pre-Requisites for Migrating Emails
- Provide the UPN
- The destination account should be having a valid license.
- Domain-wide scopes must be provided for destination domains.
- The destination domain should be having Mail.ReadWrite(GoogleApi), permissions granted on gcp project.
- The source domain should be having Mail.Read(Graph) , Mail.Read, full_access_as_app(Exchange) permissions granted on the Azure project
Features (Supported & Not Supported)
`
| Feature Point (Supported) |
Description |
| Demo Version License |
Only two users |
| Date Filter |
From - To supported (on Created Date) |
| Folder Structure |
Original Structure Maintained |
| Special Characters / Foreign Language Names For Folders |
Yes, if in accordance with google rules |
| Folder Name Existing conflicts |
Folders remain unaffected and gets used |
| Inbox , Sent Items, Drafts |
Supported |
| Archive Folder, Deleted Items |
Supported |
| Subject, To, Multiple To, Cc, Multiple Cc, Bcc , Multiple Bcc |
Supported. |
| Categories |
Need to check email header. |
| Read/Unread Status |
Maintained |
| Mail Attachments |
Supported (if it is on one drive then it is not supported) |
| Flags |
Supported(mark as Important) |
| Conversation Threads |
Supported |
| Mail Timestamp Retention |
Mail Sent/Received times maintained. Drafts get migration timestamp. |
| Time-zone difference |
Same as source |
| Maximum Mail Size |
If it crosses default size then the mail will be stored on g-drive as .eml |
| Delta |
Supported |
`
| Feature Point (Not Supported) |
Description |
| Sharing Permissions |
Not Supported |
| Policies |
Not Supported |
| Signatures |
Not Supported |
| Group folders/shared folders |
Not Supported |
| Cross language |
Not Supported |
Shortcomings and Limitations
`
| Limitation |
Reason |
| All folders present even if they are outside
the date filter’s range |
The application is designed to pre process the folders first and then the files |
| Folder length |
G-suite supports max 225 character length for folder path to overcome this limitation we are
trimming each folder name to 20 characters.
After exceeding the folder limit of 225, folder will be created at Root level |
Known Issues
`
| Issue |
Reason |
| Requests Timed Out in Logs |
Slow Internet connection |
| Exchange Server Temporarily Unavailable |
Exchange Service outage |
Other Pre-Requisites for Migrating Contacts
- Provide the UPN
- The source account should be having a valid license
- End user of destination should have access of Google mail.
- Domain-wide scopes must be provided for destination domains.
- The source domain should be having Contact.Read(Graph) permissions granted on the Azure project
- The destination domain should be having Contact.ReadWrite(Google api) permissions granted
Features (Supported & Not Supported)
`
| Feature Point (Supported) |
Description |
| Demo Version License |
Only two users |
| Date Filter |
From - To supported (on Created Date) |
| Folder Structure |
Original Structure Maintained |
| Special Characters / Foreign Language Names For Folders |
Yes, if in accordance with g-suite rules |
| Folder Name Existing conflicts |
not applicable |
| Multiple email addresses |
Supported |
| Phone :Business,home and mob(1) |
Supported |
| IM address |
Supported(Maintaining as Custom field)
|
| Company ,first name,last name |
Supported |
| Work (Job title,department,company name,office location,manager,assistant name) |
Supported |
| Note, Profile Photo |
Supported |
| Personal Info - First Name,Last Name,Suffix,Prefix |
Supported |
| Addresses : Business,Home ,Other |
Supported |
| Other : Nick name,birthday,significant other,web page |
Supported |
| Delta Migration |
Supported |
`
| Feature Point (Not Supported) |
Description |
| Phone: Other category(like fax,pager..) |
Not Supported
|
| Other : Hobbies,School,Personal web page , Anniversary |
Not Supported |
| Contact groups |
Not Supported |
| Follow up Contacts |
Not Supported |
| Contact List |
Not Supported |
Shortcomings and Limitations
`
| Limitation |
Reason |
| All folders present even if they are outside the date filter’s range |
The application is designed to pre process the folders first and then the
contacts.
|
Known Issues
`
| Issue |
Reason |
| List and Groups not supported |
no API endpoint
|
| Requests Timed Out in Logs |
Slow Internet connection |
| IM Address |
Maintaining custom field for this |
| Significant other |
Maintaining as Spouse Name |
| Few Folders such as Group Folder,person metadata..etc are getting skipped |
Not receiving from API in folder list |
Objective :
Admin user should be able to migrate end users Office 365 calendars to G Suite Calendars.
Other Pre-Requisites for Migrating Calendars
- Provide the UPN
- Domain-wide scopes must be provided for source and destination domains
- The source domain should be having Calendar.Read(Graph) permissions granted on the Azure project
Features (Supported & Not Supported)
`
| Feature Point (Supported) |
Description |
| Demo Version License |
Only two users |
| Folder Structure |
Supported |
| Date Filter |
Supported
[on the Start date] |
| Delta Migration |
Supported |
| Special Characters / Foreign Language Names |
Supported |
| Recurrence, Folder Color |
Supported |
| Attendees out side domain |
Supported
[For valid email address and domain hosted on google]
|
| Attendees Mapping |
Supported |
| Time-Zone Mapping |
Supported |
| All Day Event |
Supported |
| Reminders, Location, Attendees Status |
Supported |
| Addresses : Business,Home ,Other |
Supported |
| Visibility |
Supported |
| Calendar Status |
Supporting only Free and Busy |
| System Folder Mapping |
Supported |
| Cross-Language Account |
Translation Not Supported |
`
| Feature Point (Not Supported) |
Description |
| Drive Attachment |
Not Supported
|
| Shared Calendar |
Not Supported
|
| Notification |
Not Supported |
| Html Body |
Not Supported |
| Categories |
Not Supported |
| Read Only Calendars, Shared Calendars |
Not Supported |
| Group Supported |
Not Supported |
Known Issues:
`
| Limitation |
Reason |
| Attendees Outside Domain
[Other than G Suite Domain] |
Not supported. Also depends on which platform domain is hosted
|
| Max 35 Calendars/ day |
API Limitation
|
| System folders (My Calendar, Other Calendar and People’s Calendar) |
Created on destination
|
API Details:
We use Google Calendar API V3 for the reading and writing calendars.
https://developers.google.com/calendar/
API Quota:
Queries Per Day : 1,000,000
Queries Per 100 Seconds Per User: 500
Story Conclusion
- Time Zones that are not on G Suite are defaulted to the account's time zone.
- Daylight savings are observed. Refer to https://en.wikipedia.org/wiki/Daylight_saving_time
- If a recurring event has different start and end time zones, G Suite will keep the start time zone only.
- Time zones map from windows time to IANA (Olson) time. Refer to https://en.wikipedia.org/wiki/List_of_tz_database_time_zones for IANA
- Monthly recurrence on particular day of week after export showing as Unsupported Recurrence. Its setting type as Unsupported but if we
check the series of recurrences at destination it is showing recurrences on that day.
- Events having Start time zone as Fiji and End time zone as Kamchatka showed different behaviour on Linux and Windows. The daylight
saving time was differently calculated on both platforms but the event duration stayed the same
| Time Scenario |
Conclusion |
| Default Time zone |
Maps to Default |
| Same Time zone for Start and End |
Maps to Start and End |
| Different Time zone for Start and End (Both
supported) |
Maps to Start and End |
| Different Time zone, Start Not Supported |
Start Maps to Calendar Default, End maps to whatever is set, but times comes according to default time zone. |
| Different Time zone, End not Supported |
End is ignored, Start is mapped and start and end time comes according to Start Time zone.
|
| Different Time zone, Both not supported |
Time zones are account default, and start and end time is according to default time zone.
|
| Time zone Regions |
Maps according to IANA database. https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
|
| Daylight Saving |
Time zone shows the daylight adjustment, time remains unchanged.
|
Other Pre-Requisites for Migrating Documents
- Domain-wide scopes must be provided.
- Email address of Office 365 must be UPN
- End user of Gsuite should have access to Google Drive.
- End user of Office365 user should have access of One Drive and must be licensed.
- Source domain should be having Files.Read permissions granted on the Azure project
Features (Supported & Not Supported)
`
| Feature Point (Supported) |
Description |
| Demo Version License |
Only two users |
| Max size supported |
Microsoft Graph api supports max 15GB of file.
Google Drive API supports max 5TB of file size
|
| Folder Structure |
Application maintains folder hierarchy |
| Folder Sharing |
Sharing permissions migrated as per user mappings supplied
|
| File Sharing |
Sharing permissions migrated as per user mappings supplied |
| Permission Inheritance |
Supported |
| SharePoint Permission |
Supported. Translated accordingly. |
| Date Filter |
Supported for files and not for folders
|
| Unique Names for Files/Folders |
One drive supports unique file name but google drive don't support it. If same file name already exists then
application will create new file with same. |
| Unique Names for Folder |
Behavior will be same as Files |
| Special Characters / Foreign
Language Names
|
Supported |
| Date Time retention |
Supported |
| Creation of a Root Folder |
Customizable. If chosen, a top level folder gets created with its name as the source e-mail address |
| Delta Migration |
Existing files/folders are preserved untouched, new additions in source are migrated. Delta migration will
work only on Created date.
|
`
| Feature Point (Not Supported) |
Description |
| Trash Folder Migration |
Not Supported
|
| Shared With Me Folder Migration |
Not Supported |
| One Note, Sharing link, File Version, Discovered |
Not Supported |
| Recent |
Not Supported |
| Outside domain address
handling |
Not Supported |
| Create sub-folder in Shared With
Me Folder |
Not Supported |
| Partial file migration |
Not Supported |
| Different Owner folder & files |
Not supported (Note: If different owner folders containing file created by migrated users file those files will
get migrated into Root folder of Drive)
|
Limitations
`
| Limitation |
Reason |
| Sharing links not migrated |
API Limitation
|
| Version History not migrated |
Additional overheads
|
| Multiple owners |
API limitation. Secondary owners get relegated with write permissions
|
| All folders present even if they are outside the date filter’s range |
The application is designed to preprocess the folders first and then the files
|