Document Migrations

This guide covers general information about how document migrations should be prepared for and performed. It is intended to be generalized information for those new to document migrations in MigrationWiz, rather than specific, and should be used in conjunction with your environment and migration guides. 

Document migrations function differently from Mailbox migrations as far as environment preparation and the advanced & support options utilized. 

Document Migrations

Performing a Document Migration

Document migrations follow a general basic flow:

  1. Prepare your source environment (as outlined in your scenario-specific migration guide).
  2. Prepare your destination environment (as outlined in your scenario-specific migration guide).
  3. Verify license quantity and apply (if using UMB licenses). [LINK]
  4. Create a Document migration project (these steps are outlined below).
  5. Create or apply endpoints [LINK].
  6. Add users (this, and all following steps, are laid out in the migration guide for your scenario).
  7. Apply Advanced & Support Options (as directed in your migration guide). 
  8. Verify credentials.
  9. Notify users.
  10. Run the migration.
  11. Retry errors.
  12. Post-migration steps. 

To set up a document migration project, perform the following steps in order:

  1. Click the Go to My Projects.
  2. Click the Create Project.
  3. Create a Document project.
  4. Click Next Step.
  5. Enter a Project name and select a Customer.
  6. Click Next Step.

Advanced & Support Options for Document Migrations

Each scenario-specific migration guide will let you know what options are suggested for that scenario. The following section explains those options in more detail, and provides additional context for their use. When in doubt, follow the instructions in your migration guide. 

Remove Existing Permissions When Unspecified

Option Command: RemoveExistingPermissionsWhenUnspecified=1

Environment(s) & Scenarios: Google Drive to OneDrive for Business; Dropbox (as destination).

Migration Type(s): Document

Description: This option is used to resolve any conflict of permission problems during certain types of document migration projects. This clears existing permissions from the Destination, before adding any new permissions.

Should Convert to Destination Format

Option Command: ShouldConvertToDestinationFormat=1

Environment(s): Google Drive as Destination only

Important: This option will try to maintain migrated items in Google Format.

Description: This support option takes the source system format and will converts it to the destination format.

OneDrive Import/Export URL

Note that this is a suite of options. Some or all may be applicable to your migration. For more information, contact Support.

Option Commands:

Exporting data:

  • OneDriveProExportUrl=https://tenant-my.sharepoint.com - Provides an override option for domain, tenant, and extension identification in OneDrive migrations for the source(export). By default, OneDrivePro attempts to detect this information. In some cases, there may be ambiguity that requires the customer or support to be specific.
  • OneDriveProExportAdminUrl=https://myadmin.sharepoint.com - This is needed when the admin url is not in one of the standard format and thus can't be derived from the OneDriveProExportUrl.

Importing data:

  • OneDriveProImportUrl=https://tenant-my.sharepoint.com - Provides an override option for domain, tenant, and extension identification in OneDrive migrations for the destination (import).
  • OneDriveProImportAdminUrl=https://myadmin.sharepoint.com - Provides an override option for domain, tenant, and extension identification in OneDrive migrations for the destination (import).

Environment(s): OneDrive only

Migration Type(s): OneDrive as source or destination only

Important: The URLs listed in the command are examples only. Replace with your environment URL.

Description: Add these options if the administrative credentials are unable to verify the source or destination target OneDrive containers.

Map Permission Email by Pairs

Option Command: MapPermissionEmailByPairsInProject=1

Environment(s): OneDrive/Google Drive (Destination)

Migration Type(s): OneDrive/Google Drive as destination only.

Important: Permissions generally cannot be migrated unless the prefix of the mail address is the same in the source and the destination. However, choosing Support Option MapPermissionEmailByPairsInProject=1 will allow permissions to be migrated without identical mail addresses.

Description: When OneDrive/Google Drive is the destination, this option can be used to map permissions by pairs in the project. user@domain.com to firstinitial.lastname@domain.com

Government OneDrive/Office 365 Tenant

Note that this is a suite of options. Some or all may be applicable to your migration. For more information, contact Support.

Option Command:

To export from Germany, China, or US Government instances, enter:

  • OneDriveProExportEnvironment

Then select one of the following:

  • AzureGermanyCloud
  • AzureChinaCloud
  • AzureUSGovernment

To import to Germany, China, or US Government instances, enter:

  • OneDriveProImportEnvironment

Then select one of the following:

  • AzureGermanyCloud
  • AzureChinaCloud
  • AzureUSGovernment

Environment(s): OneDrive/Office 365 tenants only

Migration Type(s): Document migrations

Important: This option must be used for all migrations involving China, Germany, or US Government instances.

Description: This option targets the needed URI to migrate data on these specialized Azure instances.

Note: If this option is not used for the listed migration instances, the following error will appear:

Your migration failed checking source credentials. Authentication Error: Bad username or password. You must call the Connect-MsolService cmdlet before calling any other cmdlets.

If this error appears, navigate back to the Project Setup and enter the appropriate option and environment before proceeding with your migration.

​​​Increase Initialization Timeout Window

Option Commands: InitializationTimeout=X        

This option can be adjusted as needed to the following parameters:

Hours:

  • InitializationTimeout=2 will increase the timeout to 2 hours.
  • InitializationTimeout=4 will increase the timeout to 4 hours.
  • InitializationTimeout=8 will increase the timeout to 8 hours.

Milliseconds:

  • InitializationTimeout=7200000 will increase the timeout to 2 hours.
  • InitializationTimeout=14400000 will increase the timeout to 4 hours.
  • InitializationTimeout=28800000 will increase the timeout to 8 hours.

Environment(s): All

Migration Type(s): Document migrations

Important: This value is in hours, up to a maximum of 100 hours.  Values above 100 are in milliseconds.

Description: This option increases the timeout limit to 8 hours.

Rename Conflicting Files

Option Command: RenameConflictingFiles=1

Environment(s): OneDrive

Migration Type(s): Document

Description: Enables document renaming to resolve conflicts

Document Browsing Mode

Option Command: DocumentBrowsingMode=FullCopy     

Choose one of the following customizations: FullCopy | Strict (default)

Environment(s): All

Migration Type(s): Document

Description: Define the browsing strategy MigrationWiz uses for document scanning. All folders are migrated.       

Ignore Conflicting Files

Option Command: IgnoreConflictingFiles=1        

Environment(s): OneDrive/SharePoint

Migration Type(s): Document migrations

Description: Set this value to skip FileAlreadyExists exception in the One Drive (Sharepoint).

Ignore List View Threshold

Option Command: IgnoreListViewThreshold=1   

Environment(s): All

Migration Type(s): Document migrations

Description: Allows the user to continue migration when the list view threshold (> 5000 items) is reached for a specific folder. If the option is not set, an error is logged and migration is halted.

Migrate External User Permissions

Option Command: MigrateExternalUserPermissions=1

Environment(s): Google Drive, Dropbox

Migration Type(s): Document Migrations

Description: Enable external user permission fallback.

Remove Existing Permissions When Unspecified

Option Command: RemoveExistingPermissionsWhenUnspecified=1

Environment(s): All

Migration Type(s): Document

Description: This option is used to resolve any conflict of permission problems during certain types of document migration projects by clearing existing permissions from the Destination before adding any new permissions.           

Was this article helpful?
1 out of 3 found this helpful