Cross forest migration Exchange 2013 to Exchange 2016

Preparing a cross-forest migration from Exchange 2013 to Exchange 2016. The migration itself will take a couple of weeks, so it's important that cross-forest availability is enabled and that autodiscover is functional. I've been reading several post and compiled a list of steps, could some check if these are correct?

Situation

Cross forest migration from contoso.local to internal.contoso.com

Source forest (single domain): contoso.local (Exchange 2013)

Target forest (single domain): internal.contoso.com (Exchange 2016)

SMTP domain: @contoso.com

1. Check connectivity between the two forests
2. Check that no ports are blocked
3. Setup conditional forwarders or secondary zone
4. Verify DNS functionality by pinging resources in and from both forestss
5. Create a 2-way forest trust (transitive)
6. Enable SID history on the forest trust
7. Add the target forest domain admin in the built in admin group of source forest/domain.
8. Install ADMT and the Password Export Service
9. Install Exchange 2016 in the target forest
10. Configure Exchange 2016 (send and receive connectors, add and bind the required certificates). Just like setting up a normal Exchange Server
11. Set up an internal send connector on exchange2013.contoso.local to send email for contoso.com to exchange2016.internal.contoso.com
12. Set up an internal send connector on exchange2016.internal.contoso.com to send email for contoso.com to exchange2013.contoso.local
13. Ensure the receive connectors on both exchange2013.contoso.local and exchange2016.internal.contoso.com are configured for anonymous authentication and will accept connections from the other server.
14. Set up a new accepted domain on exchange2016.internal.contoso.com for contoso.com and ensure it is set to internal relay.
15. Test the Outlook Web Services and Outlook Connectivity
16. Create GAL sync service account
17. Add the serviceaccount to the recipient management group: ADD-RoleGroupMember "Recipient Management" –Member "Galsync"
18. Enable remote PowerShell: Set-user -identity "GALSYNC" -RemotePowerShellEnabled $True
19. Schedule GAL sync script, The script finds the mail-enabled  users in one domain, and creates contacts for them in the other domain. Existing contacts will also be updated and deleted as needed.
20. Verify connectivity to the Exchange 2016 server using testexchangeconnectivity.com
21. Export the Autodiscover from the target forest to the source forest: Export-AutoDiscoverConfig -TargetForestDomainController <TargetForestDomainControllerName> -TargetForestCredential (Get-Credential)
22. Add AvailabilityAddressSpace of shared domain to source forest: Get-ClientAccessServer | Add-ADPermission -AccessRights extendedright -ExtendedRights "ms-exch-epi-token-serialization" -User "<sourceforest\Exchange Servers>"
23.  Enable MRS service on the Exchange 2013 server in the source forest (Set-WebServicesVirtualDirectory -Identity “Exch2013.contoso.local\ews (default web site)” -MRSProxyEnabled $true)
24. Verify MRS proxy by opening: https://<ews internal FQDN>/EWS/mrsproxy.svc
25. Check if there’s enough space to write the logs, if not circular logging can be enabled
26. Prepare the move request by running: .\Prepare-MoveRequest.ps1 -Identity “alias” -RemoteForestDomainController “sourceDC” -RemoteForestCredential $Rcred -TargetMailUserOU “OUDN”
27. Move the mailbox to the Exchange 2016 server in the target forest: New-MoveRequest -Identity “alias” -Remote -TargetDatabase “DBName″ -RemoteGlobalCatalog “sourcedomainDC” -RemoteCredential $Rcred -TargetDeliveryDomain “DomainSuffix” -RemoteHostName “SourceexchangeEWSName”
28. Migrate the user account using ADMT
29. Verify mailflow, calendar sharing once the user and mailbox have been migrated
30. Migrate distribution groups using ADMT, first export Exchange Attributes and import them into the target forest once the distribution groups have been migrated