Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Migrations
  • Migration Jobs
  • Job Locations

Configuring Job Locations

Learn how to add the source and destination locations for a migration job.

Written by Andrea Harvey

Updated at May 22nd, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Insights
    Prebuilt Insights Custom Insights
  • Content
  • Accounts
  • Activity Log
  • Content Scans
  • Migrations
    Migration Jobs Migration Reports Maps Flagged Items Migration Tools
  • Connections
    Supported Platform Connections Creating Connections Connection Maintenance Connection Pools
  • Entity Types
    DryvIQ Available Entity Types Custom Entity Types Entity Type Maintenance
  • Action Sets
    Creating Action Sets Action Sets Maintenance
  • Settings
    License Performance Notifications Extensions Entity Types Settings Display Settings Configuration
  • API, CLI, and SDK Documentation
    REST API Documentation Command-line Interface SDK Development
  • POC Offering
  • Release Notes
+ More

Table of Contents

Overview Source and Destination Connection Run as User (Impersonation) Impersonating Read-Only or Disabled Users Source Path and Destination Path Child Job Source Path and Destination Path

Overview

The Locations page is where you will select the source connection and destination connection to use for the job. The source defines the current location of the content you wish to transfer; the destination defines where you would like to move your content. Other fields on this page display based on the job type selected and if the platform supports impersonation. 

 

The Locations page for an intelligent migration job only provides an option to select the destination connection. The source connections used for an intelligent migration will be based on the data sources assigned in Discover. You can only select one destination location. If you need to move items to multiple locations, you will need to create individual intelligent migration jobs for each destination location you want to use. Impersonation (Run as user) is available for connections that support this feature, and you can specify the specific path to use. 

 

Source and Destination Connection

Select the connections by clicking Edit in the Source connection or Destination connection fields. This will open the corresponding Connection modal, where you can scroll through the list of available connections. Note that not all connections will display in the list since DryvIQ filters the list to show only connections applicable to the selected Job Type. The list initially only shows the first 50 connections. If you reach the end of the list but don't see the connection you want to use, click Load more to load additional connections. 

 

You can also click Search and use the Search box to find a specific connection. Type the name of the connection or account associated with the connection and press ENTER. The list will display only connections that match your search criteria. 

 

Click on the connection you want to select and click Use this connection. The selected connection will fill in the corresponding connection field. 

Run as User (Impersonation)

Impersonation allows a site admin access to all the folders on the platform, including those that belong to other users. A job can be set up using the username and password of the site admin to sync/migrate/copy files to or from a different user's account without ever having the username or password of that user. If a connection has been created with an account with the proper permissions, you can turn on the Run as user toggle on the source and/or destination. You then select the user you want to impersonate for the job.

Click Choose.

 

Only some platforms support impersonation. They include:

  • Box
  • Dropbox for Business
  • Google Workspace
  • Google Team Drives
  • Microsoft OneDrive for Business
  • Microsoft SharePoint. 
Select the user to impersonate.

 

 

Impersonating Read-Only or Disabled Users

When setting up jobs with impersonation, there are several types of users to choose from. If you select a read-only or disabled user, your job may not perform as expected because different platforms treat these users differently. In this situation, you have several options:

  1. Select a different user: You may have mistakenly selected the read-only or disabled user. To continue unimpeded, select a different user.
  2. Update the user within the platform: Someone may be able to log into the platform and update the user.
  3. Continue with the selected user: The job may perform adequately with the selected user. You can attempt to continue with the selected user.

Source Path and Destination Path

If you wish to transfer all content, leave the source path blank. Otherwise, click Edit to select the specific path you want the job to use. You can also manually specify the path. If the path you specify doesn't exist, DryvIQ will create it. 

For Folder Mapping jobs, a child job will be made for every top-level folder. If a folder is selected for the source path, a child job will be made for every subfolder within the parent folder. 

For Network Home Drive Mapping jobs, a child job will be created for every home drive. If a directory is selected for the source path, a child job will be created for every home drive within the parent directory. 

Select the path to use.

 

Manually enter the path.

 

Child Job Source Path and Destination Path

These fields display for Folder Mapping jobs, User Job Mapping jobs, and Network Home Drive Mapping jobs. You can use the root of each folder or specify the directory you want to use. If the directory does not exist on the destination, DryvIQ will create it.

  • Target the root of each folder: The child job will be created for the first-level folder relative to the source path.


     
  • Target a specific directory within each folder: If a folder exists in every directory, you can define it with this option.

migrate migrations job locations source destination path impersonation run as user

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Reconnecting Connections
  • Searching for Connections
  • User Mappings Using REST API

Copyright 2025 – DryvIQ.

Knowledge Base Software powered by Helpjuice

Expand