{"id":"data-transfers.transfer-completed-but-nothing-changed","url":"/faq/data-transfers/transfer-completed-but-nothing-changed","category":{"id":"data-transfers","title":"Data Transfers"},"subcategory":{"id":"problems","title":"Problems and messages"},"question":"Why did my transfer say Completed but nothing changed at the destination?","alt_questions":["transfer completed but no files copied","sync finished nothing happened","files not at destination after transfer","completed with zero bytes","copy did nothing"],"short_answer":"Usually Dry run was on (it completes without changing anything) or everything already matched, so nothing needed sending. Check the log and the full destination path in the transfer's status card.","answer_markdown":"Two common reasons:\n\n- **Dry run was on.** A dry run goes through everything and completes without changing any file. Check the transfer's log — it lists what *would* have happened. Set it up again with **Dry run (preview only)** off.\n- **Everything already matched.** Copy and the syncs skip files that are already identical, so a transfer between two places that are already in step finishes quickly with little or nothing to send.\n\nAlso make sure you're looking at the destination folder you actually chose — the full path is in the transfer's status card.\n\nRelated: [What is a dry run?](/faq/data-transfers/what-is-a-dry-run) · [Why is a repeat run faster?](/faq/data-transfers/why-is-a-repeat-transfer-faster)","answer_html":"

Two common reasons:

\n\n

Also make sure you're looking at the destination folder you actually chose — the full path is in the transfer's status card.

\n

Related: What is a dry run? · Why is a repeat run faster?

","answer_text":"Two common reasons:\n\n- Dry run was on. A dry run goes through everything and completes without changing any file. Check the transfer's log — it lists what would have happened. Set it up again with Dry run (preview only) off.\n- Everything already matched. Copy and the syncs skip files that are already identical, so a transfer between two places that are already in step finishes quickly with little or nothing to send.\n\nAlso make sure you're looking at the destination folder you actually chose — the full path is in the transfer's status card.\n\nRelated: What is a dry run? · Why is a repeat run faster?","tags":["completed","dry run","troubleshooting"],"related":[{"id":"data-transfers.what-is-a-dry-run","question":"What is a dry run and how do I read its results?","url":"/faq/data-transfers/what-is-a-dry-run"},{"id":"data-transfers.why-is-a-repeat-transfer-faster","question":"Why does running the same transfer again finish so much faster?","url":"/faq/data-transfers/why-is-a-repeat-transfer-faster"},{"id":"data-transfers.where-is-the-transfer-log","question":"Where can I see the details or log of a transfer?","url":"/faq/data-transfers/where-is-the-transfer-log"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"Why did my transfer say Completed but nothing changed at the destination? — Storage Studio FAQ","description":"Usually Dry run was on (it completes without changing anything) or everything already matched, so nothing needed sending. Check the log and the full destination path in the transfer's status card.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Data Transfers","path":"/faq/data-transfers/"},{"name":"Why did my transfer say Completed but nothing changed at the destination?","path":"/faq/data-transfers/transfer-completed-but-nothing-changed"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/data-transfers/transfer-completed-but-nothing-changed","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"Why did my transfer say Completed but nothing changed at the destination?","alternateName":["transfer completed but no files copied","sync finished nothing happened","files not at destination after transfer","completed with zero bytes","copy did nothing"],"acceptedAnswer":{"@type":"Answer","text":"Two common reasons:\n\n- Dry run was on. A dry run goes through everything and completes without changing any file. Check the transfer's log — it lists what would have happened. Set it up again with Dry run (preview only) off.\n- Everything already matched. Copy and the syncs skip files that are already identical, so a transfer between two places that are already in step finishes quickly with little or nothing to send.\n\nAlso make sure you're looking at the destination folder you actually chose — the full path is in the transfer's status card.\n\nRelated: What is a dry run? · Why is a repeat run faster?","url":"https://storagestudio.us/faq/data-transfers/transfer-completed-but-nothing-changed"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Data Transfers · Problems and messages

\n

Why did my transfer say Completed but nothing changed at the destination?

\n

Short answer: Usually Dry run was on (it completes without changing anything) or everything already matched, so nothing needed sending. Check the log and the full destination path in the transfer's status card.

\n

Two common reasons:

\n
  • Dry run was on. A dry run goes through everything and completes without changing any file. Check the transfer's log — it lists what would have happened. Set it up again with Dry run (preview only) off.
  • Everything already matched. Copy and the syncs skip files that are already identical, so a transfer between two places that are already in step finishes quickly with little or nothing to send.
\n

Also make sure you're looking at the destination folder you actually chose — the full path is in the transfer's status card.

\n

Related: What is a dry run? · Why is a repeat run faster?

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}