Other Pre-Requisites for Migrating Emails
- The source domain should be having Mail.Read(Graph) , Mail.Read, full_access_as_app(Exchange) permissions granted on the Azure
project
- The destination domain should be having Mail.ReadWrite(Graph) , Mail.ReadWrite, 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 |
The application maintains folder hierarchy as it is. |
| Date Filter |
Supported for emails and not for folders
For drafts Creation time
( received\send date time) |
| Folder Name Existing conflicts |
Folders remain unaffected and gets used |
| Special Characters / Foreign Language Names for folders |
Yes, if in accordance with Outlook rules
|
| Folder Name Length |
255 Characters as supported by Office |
| Inbox , Sent Items, Drafts |
Supported |
| Archive Folder, Deleted Items |
Supported |
| Subject, To, Multiple To, Cc, Multiple Cc, Bcc ,
Multiple Bcc |
Supported |
| Categories |
System Categories Map by default. User Categories map only if they already exist at
the destination. |
| Mail Attachments, Signatures, Flags, Conversation Threads |
Supported |
| Time-zone difference |
Adjusted for (The timestamps will get set in accordance with the destination time zone) |
| Mail Timestamp Retention |
Mail Sent/Received times maintained. Drafts get migration timestamp. |
| Maximum Mail Size |
150 Mb (Sent, Received) |
| Flags (Important, Priority etc.) |
Preserved
|
| Feature Point (Not Supported) |
Description |
| Shared/Group Folders |
Not Supported |
| Policies |
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 preprocess the folders first and then the files. |
| User Categories aren’t automatically migrated. |
The feature is yet to be implemented |
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
- The source domain should be having Contacts.Read(Graph) permissions granted on the Azure project
- The destination domain should be having Contacts.ReadWrite(Graph) 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 Outlook rules |
| Folder Name Existing conflicts |
Folders remain unaffected (need to check)
|
| Multiple email addresses |
Supported |
| Phone :Business,home and mob(1) |
Supported |
| IM address |
Supported
|
| Yomi 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 |
Not Supported
|
| Other : Hobbies,School,Personal web page , Anniversary,Location |
Not Supported |
| Follow up Contacts |
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 preprocess the folders first and then the
contacts.
|
Known Issues
| Issue |
Reason |
| List and Groups not supported |
no API endpoint
|
| Deleted items, Directory, Follow up Contacts |
no API endpoint
|
| frequently contact list, Favorites |
no API endpoint
|
| Requests Timed Out in Logs |
Slow Internet connection
|
| Invalid email address contacts got
failed
|
bug no: ,441,APIInvokeFailed, BadRequest
ErrorInvalidMailbox, Message: EmailAddress or ItemId must be included in the request
|
| Some folder got skipped |
bug no: ,435,We are not aware how that folder data has been created and API is not giving those
folder list
|
Other Pre-Requisites for Migrating Calendars
- The source domain should be having Calendar.Read(Graph) permissions granted on the Azure project
- The destination domain should be having Calendars.ReadWrite.All, full_access_as_app(Exchange) Calendars.ReadWrite.All,
permissions granted on the Azure project for writing calendar attendees we are using Exchange API
Features (Supported & Not Supported)
| Feature Point (Supported) |
Description |
| Demo Version License |
Only two users |
| Local Attachment |
4mb request supported |
| Folder Structure |
Supported |
| Date Filter |
Supported [on the Start date] |
| Delta Migration |
Supported |
| Special Characters / Foreign Language Names |
Supported |
| Recurrence, Folder Color |
Supported [customized color need to check]
|
| Attendees out side domain |
Supported [need to implement]
|
| Resouces |
Supported |
| Future events |
up to +1 year supported |
| Categories |
supported(user-created categories should be present at destination) |
| Reminders, Location, Other Calendars |
Supported |
| Visibility, Time Zone Mapping, Private and Public |
Supported |
| System calendars |
supported and mapped to destination system calendar(need to check for non English system
folder) |
| Future Events |
The date range will be +1 year from the current date |
| Feature Point (Not Supported) |
Description |
| Drive Attachment |
Not Supported |
| Notifications |
Not Supported
|
| Attendees status |
Not Supported |
| Imported / Web Only Calendar Folder |
Not Supported |
| Charm |
Not Supported |
| Read Only Calendars, Shared and Group Calendars |
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 preprocess the folders first and then the file
|
| User Categories aren’t automatically migrated. |
The feature is yet to be implemented
|
Known Issues
| Issue |
Reason |
| Requests Timed Out in Logs |
Slow Internet connection
|
API Limitations
The application is using the Microsoft Graph API which a REST based API for interacting with Office 365,
also Microsoft Exchange Web Service API is used for Outlook 365 communication
Graph API : https://docs.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0
EWS : https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/start-using-web-services-in-exchange
API Request Volume Limit : 10000 requests every 10 minutes.
Other Pre-Requisites for Migrating Documents
- The source domain should be having Files.Read permissions granted on the Azure project
- The destination domain should be having Files.ReadWrite.All , Sites.ReadWrite.All, Site.FullControl permissions granted on the Azure project
- The destination account OneDrive should be provisioned i.e completed the initial setup necessary to activate the drive
Features (Supported & Not Supported)
| Feature Point (Supported) |
Description |
| Demo Version License |
Only two users |
| Date Filter |
From - To supported
|
| Folder Structure |
Original Structure Maintained |
| Folder Sharing |
Sharing permissions migrated as per user mappings supplied
|
| File Sharing |
Sharing permissions migrated as per user mappings supplied |
| User/ Group Permission Mapping Manifest |
Needed from user |
| Sharepoint Permissions |
Yes, Translated accordingly |
| Permission Inheritance |
Yes |
| File Timestamps |
Create and Last Modified time maintained
|
| Time-zone difference |
Adjusted for (The timestamps will get set in accordance with the destination time zone) |
| Special Characters / Foreign Language Names |
Yes, bound by OneDrive rules
|
| Creation of a Root Folder
|
Customizable. If chosen, a top level folder gets created with its name as the source e-mail
address |
| File/Folder Name Existing conflicts |
Folders remain unaffected and gets used. File data will be overwritten.
|
| 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.
|
| Delta Migration |
If file or folder migrated already will skipped. Only newly created files or folders will get
migrate. Delta migration will work only on Created date. |
| Empty files (0 Size) |
Supported
|
| Outside domain address handling |
Permissions sets as External Use
|
| Maximum Filesize |
15 Gigabytes
|
| Feature Point (Not Supported) |
Description |
| File/Folder Share through link |
Not Supported
|
| File Versions, Recycle bin |
Not Supported |
| Shared with me |
Not supported as a direct feature, but will be get populated as a result of file/folder sharing |
| Discover |
Not Supported |
| Recent, OneNote |
Not Supported |
| Editing inside Shared with me (Create child
folder inside shared folder)
|
Not Supported |
Shortcomings and Limitations
| Limitation |
Reason |
| Sharing links not migrated |
API Limitation
|
| Version History not migrated |
Additional overheads
|
| Max folder/file name length of 100
characters
|
Compensating for cross-platform migrations where source allows for a larger folder/file name
length. OneDrive allows 400 characters in the total path.
|
| Storage metrics shows twice the original
size
|
OneDrive maintains version history when the drive data gets uploaded and the modification date
changes.
|
| 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
|
Known Issues
| Known Issue |
Reason |
| Requests Timed Out in Logs
|
Slow Internet connection
|
| Email/Calendar Folder created
in full suite migration
|
They are dump folders for calendar events and invalid emails
|
| Site Not Found in Logs |
Unprovisioned user
|
| Folders and Files placed at
Root Folder |
If a File/Folders total path length is crossing 320 characters, we change its parent to ROOT. Further the
hierarchy maintains until again it reaches 320 characters and split.
|
| Mail Notification for item shared
outside domain |
It is a security feature of Microsoft to notify the file owner if a file gets shared outside the domain
|
Other Pre-Requisites for Migrating Tasks
- Project should be created on Azure Panel
- Source and Destination users should have valid license
- API Permission should be given on Azure Project
- Source API Permission
- Destination API Permission
- Tasks.Read and Tasks.ReadWrite as Exchange scopes need to be added
- Minimum Bandwidth must be 100mbps
Features
| Feature |
Description |
| Demo Limitation |
2 users |
| Attachments |
Supported [up to 25 MB]
It will get stored in task as inline attachments
|
| Body |
Supported |
| Important |
Supported |
| Status |
Supported
Application will not sync up after migration.
User need to change the task status manually (for Completed). |
| Subject |
Supported [255 characters]
|
| Due Date |
Supported |
| Reminder |
Supported |
| Recurrence [Repeat] |
Supported
[In Yearly pattern recurrence interval not supported] |
| Categories [Default, Custom] |
Supported |
| Steps [Sub tasks] |
Not Supported |
| Custom Task Lists |
Supported |
| Assigned to You Task [Tasks that are assigned by other users] |
Not supported |
| Themes |
Not supported |
| Date Filter |
Supported [on Created Date] |
| Delta |
Supported |
| Foreign language / Special characters |
Supported |
| Task list name length |
Supported 255 Characters |
| Future tasks |
Supported |
| Task created in Outlook |
Supported
[Need to configure the destination Office 365 account in Outlook to
view the properties]
[Priority, %Completed, In Progress, Not Started, Deferred, Waiting
on someone else, Completed, Owner, Reminder, Reminder Time,
Priority, Importance, Categories, Recurrence ] |
| Add to my day |
Not Supported |
| Group |
Not Supported |
API Limitations
| Features |
Limitations |
| Recurrence [for Yearly Pattern]
|
Cannot retrieve interval property in recurrence Yearly Pattern
[for e.g. For every 2 Years It displays only Yearly] |
| Group of Tasks List |
Cannot retrieve the group from API
|
API:
- microsoft.exchange.webservices.data.task => exchange-ews-api
Pre-Requisites for Migrating Other Categories
- Project should be created on azure portal.
- Source and Destination Users should have valid license
- API Permission should be given on Azure Project
- MailboxSettings.Read / MailboxSettings.ReadWrite Scopes need to be added.
- Minimum bandwidth must be 100mbps
Supported workloads for Categories:
- Emails
- Calendar events
- Tasks
Features
| Feature |
Description |
| Demo limit |
2 complete users |
| Default Categories [Red, Green, Blue, Orange, Purple, Yellow ] |
Supported
|
| Custom Categories |
Supported |
| Color retention |
Supported |
| Categories Name |
Supported
|
| Name length of Categories |
255 characters
|
| Max count of Categories |
Around 1000-1100 |
| Foreign language |
Supported |
| Special characters |
Supported, [according to Microsoft rules] |
| Categories to Emails |
Supported |
| Categories to Calendars |
Supported |
| Categories to Tasks |
Supported |
| Add to favorite |
Not supported |
| Deleted Categories |
Not Supported [Data syncing is not supported if Category deleted
from Source or Destination] |
| Multiple Categories for Single Item |
Auto update |
| Categories Conflict by name |
Will consider destination name |
| Categories Conflict by color |
Will consider destination color |
API:
Features
| Feature |
Description |
| User Creation |
Provided support to create Users at Office 365 destination domain. |
| License Consumption |
No licenses will consumed for Users creation |
Limitation
| Features |
Limitations |
| License Assignment |
Cannot provide licenses to the created user, due to API limitations |
Features
| Feature |
Description |
| Group Creation |
Provided support to create Groups at Office 365 destination domain. |
| Group Member migration |
Provided support to migrate Groups and Group Members for Office 365 to Office 365 |
| License Consumption |
No licenses will consumed for Group creation and Group migration. |
Limitation
Groups are not supported for Tasks