Copy, Organize, or Move Files With Blober

The same file browser and destination controls serve very different goals, and problems start when the action doesn't match the goal.

Before choosing filters or a path template, decide which statement is true:

1. "I need another copy exactly as this is."
2. "I need a backup, but only of useful files."
3. "I need a second copy arranged more clearly."
4. "I need the files relocated and removed from the source."

Blober supports all four, and the safest settings are different for each.

Use this for disaster recovery, provider migration, or preservation when changing paths would make verification harder.

Action: Copy
Source: selected files or folders
Advanced Filters: unchanged
Include Subdirectories: enabled
Path Template: empty

Blober preserves the relative folder structure under the selected source folder. This is the simplest workflow and often the correct one.

Don't add a path template only to look organized. The first job of a backup may be to match the source exactly.

Use this when the source contains rebuildable or irrelevant material:

Action: Copy
Selection: broad project folder
Include: required extensions or paths
Exclude: proxies, caches, temp files, dependencies
Path Template: empty or {file_dir}/{filename}

The destination can keep the original hierarchy and leave out the noise.

This approach is useful for:

• Source code without installed dependencies
• Video originals without proxies
• Business records without autosaves
• Approved exports without drafts

Every exclusion decides what you won't be able to restore from this backup, so confirm that the omitted files really can be rebuilt or discarded.

Use this when the source should stay untouched but the new copy should be easier to browse.

Action: Copy
Template: {file_ext}/{file_created_date}/{file_dir}/{filename}

This can split a mixed source by type and date while keeping nested project folders.

It helps most when copying from:

• Flat object-storage prefixes
• Camera-cloud libraries
• Shared drives with inconsistent top-level folders
• Old disks accumulated over many years

Having an organized second copy does not mean the original can be deleted.

Use Move only when the files should disappear from the source after a successful transfer.

For example:

• Retiring completed projects from expensive active storage
• Moving approved files out of an intake area
• Relocating files into a final archive after verification
• Cleaning up a provider after a completed migration

Move is a transfer plus a deletion. A wrong include rule can leave files behind, a wrong path rule can put them somewhere unexpected, and a broad selection can relocate more than you meant to.

The safe sequence is:

1. Build the intended workflow as Copy.
2. Test a representative folder.
3. Verify destination paths and open sample files.
4. Confirm counts and task results.
5. Use Move only for the verified scope.

Blober can use the same supported provider on both sides when the adapter and action allow it. That lets you reorganize one bucket, container, drive or account into another location.

The destination must not be:

• The same folder as the source
• Inside a selected source folder

An overlapping destination could be picked up again while Blober scans the source, or cause a file to be copied onto itself, so Blober blocks it. Choose a sibling folder, a different bucket or container, a separate account, or another provider.

Example:

Source: incoming-media
Destination: organized-media
Action: Copy
Template: {file_ext}/{file_created_date}/{file_dir}/{filename}

A workflow records the source, selection, filters, destination, action and path expression, so an organization rule that worked once can be run again.

Examples:

• Run the same camera ingest after each shoot.
• Copy each month's reports into a dated archive.
• Move completed exports from intake to delivery.
• Archive large files after projects close.

Before you rerun an old workflow, preview it again. The source folders and naming conventions may have changed since the filter was written.

Preview & Summary answers:

• Which filters are active?
• Which files currently match?
• How many items and known bytes are represented?
• What destination path will each example receive?
• Is {file_dir} preserving the expected relative structure?

You save the workflow before you run it, and saving transfers nothing. Running it creates a task that tracks per-file progress and results.

Use the simplest row that meets the need, and add filters or a template only when the goal calls for them.

What is the difference between Copy and Move? Copy leaves the source as it is. Move transfers the files and then removes them from the source, so test the same rule as a Copy first.

Can I reorganize files into another folder on the same cloud? Yes, when the provider and action allow it. The destination can't be the source folder or a folder inside the selection, so pick a sibling folder, another bucket or container, or a separate account.

Does saving a workflow start the transfer? No. Saving stores the configuration. Running the workflow creates a task that tracks per-file progress and results.

• Blober Path Templates: Organize Files During Transfer
• File Organization Workflows for Creators, SMEs, and IT