Exchange 2013 migration: final steps!

Good morning, all!  Environment is two sites, one legacy Exchagne 2010 standalone server at each site (one about to be decomissions, other close to it), and an Exchange 2013 DAG spanning both sites, one Ex2013 server per site with its own client database (sites replicating to each other).  Just about all of our migration from 2010 to 2013 has been completed, and I'm almost at the final steps. The public folder migration is the last step, but the below question arose.

All user mailboxes have been migrated successfully (for the most part), and in looking at the list of remaining mailboxes I see these:
x Discovery Search Mailbox (Discovery Mailbox)
x Microsoft Exchange (System Mailbox)
x Microsoft Exchange Approval Assistant (System Mailbox)
x Microsoft Exchange Approval Assistant (FederatedEmail)

Do these mailboxes need to be migrated to Exchange 2013?  I haven't seen these documented anywhere in the migration process except for one blog, and I'm hesitant to migrate them based on just the one resource.  I'm assuming these system mailboxes already exist on our 2013 system, and I don't want to compromise an already well-running Ex2013 DAG by moving over some kind of legacy mailbox that will just sit there.  On a side note, I'm not sure what the "Federated Email" entry is there for; we don't have a Federation set up in our 2012 forest (2008 functional level).

Comments welcome!  Thanks!
Steve BottomsSr Network AdminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Simon Butler (Sembee)ConsultantCommented:
System Mailboxes can be ignored.
For the others, use this command:

Get-Mailbox -Database "Exchange 2010 Mailbox Database" -Arbitration |new-moverequest -targetdatabase "Exchange 2013 Mailbox Database"

Change the names of the databases to match yours.


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
Steve BottomsSr Network AdminAuthor Commented:
Awesome, thanks once again, Simon!!  =)
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

From novice to tech pro — start learning today.