Offload into an existing project

Once a project exists, project Offload is a shorter wizard than creating a project from scratch. It already knows your project, primary folder, and destinations, so you only pick the source, decide on a local copy, and start.

Start it with Offloadon the project page (or from the project's More actions menu). The wizard is two steps: Select Source, then Review & Start.

If you only need verified copies and a transfer report, without project tracking, use Standalone offload instead.

If destinations are disconnected

If any of the project's destinations are currently disconnected (drive unplugged, no internet for cloud), the review step shows them clearly and disables Start until they reconnect. The button enables automatically when every destination is back.

Local cleanup panel

If the local-copy option is off and your project's primary folder already contains files with the same names as files on the source, Tusk surfaces a local cleanup panel. Common causes: earlier offloads that landed locally, or files you copied into the primary folder by hand.

The panel lists the conflicting paths and offers choices such as:

• Delete local copies and continue: removes the local files (with explicit safety warnings) so the offload can treat the source as canonical. Tusk warns that this is destructive.
• Switch to copy locally: turns the local-copy toggle on so Tusk handles the paths via standard conflict resolution.

Conflicts with files already in the destinations

Tusk also checks whether files on the source already exist on any of your destinations (in the file index or on disk). If so, you get a conflict-resolution panel: skip or overwrite. See Conflict resolution.

What happens to other syncs while Offload runs

Normal backup jobs for this project pause automatically during Offload so the queue does not fight for drive bandwidth. They resume when the offload completes. Other projects keep syncing as normal.