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 Behaviors

Preserve File Versioning Between Locations

Learn how to configure how file versions are handled for migration jobs.

Written by Andrea Harvey

Updated at June 17th, 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 All Versions Limited Versions Box File Versions

Overview

Some platforms keep snapshots of every change made to files. Version preservation determines how file versions are handled in the transfer. When version preservation is enabled for a job (the default option), DryvIQ will attempt to preserve all or the specified number of versions of the files, if supported on both platforms. If version preservation is turned off for a job, DryvIQ transfers only the most recent file version.  

Regardless of the version preservation option you select, the number of versions that can be transferred is contingent on what each platform supports.

 

All Versions

This option preserves all versions on both the source and destination. For example, if a file has five versions, all five versions will be transferred (if the destination platform supports this number of versions).

Limited Versions

This option allows you to specify the number of versions you want to transfer. For example, if a file has five versions and the preservation value is set to 2, DryvIQ will transfer only the most recent two file versions. 

Box File Versions

Each Box account type is limited to the maximum number of file versions that can be accessed. This means that while the UI shows as many versions as you upload, you can only access a certain number of versions. In addition to the default version maximum, account administrators can set the maximum number of file versions to save and track for the account. Both the default file version maximum and any custom version settings added to the Box account affect version transfers. Please refer to Box’s version history documentation to understand the version limitations of your account.

 

 

file versions versions versioning

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Change Item Inspection Policy
  • Allow Truncation
  • Allow Unsupported File Names to be Changed
  • Link Detection and Remediation

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand