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

Allow Unsupported File Names to be Changed

Learn how to change unsupported file names during migration 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 Replace with Underscore Encode Invalid Character

Overview

This behavior controls whether DryvIQ can change the names of folders and files that don't comply with the destination platform’s rules for unsupported characters. By default, this behavior is turned on for the job. DryvIQ will rename a file or folder instead of flagging it for manual remediation and preventing it from being transferred. You can choose between two options for how you want the content to be renamed. Turn the toggle off if you prefer DryvIQ not to rename items with unsupported characters. When this behavior is off for a job, files and folders with unsupported characters will be flagged for manual remediation. 

 

Replace with Underscore

This option replaces invalid characters with underscores. For example, if DryvIQ encounters a file named "Congrats!.txt" during a transfer to a platform that doesn’t support exclamation marks in file names, DryvIQ will rename the file to "Congrats_.txt" on the destination.

Encode Invalid Character

This option encodes invalid characters instead of replacing them with an underscore. The UTF8 bytes for invalid characters are used and converted to a hex string. For example, a file named "123白雜.txt" would be converted to "123E799BDE99B9CE8.txt."

 

invalid names rename files underscore encode unsupported file names

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Allow Truncation
  • Zip Unsupported File Types
  • Preserve File Versioning Between Locations
  • Change Item Inspection Policy

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand