I am currently working a contract where I will be pretty much the point person in migrating another company's Exchange 2010 databases in to the client's Exchange 2010 all while converting shared calendar's in to public folders. Now I've been an admin for Exchange 2010 but a bit interested in what would be best practices for performing something like this, as well as trying to avoid any potential issues.

I will be having a call with the senior Exchange engineer who is assisting with this merger who will pretty much assisting me during this time.

My potential for being hired is riding on this project and would like as much assistance as possible. I'm feel confortable with most core concepts of the Exchange server but never merged another companies info in a completely different environment before.

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Okay, my boss has me in the beginning stages of the move. Currently the AD accounts have been created on the target domain and he wants me to start moving the DLs over and applying the hidden attribute. Is there any way I can use the ADMT to do this or would I have to go through the painfull process of either creating them manually and/or exporting from the source server and then moving over to the target that way?

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Thank you for the comments thus far. However, some more information has just been given to me regarding this project. Apparently, the CIO previously rejected the idea of creating a Two Way Transitive Trust between the 2 domain. So this means the whole project just became more manually....URGGGGH! So what the target company is thinking about doing is creating the accounts on their end and then exporting mailboxes, rules and Public Folders to PSTs and then copying the data via an IPSec tunnel to the target domain and then copying the data manual. I myself, would rather Powershell the importing of the PSTs with a log output at the end to ensure there where no issues with the importing of the PST.

I've already wasted about 2 weeks by planning to use ADMT and .\PrepareMoveRequest.ps1 command. So any thoughts on how I can automate this as much as possible would be really helpful!

Sorry about bringing this information to light now but as a contractor I have to really dig deep on my own and harass the FTE for information, which I just received an hour ago on a conference call.

-I wasted 2 weeks planning to use ADMT and the .\PrepareMoveRequest.ps1 command but the CIO previously rejected the idea of creating a Two Way Transitive Trust between the 2 domain. So this means the whole project just became more manual....URGGGGH!

-They want to export mailboxes, rules and Public Folders to PSTs and then copy the data via an IPSec tunnel to the target domain

-Employees from the source domain will be keeping their original SMTPs with secondary SMTPs from the company they are merging with

I want to Powershell script this to be able to batch import this in to the corresponding users mailboxes with a log file, if possible.