Skip

Drawing 04 · File movement

Home / SFTP

Transfer drawing

Files need a route and a receipt.

Official MobaXterm materials describe a graphical SFTP browser that appears with an SSH connection. We help teams define what may move, where it lands, and how an operator verifies the result.

Blueprint file-transfer route from Windows folders through encryption to a remote server
SELECT · TRANSFER · VERIFYConceptual transfer model
Source
Authoritative local file, version, and selection rule.
Destination
Remote directory, filename rule, and owning service.
Permission
Who may read, write, replace, or remove.
Integrity
Size, checksum, parse, or application-level confirmation.
Retention
Local staging and remote cleanup expectations.
Exception
Partial upload, collision, interruption, or wrong-path response.
  1. Prepare

    Name the source and destination before connecting.

  2. Observe

    Confirm the SSH host and current remote path.

  3. Move

    Use the approved direction and overwrite rule.

  4. Verify

    Check the agreed evidence, not merely a completed progress bar.

Transfer questions

Should credentials appear in the document?

No. Record the approved credential source and owner, not the secret.

Do you provide a managed transfer service?

No. This engagement documents client-operated workflows using approved systems.

Can the same route support remote editing?

Possibly, but direct remote editing deserves separate recovery and version-control decisions.

Start from the connection record.

Review SSH session design