The Start-XAMigration cmdlet is intended for scripted, unattended migrations. For interactive testing, the XenApp 6 Migration Tool includes additional object-specific import cmdlets. These cmdlets offer alternatives to using the –ImportOnly option with the Start-XAMigration cmdlet and the -ObjectType and -Include options with the Set-XAMigrationOption cmdlet.
You can also use these cmdlets during indirect migrations.
These cmdlets use the configured server mappings, migration options, and object property value overrides.
Using the advanced XALegacy cmdlets can be helpful if an object did not migrate as expected. The Get-XALegacy* cmdlets connect to the legacy farm and read the settings for an object in the legacy farm. You can use the Convert-XALegacyObject, New-XALegacyConnection, and Remove-XALegacyConnection cmdlets when creating a custom migration script that does not use the Import-XA* or Start-XAMigration cmdlets.
These advanced cmdlets include objects that cannot be migrated alone (for example, session printers that are inside a user policy, and HMR tests that are inside farm or server settings). This greater granularity may be helpful when troubleshooting migration, because these objects are more complex, with multiple sets of properties.