11.12 Performing a Folder to Folder Migration

A folder to folder migration has flexible target specification options that are not available in the previous migration options. When you perform a folder to folder migration, you can either specify an existing target folder or create a target folder in the Data Migration Wizard. You can also decide whether to migrate all of the files at once, or skip some files and migrate them later.

The preferred time for performing a folder to folder migration is when all files located in the folders to be migrated are closed, such as during the weekend. However, if you have terabytes of data to migrate, some folder to folder migrations might need to be started during the week, when some of the files intended for migration are open. In cases such as these, we recommend a two-phased folder to folder migration:

Migrating Closed Files: While users are still logged in, you migrate all of the closed files on your network. This will be the vast majority of your network files. Because the Skip Open Files option is selected, open files are not migrated, but the filenames and paths of all of the open files are logged in a text file.

NOTE:If you perform a Cross-Empire Data Migration when all users are logged off, you do not need to migrate skipped files.

Migrating Skipped, New, and Modified Files: After having all users log off, migrate the skipped files, migrate the new and modified files, then compare the files on the source and target servers to verify that everything migrated correctly.

11.12.1 Migrating to an Existing Target Folder

Migrating Closed Files

  1. Make sure you have completed the prerequisites and have created a migration proxy account.

    For more information on the prerequisites, see Section 11.3, Prerequisites. For more information on creating a migration proxy account, see Section 11.4, Creating the Migration Proxy Account.

  2. (Conditional) If you want to migrate closed files now and skip some files to migrate later, complete the following steps:

    1. From the Novell Storage Manager ISO image, copy the CEDM folder to the Windows target server.

    2. On each NetWare server from which you are going to migrate data, create a NovScan directory.

    3. From the Novell Storage Manager ISO image, copy the novscan.nlm file from the Utilities\CEDM\NovScan folder to the NovScan directory you created in Step 2.b.

    4. In the new NovScan directory, create a new subdirectory and name it Open.

      Figure 11-1 Summary of Substeps to Complete

  3. In NSMAdmin, click the Main tab.

  4. Click Data Migration.

  5. Click Migrate Data and Trustees.

  6. From the Migration Type drop-down menu, select Folder to Folder.

  7. Click Next.

  8. Fill in the following fields:

    Generate Automatic Mappings: Select this check box to activate the other fields.

    Source Folder: Specify an initial UNC path for a server and volume to browse.

    For example, \\server_name\volume_name\ or \\ip_address\volume_name.

    After a path is entered, you can click the Browse button to browse to the folder you want.

    Target Folder: Browse to select the target folder.

    Create new folder entries for items not having a matching target: Selecting this check box indicates that you want Novell Storage Manager to display both matching and non-matching source and target folders.

    Selecting this check box also indicates that you want Novell Storage Manager to create and populate any subfolders that do not exist in the target folder.

    For example, assume that the source path at \\10.10.10.233\Vol2\Projects is being migrated to \\Corpserver\Projects and the Projects directory on the source server has a Stategov subfolder. If there is no Stategov subfolder in the target folder, a Stategov subdirectory is created to include the directory contents.

  9. Click Next.

    The Data Migration Wizard attempts to match the names of the subfolders of the source path with the subfolders of the specified target directory. If there is a match, the listed folder in the Source Folder field is selected and a corresponding match is listed in the Target Folder column.

  10. Specify a target folder for each source folder that is not automatically matched or that has an improperly matched subfolder by double-clicking the name to bring up the Modify Data Map Entry dialog box.

  11. Remove the existing path in the Target Folder field and click Browse.

  12. Locate and select the desired target folder, then click OK.

    The new target path is indicated in the Target Folder field of the Modify Data Map Entry dialog box.

  13. Click OK.

  14. Click the check box corresponding to the listing with the new target.

  15. Click Next.

  16. Fill in the following fields:

    Overwrite Options: Indicate what you want to take place when duplicate filenames are encountered in the source and target.

    Directory Quota: Specify how quota settings from the source Novell file system should be applied after the migration.

    Target Subfolder: If you want migrated data to be placed in a subfolder, select the Use subfolder check box and specify the subfolder name in the field.

    Advanced Namespace Handling: Selecting this check box allows the Cross-Empire Data Migration subsystem to look for alternate namespaces for files that the Novell file system cannot resolve and therefore cannot migrate.

    For example, files originally saved on a Mac or Linux system might use characters that the Novell file system cannot recognize. By looking for an alternative namespace, the Novell file system might be able to resolve the problem and migrate the file.

    Open File Options: If you want the Cross-Empire Data Migration subsystem to skip all open files on the network and not migrate them, select Skip Open Files.

    Selecting Skip Open Files activates the File List UNC Path field where you specify the name and location of the log file listing all of the open files that are skipped during the migration.

    Specify the UNC path for the directory you created in Step 2.d along with a filename for the text file that will list the skipped files.

    For example, \\server_name\volume_name\directory_name\Open\skip.txt

    or

    \\ip_address\volume_name\Open\skip.txt

    The Cross-Empire Data Migration subsystem does not validate the path, so you must make sure that the path entered is correct. Otherwise, the migration fails.

  17. Click Next.

  18. Fill in the following fields:

    Owner for Target Folder: Use these settings to specify how ownership of the migrated folder is determined.

    • Use Operating System Defaults: This default setting allows the target Microsoft Windows Server to adjust the file ownership according to the setting on the target server.

    • Set Explicit Owner: Allows you to browse and select an object as the explicit owner of the migrated folder.

    Owner for Target Folder Contents: Use these settings to specify how ownership of the migrated folder contents is determined.

    • Use Operating System Defaults: This default setting allows the target Microsoft Windows Server to adjust the file ownership according to the settings on the target server.

    • Set Explicit Owner: Allows you to browse and select an object as the explicit owner of the migrated folder.

    Use the Identity Map: Select this check box if you want Novell Storage Manager to utilize the identity map you created earlier and use the corresponding IDs to copy security rights and file ownership from eDirectory to Microsoft Active Directory.

    • Transfer Rights and Ownership: Select this option if you want to transfer the file and folder security rights along with the ownership settings.

      Be aware that when you transfer the ownership of a file or folder in a Windows network, you are granting the owner Full Rights, which you might not want to provide.

    • Transfer Rights Only: Select this option to transfer only the file and folder security rights.

    • Overwrite Trustees: Select this option to override any existing trustee assignments for a target file or folder with the established Novell eDirectory trustee assignments for those files and folders.

    • Merge Trustees: Select this option to merge the established Novell eDirectory trustee assignments with those of the target files or folders in Active Directory.

  19. Click Next.

  20. (Conditional) If you want to use a filter to include or exclude specific files, select the Use Copy Filter check box and click the Add button.

    1. Fill in the following fields:

      Description: Specify a description of the filter.

      Action: From the drop-down menu, select either Migrate or Ignore, based on whether the filter specifies to migrate files or folders or to ignore them.

      Files, Folders: Specify if the filter applies to files or folders.

      Masks: List the file types to migrate or ignore.

    2. Specify any additional filter criteria in the menus and fields that remain.

      For a detailed explanation of this region of the dialog box, see Section 5.5.8, Setting Vault Rules.

    3. Click OK.

  21. Click Validate.

    Validate shows the result of certain checks that can be run prior to the migration. The Result column shows the status of the validation checks. If errors are displayed, you can choose to correct those errors prior to running the migration.

  22. (Conditional) Take any necessary action in the Active Directory target and then re-run the Data Migration Wizard.

  23. Click Migrate.

    A page appears with details of the data migration events that are queued for processing. To view the status of migration events, click Pending Events. For more information on Pending Events, see Section 12.1.6, Pending Events.

  24. Do one of the following:

    • If you skipped some files to migrate later, click Finish and then continue with Migrating Skipped Files.

    • If you have migrated all of your data, click Finish.

      You are now finished with the folder to folder migration.

