Import files

Import files only after you know the target folder. Uploading into the wrong place creates permission mistakes, search noise, and cleanup work.

Choose an import method

Method	Use it when
Web upload	You are adding normal files or folders into the current Explorer folder
Append or save as version	You are updating an existing file’s history instead of creating a new file
SynckHub Desktop	You need local edit, sync, Save As, or longer-running file workflows
Managed migration	You are moving a large existing repository or doing a formal onboarding migration

Upload files or folders in the web app

1. Open Explorer.
2. Navigate to the folder that should own the files.
3. Use upload, drag and drop, or the file picker.
4. Confirm the destination before starting.
5. Keep the upload dialog open until the durable finish completes.
6. Open the destination folder and verify the result.

Understand upload progress

SynckHub upload progress has more than one phase.

Phase	Meaning
Staged on server	The browser has transferred bytes to server staging storage
Blob stored or durably finished	The server has hashed, stored, committed, and projected the final repository state

Do not treat an upload as complete just because browser byte transfer reached 100%. The durable finish step is what makes the file reliably available in the repository.

Append or save a new version

Use an append-version or save-version workflow when the new file content belongs to an existing file record.

Good examples:

• replacing a draft with a revised document
• saving a reviewed contract version
• preserving history for a file that collaborators already know

Avoid uploading a revised file under a new name unless you intentionally need a separate file.

Use Desktop for heavy file flows

Use SynckHub Desktop when:

• local tools create the file
• network interruptions are likely
• the workflow depends on a local working copy
• you need Save As ingestion from a desktop application
• the import is too large or too operationally sensitive for casual browser upload

For large migrations, plan the migration separately. Do not start by dragging a company file share into a browser window.

Post-import checklist

• Files appear in the intended folder.
• Names are clear and deterministic.
• Search can find representative imported files.
• Access behaves as intended for collaborators.
• Version history is correct when updating existing files.

Common mistakes

Mistake	Better approach
Uploading into repository root	Open the owning folder first
Creating duplicate revised files	Append or save a version when history should stay together
Moving large batches after upload	choose the destination before uploading
Announcing files before checking access	verify with one intended collaborator first

Next step

Continue to Share and Manage Access.