Unable to set the new directory in Copy Data" Sage 50 error explained
Sage 50 cannot create or write to the destination folder you chose for the copied company data, so the copy stops.
When Sage 50 shows “Unable to set the new directory in Copy Data”, it means the program tried to create or switch to the destination folder for your copied company data and was refused. Despite the wording, the problem is almost never your data itself; it is the folder, the path, or the permissions around the copy operation.
What the message actually means
“Copy Data” is the maintenance function that duplicates a company’s data files into a new location. To do that, Sage 50 must create the destination directory and then set it as the active working directory for the copy. When either step fails, Windows or the program rejects the request and you get this message. In plain terms: Sage 50 could not make or use the folder you pointed it at.
Common causes
- The destination folder is on a drive or network share that is unavailable, read-only, or full.
- You do not have Windows-level write permission to the folder, which is common on network shares, second machines, or folders under protected system locations.
- The path is too long, contains characters Sage 50 cannot handle, or includes a mapped drive letter that is not visible to the account running Sage 50.
- Another user or process has the company data open, locking the files mid-copy.
- Antivirus or backup software interferes with the newly created folder before Sage 50 can write into it.
What to try, safest first
Copy to a simple local folder
Choose a short, plain path directly on the local hard drive, such as a new folder you create yourself at the top level of the drive. Avoid spaces, special characters, and long folder names. This rules out network and path-length issues in one step.
Check the folder permissions
Right-click the destination folder, check that your Windows user has full write access, and confirm the drive is not full or write-protected. If Sage 50 runs elevated on your machine, make sure the folder is accessible to that elevated context too.
Use a UNC path instead of a mapped drive
If the destination is on a network share, mapped drive letters can be missing or inconsistent between sessions. Typing the share as a direct network path rather than a letter often resolves the failure.
Close other sessions and pause interference
Make sure nobody else has the company open, and temporarily pause antivirus or backup jobs that may grab the new folder the moment it is created. Then retry the copy.
Check the source data
If the copy still fails on a known-good local folder with full permissions, the source company data itself may be damaged, and Sage 50 is failing before it ever reaches the directory step. That is less common, but it does happen, and it needs a different fix than folder troubleshooting.
When to get help
If you have tried a clean local destination and the message persists, the next useful step is a free evaluation of the company file itself. Our engineers can inspect the data, confirm whether the fault is in the file or the environment, and if the goal of the copy was to move to QuickBooks, handle the Sage 50 to QuickBooks conversion directly. For damaged Sage 50 / Simply Accounting data, we also offer a dedicated database repair service; you can send the file for a no-cost assessment and a quote before deciding anything.