Migrating Skipped Files

The second phase of a folder to folder data migration is conducted when all of the users are logged off the network, so all network files are closed.

  1. Have everyone log off the network so that there are no open files on the source NetWare or Open Enterprise Server machines.

  2. Open the text file that you created in Step 16 and view the files that were skipped.

    Do not make any changes to the file. Doing so causes errors during the migration.

  3. Save a copy of the text file.

    For example, if you named the file skip.txt, save a copy as skip_copy.txt.

    After the Cross-Empire Data Migration subsystem migrates the skipped files, it deletes the text file. You can use the copy to verify that the files were migrated.

  4. In NSMAdmin, click the Main tab.

  5. Click Data Migration.

  6. Click Migrate Data and Trustees.

  7. From the Migration Type drop-down menu, select Folder to Folder Using File List.

  8. Click Next.

  9. Skip the Automatic Mappings settings by clicking Next.

  10. On the Define Mappings wizard page, click Add.

  11. In the Add Data Entry dialog box, browse to and select the source and target.

  12. Click OK.

  13. On the Define Mappings wizard page, verify the source folder and the destination folder and click Next.

  14. On the Copy Options - Data wizard page, from the Option drop-down menu in the Overwrite Options region, select Overwrite if Newer and click Next.

  15. (Optional) On the Copy Options - Rights and Owners wizard page, from the drop-down menu of the Owner for Target Folder region, select Set Explicit Owner.

  16. (Conditional) If you chose to set an explicit owner for the folder, click the corresponding Browse button and browse to specify an owner for the target folder.

  17. (Optional) From the drop-down menu of the Owner for Target Folder Contents region, select Set Explicit Owner.

  18. (Conditional) if you chose to set an explicit owner for the folder contents, click the corresponding Browse button and browse to specify an owner for the target folder contents.

  19. Select the Use Identity Map check box and click Next.

  20. On the Copy Filter wizard page, specify the UNC path to the file you created in Step 16.

  21. Click Validate to confirm that the path is correct.

  22. Click Migrate.

    The skipped files are migrated and the text file that you created in Step 16 is deleted.

  23. Click Finish.

  24. Continue with Creating a Job File to Scan the Source Server for New or Modified Folders and Files.

