Using MAPI (or EWS) on the source and EWS on the target are what ALL of the third-party solutions do, including: MigrationWiz, BinaryTree, Dell/Quest, etc.
Doing the actual "message-by-message" transfer is not the difficult part. The difficult part is dealing with throttling and the various different types of potential items (message, calendar, contact, task, etc.). All of the various types require special handling and consideration. From: [email protected] [mailto:[email protected]] On Behalf Of Joseph L. Casale Sent: Saturday, May 9, 2015 8:04 PM To: '[email protected]' Subject: [Exchange] RE: Development Exchange Web Services (EWS)? Seems pretty straightforward with c#, https://msdn.microsoft.com/en-us/library/office/dn672316%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396 I'd be shocked though if something didn't already exist to save you from re-inventing the wheel. jlc From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Finnesey Sent: Saturday, May 9, 2015 1:28 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Development Exchange Web Services (EWS)? Has anyone within the group done any development work with Exchange Web Services (EWS)? How default would it be to access a server via EWS and have the mail items "copied" and then imported into Office 365? Cheers Ryan
