Cross forest migration from Exchange 2010 to Exchange 2013 RRS feed

  • Question

  • Hello,

    I have a forest where I have deployed Exchange 2010 SP2 on Windows 2008 R2 SP1 with the forest in 2003 native mode. I just created a new forest with Exchange 2013 on Windows 2012. I would like to migrate mailboxes from one organization to the other but I have no clear if I have to wait to Exchange 2010 SP3.

    I have tried to migrate a mailbox running first Prepare-MoveRequest script and then running the New-MoveRequest cmdlet that gives me the error "RemoteLegacy moves must involve Exchange 2010 or lower versions only". Am I right and I have to wait for the SP3 or am I doing any step wrong?

    Regards and thanks for the help,

    Monday, October 29, 2012 8:18 PM


  • Hi

    I haven't actually tried remote moves between Exchange 2010 and 2013 but I suspect that you are correct - 2010 SP3 will be required for this.

    Cheers, Steve

    Monday, October 29, 2012 9:11 PM

All replies

  • Hi

    I haven't actually tried remote moves between Exchange 2010 and 2013 but I suspect that you are correct - 2010 SP3 will be required for this.

    Cheers, Steve

    Monday, October 29, 2012 9:11 PM
  • You can't migrate from exchange 2010 SP2 to exchange 2013.
    You can only migrate from exchange 2010 to 2013, once you have exchange 2010 with SP3...


    Gulab Prasad,
    My Blog | Z-Hire Employee Provisioning App

    Tuesday, October 30, 2012 9:05 AM
  • Yes, you need to wait Exchange 2010 SP3, it will be released around first half of calendar year 2013 based on the announcement:


    Tuesday, October 30, 2012 10:22 AM
  • Hi,

    I have got the same issue.
    Source Domain: Windows 2008 R2
    Source Exchange: Microsoft Exchange 2010 with SP3 installed
    Target Domain: Windows 2012
    Target Domain: Microsoft Exchange 2013 with CU1 installed

    The prepare-moverequest runs without any issues but when I run the new-moverequest I get the following error

    RemoteLegacy moves must involve Exchange 2010 or lower versions only.
        + CategoryInfo          : InvalidArgument: (xxxx@xxxx.co.za:MailboxOrMailUserIdParameter) [New-MoveRequest], RecipientTaskException
        + FullyQualifiedErrorId : 6F8F05D6,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
        + PSComputerName        : xxxxxxx.xxxxxxx.co.za


    Thursday, May 16, 2013 11:10 AM
  • Hi

    You should run the new-moverequest command from the Exchange 2013 side.

    Cheers, Steve

    Thursday, May 16, 2013 12:36 PM
  • Hi,

    I am running the command from the Exchange 2013 side with the following command

    $remotecredentials = get-credential

    new-moverequest -Identity 'email address' -Targetdatabase 'Database Name' -remoteglobalcatalog 'FQDN of remote server' -remotecredentials $remotecredentials -targetdeliverydomain 'FQDN of target domain' -remotelegacy


    Friday, May 17, 2013 8:18 AM
  • Hi

    What happens if you leave off the -remotelegacy parameter?

    I don't think that this is required for 2010 to 2013 moves.

    Cheers, Steve

    Friday, May 17, 2013 12:25 PM
  • HI,

    I then get the following error

    Parameter set cannot be resolved using the specified named parameters


    Carsten Holfelder

    Friday, May 17, 2013 12:31 PM
  • Try the command like this:

    $Cred = Get-Credential
    New-MoveRequest -Id <email address> -Remote -TargetDatabase <DBName> -RemoteHostName autodiscover.yourolddomain.com -RemoteCredential $Cred -TargetDeliveryDomain yournewdomain.com

    This worked for remote 2010 -> 2010 moves I have done and I suspect that it will work for 2010 -> 2013 and 2013 -> 2013 too.


    Friday, May 17, 2013 12:43 PM
  • Hi,

    I now get the following error

    The call to 'net.tcp://Destination Server FQDN/Microsoft.Exchange.MailboxReplicationService
    Destination Server FQDN (15.0.620.24 caps:3F)' failed. Error details: Object reference not set to an instance
    of an object..
        + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], CommunicationErrorTransientException
        + FullyQualifiedErrorId : 2E0A8546,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
        + PSComputerName        : Destination Server FQDN


    Carsten Holfelder

    Monday, May 20, 2013 8:52 AM
  • That is a problem with the MRSProxy - can you check that the mailbox replication service is running and that port 443 is not blocked between the servers.

    Also as your issue appears to be different from the original post in this thread (and it's answered already) could you open a new thread?

    Cheers, Steve

    Monday, May 20, 2013 12:17 PM
  • I am experiencing these same issues today: Source Forest: Server 2008 R2, Exchange 2010 SP-3. Target Forest: Server 2012, Exchange 2013 CU2. 

    Prepare-MoveRequest.ps1 is successful. 

    Running command: New-MoveRequest -Identity <source mailbox> -TargetDatabase <database> -RemoteGlobalCatalog <FQDN source GC> -RemoteCredential $RemoteCredentials -TargetDeliveryDomain <target domain> -RemoteLegacy

    Error: RemoteLegacy moves must involve Exchange 2010 or lower versions only.

    When I take off the "-RemoteLegacy" flag, I get the error:

    Parameter  set cannot be resolved using the specified parameters. 
      + CategoryInfo: InvalidArgument: (:) [New-MoveRequest], ParameterBindingException
      + FullyQualifiedErrorId : AmbiguiousParameterSet,New-MoveRequest

    Monday, October 28, 2013 9:15 PM
  • I did a similar one recently ... 

    I should say that .. Mailbox move was easy enough ( Use ADMT and and exchange scripts --check here for cross forest migration from exchange 2010 to exchange 2013 ) but Public migration is not supported ... 

    After logging a ticket with Microsoft, I was informed that Cross forest Public folder migration from 2010 to 2013 is NOT SUPPORTED !!!!!!!!

    The only supported path for Public folders is cross forest 2010 to 2010 and then inter forest 2010 to 2013 ... .

    At the time of post there is already SP1 out for 2013 and such issues are still not addressed ... :(

    • Proposed as answer by Riddhim Dhawan Saturday, April 12, 2014 8:48 PM
    Saturday, April 12, 2014 8:48 PM