Creating a Job File to Scan the Source Server for New or Modified Folders and Files

With the skipped files migrated, you are now ready to create a job file so the NovScanConfig utility can scan the source server.

  1. From the CEDM folder that you copied in Step 2.a, open the NovScan folder and launch the NovScanConfig utility.

  2. In the Root Directory To Scan for Files field, enter the UNC path to the directory on the NetWare or Open Enterprise Server you want to scan.

    For example: \\oesnw\vol2\dept shares

  3. In the Root Subdirectory Scan Filter region, click the List button, then click the All button to include all of the subdirectories, including new subdirectories, in the directory you specified in Step 2.

  4. Ensure that the drop-down menu listing displays Include.

  5. From the Threads drop-down menu, select the thread count you want for the migration.

  6. In the Folders region, in the first date entry, select the date when you migrated the closed files.

    This specifies that the job file created by the NovScanCofig utility lists all folders that are new or modified since midnight of the selected date.

  7. In the second date entry, select a concluding date for the range.

  8. In the Files region, in the date entry pertaining to Created between, select the date when you migrated the closed files.

    This specifies that the job file lists all files that have been created since midnight of the selected date.

  9. In the second date entry for and, select a concluding date for the range.

  10. Ensure that the drop-down menu listing displays OR.

  11. In the date entry for Modified between, select the date when you migrated the closed files.

    This specifies that the job file lists all files that have been modified since midnight of the selected date.

  12. In the second date entry for and, select a concluding date for the range.

  13. From the File menu, select Save As and save the file as a text file with a .job extension in the NovScan folder that you created in Step 2.b.

    For example: vol2_dept.job

  14. When you are notified that the text file has been saved, click OK.

  15. Close the NovScanConfig utility.

  16. Continue with Using the NovScan NLM to Run the Job File.

Using the NovScan NLM to Run the Job File

  1. At the NetWare server, load the novscan.nlm from the path that you established in Step 2.b.

  2. Select either Y or N.

    If you are scanning an Open Enterprise Server, select Y and then log in as an administrator so that this NetWare server can make a connection to the remote Open Enterprise Server machine.

    If you are scanning a local NetWare server, select N.

  3. At the NetWare console, run the job file that you created in Step 13.

    The following commands can be used at the NetWare console command prompt to perform actions with the NovScan NLM:

    • JOB=path to job file on local server

      The following example is a NovScan NLM directive to run a job file:

      SERVER65: novscan job=sys:novscan\scanvol1.job

    • STOPSCAN

      The NovScan NLM can run one scan job at a time. You might want to stop a scan that is in progress. The following example is a directive for the NovScan NLM to stop a scan that is running.

      SERVER65: novscan stopscan

    • SHOW=ON/OFF

      The NovScan NLM by default shows the names of the directories as they are being scanned. These scanned directories are also logged. You can turn the display and logging on or off by using this parameter. For example:

      SERVER65: novscan show=on

      SERVER65: novscan show=off

    The Files Selected field displays the number of files created or modified since the first phase of the migration.

  4. From your Windows workstation, go to the NovScan folder that you created in Step 2.b.

  5. Observe that a new text file has been created with the same name as the job file that you created in Step 13 but with the addition of -FLIST.

    This new file is a list of all the new and modified files since the first phase of the migration. If you open this file, do not make any changes, because this causes errors during the next phase of the migration.

  6. Save a copy of the text file.

    For example, if the file is named vol2_dept-FLIST.job, save a copy as vol2_dept-FLIST_copy.job.

  7. Continue with Migrating the New and Modified Files.

