Copy and Move Items in UAPP File Studio
Choose file-operation destinations, control copy overwrite and understand File Studio move merging, replacement and partial task failures.
Select one or more files or folders in the normal file view and use Copy or Move. For multiple items, use the toolbar: right-click selects a single item instead.
Copy Items
| Field | Behavior |
|---|---|
| Selected items | Review the items and count before submission. |
| Destination Folder | Required; enter an account-relative folder or use Browse → Select Folder. |
| Overwrite existing files | Optional and initially off. Enable only when replacing destination content is intended. |
Click Copy to submit. Copy preserves source items. With overwrite enabled, matching destination files can be replaced. Directory copies merge existing directories and skip conflicting child files when overwrite is off; skipped child files may not appear as failed top-level items.
Unchecked overwrite is not complete protection
The current low-level copy implementation logs an existing destination but does not stop a directly selected file or symbolic link from replacing it when overwrite is off. Use an empty destination or preserve conflicting files first, even with the checkbox unchecked. Copy can also normalize destination ownership and modes.
Move Items
Review Selected Items, choose the required Destination Folder, then click Move. The dialog has no overwrite checkbox: it explicitly merges into the destination and replaces existing files when necessary. The service rejects moving a source into itself or its own subtree.
Move can replace destination files
Preserve existing destination content first. Move merges matching directories and can replace matching files, then removes successfully moved source content. A failed batch can leave some items moved and others at their original location.
Verify the result
Watch Tasks until the operation finishes. Inspect counts and errors, refresh both locations, and confirm needed files remain intact before retrying or deleting originals.
Neither operation updates application configuration, database references, domain document roots or public URLs. Moving a live project can break it immediately. Choose a separate staging folder where appropriate and update dependent configuration through its own documented controls. Demo servers block these writes.