A background transfer lets you browse other folders while files move, but the responsive main window is not evidence that the transfer finished. In WinSCP, each queue entry represents an operation, which may contain several files.

Before starting a batch, note its source, destination and a few expected filenames. Use a small disposable transfer first if this is a new server or a changed connection setup. Keep the source available until the actual destination has been checked.

Inspect the operation state, not just the moving file

Choose Transfer in background on the transfer-options dialog. Background operations use separate server connections, and operations beyond the configured concurrency limit wait. Adding an item to the queue therefore does not mean that its transfer has started.

Show the queue through View, Queue in the Explorer interface or Options, Queue in Commander. Read the Progress state: Waiting, Suspended, Query, Error or Prompt requires a different response from Completed. In a multi-file operation, one line describes overall progress while other lines describe the current files.

A background prompt may not automatically appear, depending on preferences and whether the main connection is idle. Double-click the relevant queue row or use its Show query/error/prompt action to read what is needed. Do not remove confirmations merely to make the queue appear less interrupted.

Close the loop for each intended transfer

For a two-folder handover, check both operations separately. One completed folder does not establish that the other has left Waiting or passed an overwrite question. Resolve only the prompts whose paths and consequences you understand.

After completion, inspect the destination and open representative files, including one from each nested folder that matters. If a file was intentionally skipped, record that decision so its absence does not become an unexplained missing item later.

The queue can hide when empty, and display of completed entries is configurable. Its disappearance alone is weaker evidence than the operation result and the expected files being present. Keep an outcome note for the batch before closing the application or changing the network connection.

If you cancel an unfinished operation, identify what remains incomplete and verify the destination before planning a retry. This separates a deliberate stop from a successful handover and prevents someone from treating a partly populated folder as the finished delivery.

Sources: WinSCP documentation, WinSCP documentation.