Migrating the New and Modified Files

Migrating all of the files that are new or modified since the first phase of the folder to folder migration follows the same process as migrating the skipped files. The only difference is that you enter a different UNC path.

  1. In NSMAdmin, click the Main tab.

  2. Click Data Migration.

  3. Click Migrate Data and Trustees.

  4. From the Migration Type drop-down menu, select Folder to Folder Using File List.

  5. Click Next.

  6. Skip the Automatic Mappings settings by clicking Next.

  7. On the Define Mappings wizard page, click Add.

  8. In the Add Data Entry dialog box, browse to and select the source and target.

  9. Click OK.

  10. On the Define Mappings wizard page, verify the source folder and the destination folder and click Next.

  11. On the Copy Options - Data wizard page, from the Option drop-down menu in the Overwrite Options region, select Overwrite if Newer, then click Next.

  12. (Optional) On the Copy Options - Rights and Owners wizard page, from the drop-down menu of the Owner for Target Folder region, select Set Explicit Owner.

  13. (Conditional) If you chose to set an explicit owner for the folder, click the corresponding Browse button and browse to specify an owner for the target folder.

  14. (Optional) From the drop-down menu of the Owner for Target Folder Contents region, select Set Explicit Owner.

  15. (Conditional) If you chose to set an explicit owner for the folder contents, click the corresponding Browse button and browse to specify an owner for the target folder contents.

  16. Select the Use Identity Map check box and click Next.

  17. On the Copy Filter wizard page, specify the UNC path to the new text file that you viewed in Step 5.

  18. Click Validate to confirm that the path is correct.

  19. Click Migrate.

    The new and modified files are migrated and the text file that you viewed in Step 5 is deleted.

  20. Click Finish.

  21. Continue with Creating a Job File to Scan the Source Server for All Folders and Files.

Creating a Job File to Scan the Source Server for All Folders and Files

  1. From the CEDM folder that you copied in Step 2.a, open the NovScan folder and launch the NovScanConfig utility.

  2. In the Root Directory To Scan for Files field, enter the UNC path to the directory on the NetWare or Open Enterprise Server you want to scan.

    For example: \\oesnw\vol2\dept shares

  3. In the Root Subdirectory Scan Filter region, click the List button, and then click the All button to include all of the subdirectories in the directory you specified in Step 2.

  4. Ensure that the drop-down menu listing displays Include.

  5. From the Threads drop-down menu, select the thread count you want for the migration.

  6. In the Folders region, in the first date entry, select the left button, which sets the date to 1/1/1970.

  7. In the second date entry, select the right button, which sets the date to 12/31/2036.

    This range of dates ensures that you identify all folders that exist in the specified path.

  8. In the Files region, in the date entry for Created between, select the left button, which sets the date to 1/1/1970.

  9. In the second date entry for and, select the right button, which sets the date to 12/31/2036.

    Again, this range of dates ensures that you identify all files created in the specified path.

  10. Ensure that the drop-down menu listing displays OR.

  11. Set the date range for modified files to the same dates you used for new folders and new files.

  12. From the File menu, select Save As and save the file as a text file with a .job extension in the NovScan folder that you created in Step 2.b.

    For example: vol2_dept-all.job

  13. When you are notified that text file has been saved, click OK.

  14. Close the NovScanConfig utility.

  15. Continue with Using the NovScan NLM to Run the Job File.

