In this topic:

• Prerequisites
• Considerations
• Starting an Migrate Workspaces Task
• Reviewing the Migrate Workspaces Task
• Reviewing the Migrate Workspaces Task Events

Prerequisites

Any Connections that are required by Reports must be migrated before scheduling a Workspace migration.

The Default Target Admin User configured in your Power BI project, is added to migrated Workspaces to ensure that access to migrated Workspaces is retained if a matching administrator account is not available for a migrated Workspace. We recommend that you retain this for safety.

Considerations

Your target tenant might already host Power BI Workspaces created before the migration. In cases where a Workspace name already exists in the destination, the migration will merge report, semantic model and Workspaces permissions data from the source tenant.

After Workspace migration, report users will remain the same as the users in semantic model.

We recommend that you run only one migration task at a time to avoid scheduling delays.

Starting a Migrate Workspace Objects Task

1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
2. From the navigation pane, click Migrate > Projects to open the My Projects list.
3. Create a new project or open an existing project.
4. From the Power BI tile on the project dashboard click Open. Then select the Workspaces tab.
5. Select one or more Workspace that you want to migrate.
6. Click Migrate in the List View menu. The New Migrate Workspace Objects Task wizard starts.
7. Start
   1. Task Name - You can specify a custom name. The default name is Migrate Workspace Objects.
   2. Use the settings from an existing migration template for this task - select this option if you have already saved a previous migration templates. if this is the first time you are migrating mailboxes, keep this option unchecked.
      • Select template - select a template that you previously created, from the dropdown list.
   3. Go to Summary step - select this option to preserve the settings and go directly to the last step of the wizard. If you do not select this option, but you have selected a template, you can step through the wizard and edit the settings in the template.
   4. Click Next.
8. Migration Options

   

   1. Migrate objects using source names - If the objects do not exist in the target workspace they will be migrated using the source name. If a source object with the same name exists in the target workspace, choose from the following collision handling options:
      • Skip processing and no changes will be made to the target environment
      • Migrate the object and add a prefix or suffix to the source name

        Enter a prefix or suffix as described below:

        • Add prefix - specify a prefix for the workspace object name. Whitespaces are not supported.
        • Add suffix - specify a suffix for the workspace object name. Whitespaces are not supported.

      • Overwrite the target object
   2. Migrate objects with the source name and a prefix or a suffix - Select this option to always create new objects in the target workspace using the specified prefix or suffix for the object names. This task will skip any objects with the new name if they already exist in the target workspace..

      Enter a prefix or suffix as described below:

      • Add prefix - specify a prefix for the workspace object name. Whitespaces are not supported.
      • Add suffix - specify a suffix for the workspace object name. Whitespaces are not supported.

   3. Re-migrate previously processed objects - select this option to remigrate workspace objects that were previously migrated and replace the target workspace object with the source object.
   4. Refresh permissions for previously migrated objects - select this option will not migrate new objects. It will only update permissions for previously migrated objects based on the Permissions selections.
   5. Click Next.
9. Processing Options
   1. Skip rebind - Select this option to prevent Power BI from retaining the data source connection for reports during migration. After migration, data in the reports cannot be refreshed in the target tenant because the original data source connection information has not been migrated. If you clear this option, data source connection will be migrated but some unsupported data sources connection types, like SQL with OAuth 2.0 authentication will be skipped. See What we migrate for supported data types.
      • Skip connection rebind for unsupported connections only - select this option to check the connection type for a semantic model. If the connection type is supported then the data source connection for reports is retained, otherwise the data source connection rebind is skipped during migration.
      • Always skip connection rebind - select this option to migrate all reports and semantic models without processing the connection to the original source data.
   2. Include reports created with a live connection to the Power BI Service - select this option to migrate reports that were created with a live connection to a previously published semantic model.

      NOTE: At least one report must be directly bound to a semantic model without a live connection.

   3. Maintain semantic model names during export - select this option to retain the source semantic model name when this is extracted though the Power BI export process, and not the default report name for the semantic model.
10. Permissions
    1. Default Target Admin User - Specify the default target admin user to use as the workspace owner when any workspace user has no match in the target tenant.
    2. Set workspace content permissions - select this option to resolve source and target permissions if there is a mismatch between existing content permissions. If this option is not selected, and the Default Target Admin User is not specified, the settings from the existing default target admin user will be used.
       • Add from source - this option migrates accounts from the source to the target that are not already in the target. Existing target accounts, groups, and roles remain unchanged. If the source accounts are mapped to target accounts that already have workspace permissions, then those target accounts will not be updated.
       • Update from source - this option migrates only mapped accounts with workspace permissions to the target. The target accounts, groups, and roles are updated to match the source permissions. Any existing permissions on the target that do not exist in the source are ignored. Permissions of other accounts in the target workspace that are not mapped to a source account are not updated.
       • Synchronize with source - this option updates target accounts, groups and roles to the source permissions. Existing account permissions that are not in the source are removed. After synchronization, target permissions of mapped accounts are the same as the source.
11. Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
       • Run now - task runs immediately.
       • Run later - task must be started manually.
       • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
       • Priority - select a priority from the dropdown for the objects scheduled for migration with this task . Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the objects are queued (Migration state = Queued). When the system accepts new migration work, objects are taken from the queue based on the assigned priority and age in the queue.
    2. Click Next.
12. Summary
    1. Save task settings as a migration template - select this option to save the settings in this wizard as a reusable migration template.
       1. Migration Template Name - specify a name for the template. If you have changed the settings of a preselected template, specify the same template name to apply the changes to the template when you complete the wizard. All saved templates are displayed in the Templates tab.
    2. Verify the task specifications as described below:
       1. Name - name of the task. The default name is Migrate Workspace Objects. You can specify a custom name.
       2. Default Target Admin User - name of the admin user specified for this task.
       3. Incremental migration - indicates whether or not this option has been selected.
       4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    3. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
13. When the task completes, the Workspace State column in the Workspaces list is updated.

Reviewing the Migrate Workspaces Task

1. Open the Tasks tab.
2. Select the Workspace migration task that you want to review.
3. In the task details pane that opens, the information presented is as described below:
   1. Task Status - current status of the task.
   2. Type - Type of the task. The type is MigrateWorkspaces.
   3. Created - Date and time when the task was created.
   4. Modified - Date and time when the task was last updated.
   5. Last Operation - The action that was most recently performed in this task.
   6. Schedule - Date and time when the task started. Now indicates that the task started immediately after the task was created.
   7. Priority - the priority of this task.
   8. Events (number) - Number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.
   9. Workspaces (number) - The number of Workspaces that were selected for migration and the number of Workspaces passing through the various states from Migrating to Migrated.

Reviewing the Migrate Workspaces Task Events

1. Open the Tasks tab.
2. Select the Workspace migration task for which you want to review the events.
3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
4. Select an event that you want to review. In the event details pane that opens, the information presented is as described below:
   1. Object - name of the Power BI object if applicable.
   2. Task - name of the task.
   3. Time - date and time when the event occurred.
   4. Summary - a descriptive statement about the event if an exception occurs.