A symbolic link stores a path to another location. Moving the link does not necessarily move the file it refers to, and copying a project does not automatically prove that all its linked data came along. Diagnose the link and its target before replacing anything.

Locate the actual target

Record the link's current location and inspect its target information. If your file manager does not expose enough detail, ask support to inspect the link without following or replacing it. Keep the original project structure available while investigating.

An absolute target starts from the filesystem root. For example, a link aimed at an old project location can continue pointing there after the link itself moves. If that original location disappears, the link becomes unusable even though the new project folder looks complete.

A relative target is interpreted from the directory containing the link. Consider a link inside a project's reports folder that points to ../data/results.csv. Moving the whole project while retaining those internal folders can preserve that relationship. Moving only reports changes the surroundings and may leave the expected data folder absent.

Repair the relationship deliberately

Find and open the intended target directly. Confirm its content and that it belongs to this project version. A similarly named file elsewhere is insufficient evidence; reconnecting to the wrong dataset can be less obvious than a broken link.

Choose whether the project should keep its original relative structure or reference a stable external location. Work on a copy where possible. Have the application maintainer or an experienced administrator recreate the affected link using the confirmed target, preserving the old link information for comparison. Avoid forced replacement commands copied without understanding their destination.

Finally, open the file through the repaired link and through its target, then perform the project's normal read operation. Check that the project still works after the old source location is unavailable. This tests the dependency that a successful folder copy alone cannot establish.

Sources: GNU documentation, GNU documentation.