> For the complete documentation index, see [llms.txt](https://moverdocs.files.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moverdocs.files.com/migration-behavior/file-and-folder-compatibility.md).

# File and Folder Compatibility

Source and destination systems can disagree about valid names, letter case, path depth, and how many items a folder can contain. Review these rules before moving data between unlike systems.

## Case and Accent Matching

Mover compares names without regard to case or accents. It treats names such as `Report.csv` and `report.csv` as the same path even when a provider can store both.

When several source or destination items have the same normalized name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ.

Rename case-only or accent-only duplicates before the live migration.

## Unsupported Names

Mover cannot transfer names containing a backslash or null character, or path components with trailing whitespace. A provider can impose additional filename, reserved-name, path-length, or file-type restrictions. The relevant connection page documents known provider-specific behavior.

## Folder Limits

Mover supports up to 100,000 items in one folder and a maximum folder depth of 50 levels. A folder beyond either limit is recorded as a failure.

Even below the item limit, smaller folders usually list faster and are less likely to time out on collaboration services.

A [dry run](/migration-guide/dry-runs.md) is the safest way to find naming conflicts and folder-limit failures before data is transferred.