Windows · File automation

Custom batch script for Windows folder migration

A known-folder migration workflow with drive selection, confirmation, execution logs and checks at each stage.

Implemented · real migration not validated4 workflow stagesCustom development
01 / Context

The challenge

Moving documents and images to another drive requires handling both the files and the paths Windows uses.

A computer may be running short of space on its primary drive while another drive has spare capacity. Moving files manually addresses only part of the problem: applications and Windows still use the configured locations for Documents, Pictures and other known folders.

This project turns that need into an explicit migration workflow. The script targets six folders belonging to the current user and preserves the profile structure on the selected drive. It is a custom automation deliverable whose use must account for the client's storage layout and operating rules.

02 / Step by step

How the workflow works

  1. 01

    Select the drives

    The operator enters source and destination drives. The BAT normalizes upper- and lowercase letters, checks drive availability and confirms that the expected source profile folder exists before presenting the plan.

  2. 02

    Confirm and record

    Paths are displayed before execution. The routine asks for confirmation, prepares exports of folder-related Registry keys and starts a dated log to track the stages.

  3. 03

    Copy before redirecting

    Desktop, Documents, Downloads, Pictures, Music and Videos are handled individually. The workflow evaluates the copy result before changing the corresponding folder paths used by Windows.

  4. 04

    Complete each folder

    After copying and updating the references, the routine performs the move stage. Failures and files remaining at the source are recorded, so review does not depend solely on a final success message.

03 / Implementation

The work

A BAT routine organizes migration for six user folders, copying data before updating Registry references.

  • Operator-selected source and destination
  • Six standard user folders
  • Copying, path updates and logging

A defined scope

The migration was designed for known folders, rather than transferring an entire Windows installation or reinstalling applications. Defining that boundary avoids mixing unrelated rules within one operation.

AppData, installed programs and other accounts are outside the described scope. OneDrive, corporate folder redirection and special permissions require their own assessment before the tool is adapted.

Validation is part of delivery

A migration script needs evaluation against representative files, filenames and permissions. A proposal can include a simulation stage and a recovery policy tailored to the client's environment.

The project contains backup export commands and logging, but these do not amount to guaranteed automatic restoration. Confirming that backups were created and testing failure behavior are necessary next steps.

Inside the logic

Example migration plan preview

An adapted BAT example that displays folders and their destination. This demonstration does not copy files or change the Registry.

batADAPTED EXAMPLE
@echo off
setlocal
set "DESTINATION=D:\Data"
echo Folder preview:
for %%P in (Desktop Documents Downloads Pictures Music Videos) do (
    echo %%P -^> "%DESTINATION%\%%P"
)
echo No files were moved.
endlocal
04 / Delivery

Delivery and context

The script was implemented and reviewed through source inspection. Real migration must be validated in the project's designated environment.

Deployment considerations

  • Deployment requires a real test in a controlled profile. This stage is still pending.
  • Before use, the backup workflow needs an explicit success check for its exports.
  • The scope covers the specified folders; applications, OneDrive and full profile migration require separate assessment.

Frequently asked questions

Can it be adapted to my company's folders?

Yes. The quote begins with an inventory of sources, destinations, permissions and retention rules. Validation should use a copy or test environment before moving operational data.

Can the displayed code migrate my files?

No. The example illustrates scope selection only. The full routine includes administrative operations and must be prepared and validated for the agreed environment.

A similar workflow in your business?

Tell me which platform you use, how your workflow operates today and what needs to change. Together, we can define the scope, integrations and acceptance checks for your project.

Request a quote

Scope and pricing tailored to your project.

Related services

Custom software development

Business software, internal tools and integrations built around your workflow.

Windows automation and custom batch scripts

Scripts and tools for repeatable Windows workflows.