Hopefully someone can give me some advice. I am trying to run a mailbox move from Exchange 2007 to 2013 in a different forest. The issue I am having is when I try to run the command new-moverequest on the Exchange 2007 management shell it is failing with 'new-moverequest is not an available cmdlet, function, script file, or operable program'

I think it may be a permission issue but cant see where to apply the necessary permissions. I am logging in as a domain admin that looks like it has everything it requires.

Could someone please advise where to look for the correct permisions.

Thanks

There is a detailed walk-through here about mailbox moves in general from different versions of Exchange, with a particular emphasis on cross-forest moves. Once you download the presentation, turn to page 43 for your exact case.

Summarizing: you'll first have to create a mail-enabled user object, (optionally) run ADMT and only then use New-MoveRequest in the target organization. Only pull moves are supported in your case, and you cannot use a push move (eg initiating the move from the 2007 org).

As for the permissions, fastest way would be to add your account to "Organization Management". The long way: by default 2 role management groups are assigned permissions for New-MoveRequest, Organization Management and Recipient Management, as stated here (section Mailbox move and migration permissions). Aside from these, you can create a custom RBAC role assignment and assign it the Mailbox moves role.

Beside the above given suggestion, you can also checkout this another informative article that covers the same area in order to get rid from such weird issue and perform a swing migration job in flawless manner.

Understanding management roles

Here is another article from Technet team that provides step-wise instructions to accomplish this job by checking all the required prerequisites.

As an alternative, to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on this automated solution http://www.exchange2007to2013migration.exchangemigrationtool.com/ that seems to be a good approach in order to get this job done without interruption.

Hope it helps you!

There is a detailed walk-through here about mailbox moves in general from different versions of Exchange, with a particular emphasis on cross-forest moves. Once you download the presentation, turn to page 43 for your exact case.

Summarizing: you'll first have to create a mail-enabled user object, (optionally) run ADMT and only then use New-MoveRequest in the target organization. Only pull moves are supported in your case, and you cannot use a push move (eg initiating the move from the 2007 org).

As for the permissions, fastest way would be to add your account to "Organization Management". The long way: by default 2 role management groups are assigned permissions for New-MoveRequest, Organization Management and Recipient Management, as stated here (section Mailbox move and migration permissions). Aside from these, you can create a custom RBAC role assignment and assign it the Mailbox moves role.

• Proposed as answer by Edward van BiljonMicrosoft community contributor, Moderator 22 hours 5 minutes ago

Beside the above given suggestion, you can also checkout this another informative article that covers the same area in order to get rid from such weird issue and perform a swing migration job in flawless manner.

Understanding management roles

Here is another article from Technet team that provides step-wise instructions to accomplish this job by checking all the required prerequisites.

As an alternative, to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on this automated solution http://www.exchange2007to2013migration.exchangemigrationtool.com/ that seems to be a good approach in order to get this job done without interruption.

Hope it helps you!

• Proposed as answer by Edward van BiljonMicrosoft community contributor, Moderator 22 hours 5 minutes ago