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 Maintenance

Creating a Migration Job

Learn the basics of creating a new migration job.

Written by Andrea Harvey

Updated at June 25th, 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 Creating a Job

Overview

The DryvIQ Platform’s bidirectional hybrid/sync capabilities enable organizations to leverage and preserve content across their storage platforms. Seamless to users, new files and file changes from either system are automatically reflected in the other. DryvIQ uses jobs to perform specific actions between the source and destination platforms. While several job types are available, the most common types of jobs are copy and sync. See Job Transfer Direction for more information.

Creating a Job

To create a job, click Create job on the Jobs page. 

 

This launches the Create job wizard, where you select all the applicable options for your migration scenario. Configure the preferred job configuration on each step, and click Next to advance to the next step (or Previous to return to the previous step). Refer to the table below for an overview of each step and links to documentation. 

 

Job Creation Step Description
Job Type 

The job type defines the kind of job and the actions the job will perform with the content. There are five job types available:

  • Basic Transfer Basic transfer: This will copy all content (files, folders) from the source to the destination. Each Job run will detect any new content on the source and copy it to the destination.
  • Folder Mapping Folder Mapping Jobs: DryvIQ automatically creates a unique job for each folder in your hierarchy. The child jobs inherit configurations from the parent job. The parent job can be controlled and manipulated just like a transfer job, but no data is transferred when this job is executed. Instead, each execution creates, modifies, or deletes its child jobs, which are responsible for data transfer.
  • User Job Mapping User Job Mapping: DryvIQ will create a unique job for each user account that can be matched between the source and destination connections.
  • Network Home Drive Mapping Network Home Drive Mapping: DryvIQ will create a unique job for each user account that can be matched between the source and destination connections.
  • Intelligent Migration: This job type is used in combination with content scans to copy or move content from any of your source connections to a specified destination connection. 
Locations During this step, you will select your source and destination connections and the path for the job. You can enable impersonation for the job during this step.
Category  Categories allow for the logical grouping of jobs for reporting and filtering purposes. The category is optional and does not alter the job function in any way. DryvIQ comes with a “Default” category assigned to all new jobs. You can create and manage custom categories based on your needs.
Policies The Policies step is where you define what should happen once items have been successfully transferred and set up rules around dealing with content as it is updated on your platforms while the job is running. Policies define how DryvIQ handles file version conflicts and whether or not it persists a detected file deletion. Each job has defined policies, and the settings are NOT global across all jobs.
Behaviors Behaviors determine how the job should be executed and what actions to take in different scenarios. Some behaviors are enabled by default as recommended settings to ensure content is transferred successfully to the destination.
Advanced Options The Advanced section provides optional job configurations that determine what features you want to preserve, filter, or add during your content transfer. 
Summary During this step, you will review the configuration settings selected before creating the job. You will also set up the job schedule and configure stop policies.

 

job migration job create job create a migration job

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Creating a Connection
  • Creating Jobs Using REST API
  • Basic Transfer Job

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand