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 Policies

New Items Job Policy

Learn how to configure how DryvIQ handles new items identified on the source during subsequent migration jobs runs

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 Transfer the New Items Do Not Transfer Items That Were Not Present on the Initial Run

Overview

This job policy determines how DryvIQ should handle new items identified on the source during subsequent job runs. 

Transfer the New Items

This option tells DryvIQ to transfer any new items identified on the source to the platform. This option is ideal for smaller jobs. For Intelligent Migration jobs, this is the only New Items policy available.

Do Not Transfer Items That Were Not Present on the Initial Run

When this option is set for a job, an inventory of the source content is taken on the first job run. Items added after that will not be considered on subsequent job runs and will not be transferred. This setting is ideal for large jobs. Note that this setting is not available for Intelligent Migration jobs. 

migrate migrations job policy new items

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Creating a Connection
  • Creating Custom Connectors
  • Creating Migration Reports

Copyright 2025 – DryvIQ.

Knowledge Base Software powered by Helpjuice

Expand