How to migrate exchange users from one domain to another domain

I need to migrate number of mailboxes (20 to 25 only) from one of our sister companies (test.com) belongs to exchange 2010 into our internal domain (internaldomain.com) in exchange 2010. We are not intended to establish trust between two domains (test.com) and (internaldomain.com). Just intend to migrate their mailboxes from test.com to internaldomain.com but once the migration will be performed then users from test.com will be using their email address/mailboxes sitting in my exchange servers (internaldomain.com)
1.      Need to migrate 25 users from test.com to internaldomain.com
2.      Users from test.com will use my exchange servers (internaldomain.com) but their email address and mailboxes will be test.com
Need guideline what could be the migration steps I will have to consider. (MX record pointer change, mailbox export etc). Would you kindly assist to know the steps or any appropriate link that might help me!!
ipsec600Asked:
Who is Participating?
I wear a lot of hats...

"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.

imkotteesSenior Messaging EngineerCommented:
Hi,

1. Create a mailbox for them
2. Export their pst and copy to your domain
3. Import it with new mailboxes

For same email address, you can put them all in a single OU and create a Email address policy as you want.

Changing MX record is needed when you are completely (all the users) moving all of them to new domain. if you are doing partial you should not do that.
0
SandeshdubeySenior Server EngineerCommented:
Cross Forest Migration Guide – Exchange 2010 to Exchange 2010
http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/
0
ipsec600Author Commented:
Hi  Sandeshdubey, thank you for your post, actually i am not intended to do cross forest migration cause i will not be able to perform trust between domain.
Hi Sandeshdubey, thank you for your post, but I am not doing cross forest migration since i am not able to do the trust between domain.

Hi imkottees,

Thank you so much for your guideline, would you kindly assist to know the followings:
1. Create a mailbox for them
Ok, Should I create mailboxes for 25 users as u1@internaldomain.com to u25@internaldomain.com, cause objective is to migrate u1@test.com to u25@test.com in our internaldomain.com

2. Export their pst and copy to your domain
OK,

3. Import it with new mailboxes
How I will import .pst of u1@test.com to U1@internaldomain.com, cause users ,pst is from test.com, would you please clarify more.

4. For same email address, you can put them all in a single OU and create a Email address policy as you want.

OK. I will create single OU and create email address policy and apply that policy on that OU, and will create "Accepted domain" for test.com in our internaldomain.com exchange server.

5. Changing MX record is needed when you are completely (all the users) moving all of them to new domain. if you are doing partial you should not do that.
Yes, we will completely move all the users to new domain, once the above steps will be completed(1,2,3,4) then we will change MX record and point test.com MX to internaldomain.com exchange servers, but during transition period email will be lost or it will be in queue, and what would be the best time to shutdown the test.com email server?
0
Determine the Perfect Price for Your IT Services

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!

imkotteesSenior Messaging EngineerCommented:
1. you need to create an accepted domain for test.com and then need to create a email address policy for this domain. Finally create a mailboxes by keeping users in this domain.
http://forum.gotzu.com/showthread.php?tid=81

3. there wont be any problem with domain.
http://exchangeserverpro.com/exchange-2010-import-pst-files-mailboxes/

4. Yes, you can't create an email address policy w/o accepted domain.

5. i would suggest this.
 
5.1.  Create all new mailboxes here in internaldomain.com with same address @internaldomain.com

5.2. Set a forwarder from internaldomain.com to test.com user mailboxes

5.3. Create an email address policy for test.com in internaldomain (should not be primary at the moment)

5.4. change the MX record to internaldomain.com (they will be able to receive emails as it is added into secondary email address list)

5.5. make test.com email address policy is the primary for test.com OU

5.6. Disable the forwarding from internaltest.com domain

5.7. Ask users to use new mailbox (this can be given to them earlier, its up to you)

P.S: Make sure you are exporting and importing the LegacyDN value into new mailboxes. Else you will receiving NDR when replying to old emails.

I hope this would help.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Pankaj_401Commented:
Use the Active Directory Migration Tool (ADMT) included on your Windows Server 2003 CD-ROM to move Active Directory objects such as user, computer, group, and OU. MoveTree should only be used in special cases to handle objects (such as contacts) which cannot currently be migrated by ADMT.
Refer the article: http://social.technet.microsoft.com/Forums/windowsserver/en-US/30aed951-6afe-4bee-932c-113cd16038d5/migrate-user-profile-from-one-domain-to-another-domain-interforest-migration
0
ipsec600Author Commented:
Hi Pankaj_401, thank you for your reference link.
Hi imkottees, thank you for your excellent clarification to attend the issue, and surely its been outstanding help for me to get a clear picture of the scenario. Lastly once again requesting on the   LegacyDN value, is it mandatory part of this migration, and if so, would you kindly provide me any useful link to perform that..
0
imkotteesSenior Messaging EngineerCommented:
Hi, You are welcome.

LegacyDN value is important if your users are choosing these users (25 of them) from the local outlook cache. Because outlook use LegacyDN value to send email.

http://www.msexchange.org/articles-tutorials/exchange-server-2003/planning-architecture/Understanding-LegacyExchangeDN.html

Export:
Get-Mailbox -ResultSize Unlimited | Ft Name, LegacyDN |Export-CSV c:\LegacyDN.csv

Import:
http://blog.msexchange.me/2013/06/import-legacy-exchange-dn-from-csv.html
0
ipsec600Author Commented:
Hi imkottees, thank you once again you are just awesome!!!!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.