You can specify a migration configuration file as a command-line option with the profile migration command. In the configuration file, you can specify settings such as the source and target profile locations, which are passed to the profile migration utility at runtime.

The migration configuration file is optional. You can override settings that you specify in the configuration file by typing the corresponding command-line options.

Migration Configuration File Format

The migration configuration file is in XML format, which makes the file easy to read, edit, and extend. For definitions of the settings, see Migration Configuration File Settings.

<migconfig takeownership="takeownership_value">
  
  <!-- specify the source V1 profiles to be migrated -->
  <source>
    <!-- specify the location of user profiles to be migrated -->
    <profilepath>source_profile_path</profilepath>
  </source>
  
  <!-- specify the target destination of converted V2 profiles -->
  <target>
    <profilepath>target_profile_path</profilepath>
  </target>
  
  <!-- specify other profile migration settings -->
  <migration>
  
    <!-- migration settings for profile folders and files -->
    <profile>
      <!-- by default, all top-level profile folders are included -->
      <!-- except 'Cache', 'History', & 'Local AppData' -->
      <includeolders>included_profile_folders</includefolders>
      <excludefolders>excluded_profile_folders</excludefolders>
    </profile>
    
    <!-- migration settings for profile registry hive -->
    <registry [disabled="1"]>
      <!-- by default, no registry keys are converted -->
      <includekeys>included_registry_keys</includekeys>
      <excludekeys>excluded_registry_keys</excludekeys>
    </registry>
    
  </migration>
  
</migconfig>