My Day✳All blog articles ↗

Map old and new names before renaming project files

Resolve destination conflicts before applying a checked name mapping.

Before renaming, record each file's old and new path. Check whether destinations are free and distinct from one another. An occupied name is a reason to stop and choose another, not overwrite the existing file. The mapping helps recover previous names under the same conditions; it does not promise a universal undo for every change.

2 planned renames; 1 initial destination conflict
2 planned renames; 1 initial destination conflict

What to do

  1. Write old–new path pairs and preserve the files' extensions.
  2. Check each destination for an existing file and conflicts with other planned rows.
  3. Resolve conflicts before changes, then compare the result with the retained mapping.

Example

Fictional example: 2 independent text files have no external links: a.txt → walk-outline.txt and b.txt → walk-notes.txt. There is 1 occupied destination, walk-outline.txt. Keep it; choose the free walk-outline-v2.txt for a.txt instead. File contents remain unchanged.

My Day · Windows

My Day can manually save the mapping as a note; renaming happens separately.

Buy My Day for Windows ↗