Using the NovScan NLM to Run the Job File

  1. At the NetWare server, load the novscan.nlm from the path that you established in Step 2.b.

  2. Select either Y or N.

    If you are scanning an Open Enterprise Server, select Y and then log in as an administrator so that this NetWare server can make a connection to the remote Open Enterprise Server machine.

    If you are scanning a local NetWare server, select N.

  3. At the NetWare console, run the job file that you created in Step 12.

    The following commands can be used at the NetWare console command prompt to perform actions with the NovScan NLM:

    • JOB=path to job file on local server

      The following example is a NovScan NLM directive to run a job file:

      SERVER65: novscan job=sys:novscan\scanvol1.job

    • STOPSCAN

      The NovScan NLM can run one scan job at a time. You might want to stop a scan that is in progress. The following example is a directive for the NovScan NLM to stop a scan that is running.

      SERVER65: novscan stopscan

    • SHOW=ON/OFF

      The NovScan NLM by default shows the names of the directories as they are being scanned. These scanned directories are also logged. You can turn the display and logging on or off by using this parameter. For example:

      SERVER65: novscan show=on

      SERVER65: novscan show=off

    The Files Selected field now displays the total number of files.

  4. From your Windows workstation, go to the NovScan folder that you created in Step 2.b.

  5. Observe that a a new text file has been created with the same name as the job file that you created in Step 12 but with the addition of -FLIST.

    This new file is a list of all the files from the specified path. If you open this file, do not make any changes, because this can cause errors during the file comparison.

  6. Continue with Scanning the Target Server for All Folders and Files.

Scanning the Target Server for All Folders and Files

  1. From the CEDM folder that you copied in Step 2.a, open the WinScan folder and launch the WinScan utility.

  2. Click the browse button for the Target Directory to Scan field and browse to select the target folder.

  3. Click the browse button for the Output File Path field, browse to the WinScan folder, and in the File name field of the Open dialog box, specify a filename with a .txt extension.

    For example, target-all.txt

  4. Click Open.

  5. Click Run.

    All of the files for the target path are displayed.

  6. Close the WinScan utility.

  7. Continue with Comparing the Source and Target Lists.

Comparing the Source and Target Lists

With file lists generated from the source and target servers, you can now compare the two lists by using the ScanCompare utility.

  1. From the CEDM folder that you copied in Step 2.a, open the ScanCompare folder and launch the ScanCompare utility.

  2. In the Source region, click the browse button for the Datafile field, then browse to and select the.job text file that you observed in Step 5.

  3. In the Target region, click the browse button for the Datafile field, then browse to and select the text file that you created in Step 3.

    After you have specified the source and target files, the Common Path Start Point fields automatically display the first line of each file.

    The next task is to specify a common starting point for the file comparison.

  4. In the Source region, edit the path so that it concludes with the directory name containing the subfolders and files that you migrated earlier.

    For example: \\oesnw\vol2\dept shares

  5. In the Target region, edit the path so that it concludes with the folder name containing the subfolders and files that were migrated earlier.

    For example: G:\Department Shares\

  6. Click Run.

    The ScanCompare utility compares the files and displays the findings.

  7. Use the findings to verify that all files were migrated.

    If the New on Target or Missing on Target fields display entries other than zero, you will need to review the targetnew.txt or targetmissing.txt files to determine the cause of the source and target record count discrepancy.

    You are now finished with both phases of the folder to folder migration.

