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

Zip Unsupported File Types

Learn how to configure migration jobs to add unsupported file types to a compressed archive file to reduce flagged items.

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

Overview

Enabling this job behavior allows DryvIQ to compress any file that is not supported on the destination into a .zip format before being transferred. This will be done instead of flagging the item for manual remediation and halting the file transfer. For example, if you attempt to transfer the file "db123.cmd" from a Network File Share to SharePoint, DryvIQ will compress the file to "db123.zip" before transferring it over, avoiding an error message. By default, the Zip unsupported file types toggle is enabled, indicated by its green status. You can disable this behavior as needed. 

Additional configuration settings are available to handle unsupported content when creating the job using the REST API.

 

 

zip compressed archive unsupported file types

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Allow Truncation
  • Allow Unsupported File Names to be Changed
  • Convert Box Notes
  • Change Item Inspection Policy

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand