Migration Kerio Connect to Exchange 2013 [message #125135] |
Wed, 21 October 2015 13:01  |
marqito
Messages: 1 Registered: October 2015
|
|
|
|
Hi Guys
we would like to move from a at the moment configured Kerio Connect 8.5.1 Server to a new Exchange 2013.
Is there a easier way for migration than exporting the mailboxes within outlook? It would be around 65 mailboxes, which would be a pitty to export.
Many thanks for your help.
Best regards,
Marc
|
|
|
Re: Migration Kerio Connect to Exchange 2013 [message #130153 is a reply to message #125135] |
Fri, 03 June 2016 12:10   |
HansAndrzen
Messages: 1 Registered: June 2016 Location: Praha
|
|
|
|
well, I'm also searching for any mailbox export tool form Kerio to PST. need to migrate 100+ kerio mailboxes to exchange. remotely. Best would be if end user doesn't notice the change at all. seamlesly. Does anyone have experience with such scenario?
|
|
|
Re: Migration Kerio Connect to Exchange 2013 [message #130166 is a reply to message #130153] |
Fri, 03 June 2016 19:48  |
Bud Durland
Messages: 586 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
There is no tool that I know of that will remotely export a user's mail sotre to a .pst file. That said, if the you are only interested in moving mail, IMAPSYNC comes highly recommended. If the users are using OutLook, you are going to have to touch the individual machines anyway in order to reconfigure them to connect to exchange and remove the OutLook connector. Off the top of my head, the path with the least user downtime would be:
1. set up exchange, enable IMAP access
2. Use IMapSync to do the initial copy of mail from KC to Exchange
3. Reconfigure MX records to point to Exchange
4. Touch workstations to:
4a - export calendards and contacts to PST
4b - remove kerio connector
4c - configure exchange connection
4d - import calendars and contacts from PST
5. When all users are done, one final ImapSync to pick up anything that was missed during step 4.
Hope this helps.
|
|
|