I have used MA in anger to move large numbers previously, and as Rob correctly points out, you need to test it on a couple of samples of 10-20 first after first making sure it works fine, there are so many variables at play one move will not be the same as anouther.
I did the bulk of my moves using EV8sp5, EV9+ is a little better at managing the proccessess available during the different move archive phases - however it is still good to get to know how you can increase the threads of Move Archive using the config file and test on your system to make sure you're not over loading things (i.e. how many threads dedicated to the copy etc).
When doing my moves I got figures simliar to the following: c.1.5gb/hr in the same datacenter, Centera storage, c.1gb/hr between datacenters off a poor source server (but archiving had been stopped and minimal access to data during the moves - still maxed out the source server on a few occasions). On average the number of archives moved perday where 15-22(in same DC), 10-15(remote DC). Al done in a window avoiding the backup window of 1am-6am.
One key thing that will trip up any large scale moves with MA (apart from the fact that it wasnt designed to do it and you'll struggle to find anyone with much experiance of using it for such as its for ad-hoc moves of arround 10 or so at a time) is the proccessess and the phases, if you're moving from 1 EV to 1 EV you will really have to ensure that you're copy phase threads arent being used up by verification phase, really test that as in EV8sp5 you had two proccesses that could run at anyone time from one source server, wether that be phase1, 2,3 or 4 etc. If moving from multiple sources to multiple targets you get much better performance as long as you spread your archives to a couple per server.
Key thing is to test it thouroughly before commiting to any management team or project that you can do x-per day - make sure you can hit that first.
