Other Pre-Requisites for Migrating Emails
- The destination account should be having a valid license.
- The destination domain should be having Mail.ReadWrite(Graph) , Mail.ReadWrite, full_access_as_app(Exchange) , permissions granted
on the Azure project.
- Exchange server should be on premise.
Features (Supported & Not Supported)
`
| Feature Point (Supported) |
Description |
| Demo Version License |
Only two users |
| Date Filter |
From - To supported (on Creation date time) |
| Folder Structure |
The application maintains folder hierarchy as it is. |
| Unicode character Names For Folders |
Yes, if in accordance with Outlook rules |
| Folder Name Existing conflicts |
Folders remain unaffected and gets used
|
| Archive Folder |
Supported(Archive system Folder only) |
| Categories, Mail Attachments |
Supported |
| Read/Unread Status |
Maintained |
| Mail Timestamp Retention |
Mail Sent/Received times maintained. Drafts get migration timestamp |
| Time-zone difference |
Adjusted for (The timestamps will get set in accordance with the destination time zone)
|
| Flags/tags |
Supported above exchange 2013 and later |
| Priority, Status, Conversation thread, Junk email |
Supported |
| Body format |
Supported |
| Exchange 2007,2010,2013,2016,2019 |
Supported |
`
| Feature Point (Not Supported) |
Description |
| Deleted item |
Not Supported
|
| Signature setting |
Not Supported |
| Share mailbox and group mailbox |
Not Supported |
| Folder policies, POST Item (RSS Feed) |
Not Supported |
| Search Folder (system folder) |
Not Supported |
| Archive Mailbox, Mail Folder contain Calendar Item
|
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. |
| Exchange 2003 |
Not supported |
| Meeting request ,meeting response not getting Destination
ItemID |
API issue |
API Issues
The application is using Microsoft Exchange Web Service API for reading.
for writing, it 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
Other Pre-Requisites for Migrating Contacts
- Target Office 365 need to be get registered with Azure application AD
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 |
| Foreign language |
Supported |
| Email address 1,2,3 |
Supported |
| Body, Contact photo |
Supported |
| Phone No, Birthday |
Supported |
| Relationship |
Supported
|
| Body Format |
Plain Text Supported |
| Nick Name, First Name, Last Name, Manager, Middle Name, File As |
Supported |
| Company, IM Address, foreign language Email address |
Supported |
| Duplicate Contact, Delta Migration |
Supported |
| Job Title, Department, Assistant, Manager |
Supported |
| Phone: Other category |
Supported (Added in body) |
| Delta Migration, Address |
Supported |
| Fax |
Supported (Added in body) |
`
| Feature Point (Not Supported) |
Description |
| Contact Attachment |
Not Supported
|
| Custom filed |
Not Supported |
| Anniversary |
Not Supported |
| Folder hierarchy |
Not Supported |
| Shared Contact |
Not Supported |
| Other : Hobbies,School,Personal web page , Anniversary,Account ,customer id and government
id, biling information, computer network name,mailing Address,location,internal-busy address |
Not Supported |
| System folder mapping |
Not Supported (new Contact folder is
created and item is migrated into that
folder )
|
| Invalid Email Address |
Not Supported |
Known Issues
`
| Issue |
Reason |
| List and Groups not supported |
no API endpoint
|
| deleted items |
no API endpoint
|
| Follow up Contacts |
no API endpoint
|
| Date filters are not working on same instance second time |
Know issue
|
API Details:
For reading the application is using the Microsoft Exchange Web Service API.
For writing the application is using the Microsoft Graph API which a REST based API .
EWS: https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/start-using-web-services-in-exchangeGraph API: https://docs.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0
Other Pre-Requisites for Migrating Calendars
- Target Office 365 need to be get registered with Azure application AD
Features (Supported & Not Supported)
`
| Feature Point (Supported) |
Description |
| Exchange 2013,2016 |
Only two users |
| Folder Structure |
Supported |
| Date Filter |
On calendars Start Date (Process Time in UTC format) |
| Delta Migration |
Supported |
| Special Characters / Foreign Language Names |
Supported |
| Recurrence, Reminder |
Supported
|
| Future Event |
The date range will be +1 year from current date
|
| Attendees |
Supported
(Include other domain) |
| Event Status, Time Zone, Show As |
Supported |
| Location, Body, Private, Categories, Importance |
Supported |
| Attendees mapping, Body format, All Day Event |
Supported |
| Different Time Zone for Start End, Occurrence |
Supported |
| File Attachment |
Supported |
| Daily Recurrence with every Workday |
Treat as Weekly recurrence |
| Default Event Filter |
we read event from 1990 to +1 from Current date |
| Same name calendar folder |
Mapped to Office 365 System Calendar folder |
| Event having Start and End Time zone different
then source account time zone
|
The Start and End time zone will get converted into time zone of which was provided to
start and end time zone and it will get migrate accordingly. |
`
| Feature Point (Not Supported) |
Description |
| Notification |
Not Supported
|
| Mail Notification |
Not Supported |
| Shared |
Not Supported |
| Organizer |
Not Supported. Organizer name is not showing in new view of Office 365 on portal. It is
showing organizer name as Required attendee |
| Multiple Organizer |
Not Supported |
| Embedded Attachment, Folder Color |
Not Supported |
| Event Follow up, Attendees Status |
Not Supported |
| RTF body format |
Not Supported |
Shortcomings and Limitations
`
| Limitation |
Reason |
| Event Up to 4 MB supported |
API issue
|
| Exchange 2003 not supported
|
API issue
|
| Date filters are not working on same instance second time
|
Know issue
|
API Details:
For reading the application is using the Microsoft Exchange Web Service API.
For writing the application is using the Microsoft Graph API which a REST based API .
EWS: https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/start-using-web-services-in-exchangeGraph API: https://docs.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0