#Run Migrations

When your device mappings within a migration project are ready for migrations, you can run migrations for the mappings to migrate permissions or rejoin domain.

Refer to the following steps to run migrations for mappings:

1. Click Projects in the left pane to access the Projects page, and click the project name of the project you want to run.

2. On the Project mappings page, select one or multiple mappings for which you want to run migrations.

   NOTE

   To ensure the migration performance, we do not recommend you select more than 5000 mappings at a time to run migrations.

3. Click Migration, you can select to run the following jobs for the mappings:

   • Rejoin domain – Rejoin the source device to the new domain. The Default App configuration and the permissions of source devices will be automatically migrated in the migration.

     The rejoin method depends on the destination connection configuration for the current project. Refer to Create a Migration Policy for details.

     NOTE

     Before the migration begins, save all open documents and close all applications to avoid data loss. Once the migration starts, your computer screen will be locked. Keep the device awake and do not attempt to sign in while the migration is in progress. The device will restart automatically after the migration is complete. Signing in too early may cause unsaved changes to be lost or interrupt the migration process.Change the Device Owner to change the owner.

   • Migrate permissions – Migrate permissions of source device areas to the destination.

     Note that the permission migration requires the device to have rejoined the domain first.

   • Migrate Windows user profile – Migrate desktop configurations and permissions under the user's local Windows user profile (C:\Users\username). This ensures the user retains access to personal data and settings, including desktop, documents, app data, and personalized operating system settings.

     NOTE

     For Entra ID users, this profile migration can now be executed as a standalone job, without requiring a prior Domain Join step.

   • Migrate Entra ID groups – Migrate the Microsoft Entra ID group memberships associated with the device from the source tenant to the destination tenant. To ensure a successful migration, the source Microsoft Entra ID connection must be enabled first. Refer to Create a Connection for details.

   • Register Windows Autopilot – Register the devices with Windows Autopilot in the destination tenant to pre-configure them for use. Windows Autopilot registration is supported only after the device has rejoined the Microsoft Entra ID domain offline.

4. Click OK in the pop-up window to run the migration immediately.

#Collect Logs

When the migration job fails or behaves unexpectedly, you can collect logs for troubleshooting, and contact AvePoint Technical Support for assistance.

Refer to the following two ways to collect logs:

• Run collect logs job - Select the required mappings and click Collect logs to export the latest logs from the device agent.

  You can monitor the job progress in the Migration history section by clicking on the source of a mapping and navigating to the View mapping report page.

  To run the collection job immediately, manually trigger it on the agent of each device. Refer to Install the Device Migration Agent for detailed instructions on how to check the status in agents. Otherwise, the job will start during the next scheduled hourly cycle. Once the logs are successfully collected, they will be available for AvePoint to check.

  NOTE

  The latest migration job must complete successfully. The log collection job is not available for jobs that were stopped or not executed.

  After collecting logs, you can provide the tenant ID and the job ID of logs collection to AvePoint Technical Support for assistance.

• Collect logs directly from the device - If the migration job is stopped or unexecuted, you can retrieve log files directly from the agent device.

  To find the logs file, navigate to: C:\ProgramData\AvePoint\DeviceAgent\Logs. You can find the corresponding log files according to the job ID and provide the log files to AvePoint Technical Support for assistance.

#Change the Device Owner

To change the device owner, run the following commands in Windows PowerShell. Replace "your device name", "the users UPN" and ${$newOwner.id} with the actual device name and user information:

if (!(Get-Module Microsoft.Graph -ListAvailable | Where-Object {$_.Version -eq "2.29.1"})) {
    Write-Host "Installing Microsoft.Graph 2.29.1..." -ForegroundColor Yellow
    Install-Module Microsoft.Graph -RequiredVersion 2.29.1 -Scope CurrentUser -Force
}
Connect-MgGraph -Scopes "Device.ReadWrite.All","User.Read.all","Directory.AccessAsUser.All"
$device = Get-MgDevice -Filter "startswith(displayName,'your device name') and TrustType eq 'AzureAD'"
$CurrentOwner = Get-MgDeviceRegisteredOwner -DeviceId $device.id
Remove-MgDeviceRegisteredOwnerByRef -DeviceId $device.id -DirectoryObjectId $CurrentOwner.id
$NewOwner=Get-MgUser -UserId <the users UPN>

New-MgDeviceRegisteredOwnerByRef -DeviceId $device.id -OdataId "https://graph.microsoft.com/v1.0/directoryObjects/$($NewOwner.id)"