11.12.2 Creating a Target Folder in the Data Migration Wizard

  1. Make sure you have completed the prerequisites and have created a migration proxy account.

    For more information on the prerequisites, see Section 11.3, Prerequisites. For more information on creating a migration proxy account, see Section 11.4, Creating the Migration Proxy Account.

  2. (Conditional) If you want to migrate closed files now and skip some files to migrate later, complete the following steps:

    1. From the Novell Storage Manager ISO image, copy the CEDM folder to the Windows target server.

    2. On each NetWare server from which you are going to migrate data, create a NovScan directory.

    3. From the Novell Storage Manager ISO image, copy the novscan.nlm file from the Utilities\CEDM\NovScan folder to the NovScan directory you created in Step 2.b.

    4. In the new NovScan directory, create a new subdirectory and name it Open.

      Figure 11-2 Summary of Substeps to Complete.

  3. In NSMAdmin, click the Main tab.

  4. Click Data Migration.

  5. Click Migrate Data and Trustees.

  6. From the Migration Type drop-down menu, select Folder to Folder.

  7. Click Next.

  8. Click Next.

  9. Click Add.

  10. In the Source Folder field, specify an initial UNC path for a server and volume to browse.

    For example, \\server_name\volume_name\ or \\ip_address\volume_name.

    After a path is entered, you can click the Browse button to browse to the folder you want.

  11. Click the Browse button that corresponds to the Target Folder field to locate the share where you want to create the new folder for the migrated data.

  12. Right-click the share, select Create Folder, name the new folder, and click OK.

  13. Click OK to close the Target File System Path Browser.

  14. In the Add Data Map Entry dialog box, click the Browse button that corresponds to the Target Folder field again, browse to and select the new folder, then click OK.

  15. Click OK.

    The defined source and target mappings are displayed.

  16. Click Next.

  17. Fill in the following fields:

    Overwrite Options: Indicate what you want to take place when duplicate filenames are encountered in the source and target.

    Directory Quota: Specify how quota settings from the source Novell file system should be applied after the migration.

    Target Subfolder: If you want migrated data to be placed in a subfolder, select the Use subfolder check box and specify the subfolder name in the field.

    Advanced Namespace Handling: Selecting this check box allows the Cross-Empire Data Migration subsystem to look for alternate namespaces for files that the Novell file system cannot resolve and therefore cannot migrate.

    For example, files originally saved on a Mac or Linux system might use characters that the Novell file system cannot recognize. By looking for an alternative namespace, the Novell file system might be able to resolve the problem and migrate the file.

    Open File Options: If you want the Cross-Empire Data Migration subsystem to skip all open files on the network and not migrate them, select Skip Open Files.

    Selecting Skip Open Files activates the File List UNC Path field where you specify the name and location of the log file listing all of the open files that are skipped during the migration.

    Specify the UNC path for the directory you created in Step 2.d along with a filename for the text file that will list the skipped files.

    For example, \\server_name\volume_name\directory_name\Open\skip.txt

    or

    \\ip_address\volume_name\Open\skip.txt

    The Cross-Empire Data Migration subsystem does not validate the path, so you must make sure that the path entered is correct. Otherwise, the migration fails.

  18. Click Next.

  19. Fill in the following fields:

    Owner for Target Folder: Use these settings to specify how ownership of the migrated folder is determined.

    • Use Operating System Defaults: This default setting allows the target Microsoft Windows Server to adjust the file ownership according to the setting on the target server.

    • Set Explicit Owner: Allows you to browse and select an object as the explicit owner of the migrated folder.

    Owner for Target Folder Contents: Use these settings to specify how ownership of the migrated folder contents is determined.

    • Use Operating System Defaults: This default setting allows the target Microsoft Windows Server to adjust the file ownership according to the settings on the target server.

    • Set Explicit Owner: Allows you to browse and select an object as the explicit owner of the migrated folder.

    Use the Identity Map: Select this check box if you want Novell Storage Manager to utilize the identity map you created earlier and use the corresponding IDs to copy security rights and file ownership from eDirectory to Microsoft Active Directory.

    • Transfer Rights and Ownership: Select this option if you want to transfer the file and folder security rights along with the ownership settings.

      Be aware that when you transfer the ownership of a file or folder in a Windows network, you are granting the owner Full Rights, which you might not want to provide.

    • Transfer Rights Only: Select this option to transfer only the file and folder security rights.

    • Overwrite Trustees: Select this option to override any existing trustee assignments for a target file or folder with the established Novell eDirectory trustee assignments for those files and folders.

    • Merge Trustees: Select this option to merge the established Novell eDirectory trustee assignments with those of the target files or folders in Active Directory.

  20. Click Next.

  21. (Conditional) If you want to use a filter to include or exclude specific files, select the Use Copy Filter check box and click the Add button.

    1. Fill in the following fields:

      Description: Specify a description of the filter.

      Action: From the drop-down menu, select either Migrate or Ignore, based on whether the filter specifies to migrate files or folders or to ignore them.

      Files, Folders: Specify if the filter applies to files or folders.

      Masks: List the file types to migrate or ignore.

    2. Specify any additional filter criteria in the menus and fields that remain.

      For a detailed explanation of this region of the dialog box, see Section 5.5.8, Setting Vault Rules.

    3. Click OK.

  22. Click Validate.

    Validate shows the result of certain checks that can be run prior to the migration. The Result column shows the status of the validation checks. If errors are displayed, you can choose to correct those errors prior to running the migration.

  23. (Conditional) Take any necessary action in the Active Directory target and then re-run the Data Migration Wizard.

  24. Click Migrate.

    A page appears with details of the data migration events that are queued for processing. To view the status of migration events, click Pending Events. For more information on Pending Events, see Section 12.1.6, Pending Events.

  25. Do one of the following:

    • If you skipped some files to migrate later, click Finish and then continue with Migrating Skipped Files.

    • If you have migrated all of you data, click Finish.

      You are now finished with the folder to folder migration.