Operate//guide // IT management
Accounting software on a network: setup, moving to another computer, backup
Where the database lives, what rights the workstations get, how to move the software to a new computer without losing documents, and how to check that the automatic backup can actually be restored.
Updated: 17.11.2026 · ~7 min read
In a small company, “the server” is often the accountant’s computer. The accounting database lives on it, and the other computers in the office connect to it over the network. The arrangement works for years. It breaks when that computer fails, when Windows has to be reinstalled, or when the company buys a new computer and wants to move the software onto it.
Google searches in Romania show exactly these moments: “instalare saga client server” (installing Saga client-server), “mutare saga server pe alt calculator” (moving the Saga server to another computer), “schimbare ip server saga” (Saga server IP change), “saga backup automat” (Saga automatic backup). On the forum of one such program, someone described reinstalling Windows without having saved the databases and asked whether they could still be recovered.
This guide is not written for any particular program. The steps below are about the network and the data. Menus, ports, file names and the exact installation order differ from one vendor to another and come from the vendor’s documentation.
Where the database actually lives
Accounting software works on a network in one of two ways:
- shared folder: the data is a set of files in a folder on one computer, and the program on each workstation opens them over the network like any shared file;
- client-server: a database service runs on the main computer, and the programs on the workstations send it requests. The workstations never touch the files directly.
The difference matters for backup and for moving. With a shared folder you copy a folder, provided nobody is working in the program at that moment. With client-server, the service keeps the files open all the time, and a copy taken while it runs can come out corrupted.
Find out the model before the first problem. The documentation says which model the software uses and where it stores data by default. On a workstation, the program’s settings show the path or address it connects to. Write them down outside that computer too.
The computer that holds the data
It does not have to be an expensive server, but it has to be treated like one:
- it stays on while the others work, with no sleep or hibernation, and updates do not restart it in the middle of the day;
- it is connected to the network by cable;
- it has a fixed IP address, set on the computer or through a reservation in the router that hands out addresses;
- it runs on a UPS, so a power cut does not interrupt a write to the database;
- it is not the computer someone uses all day to open attachments and browse random sites.
A fixed address solves a frequently searched problem, the changed IP. If the router gives the main computer a different address after a restart, the workstations look for the database at the old address and show a connection error. Some programs can be tied to the computer’s name instead of its IP. If yours allows that, the documentation says so.
Windows 10 and 11 are not designed as servers and have a limit on simultaneous connections. For a few workstations they are fine. For more users, a dedicated server is worth discussing.
Sharing and permissions
With the shared-folder model:
- share only the program’s data folder, not the whole disk;
- each person connects with their own account, not everyone with the same user and the same password;
- only the people who work in the program get modify rights, everyone else gets no access;
- avoid the “Everyone, Full Control” setting. A computer infected with ransomware encrypts everything it can modify over the network, the database included.
With client-server, the workstations do not need access to the data folder. They need the main computer’s firewall to let connections through to the database service. The port and the service name differ from one program to another, so the firewall exception is made following the vendor’s instructions. Turning the firewall off “to make it work” is not a fix.
Permissions inside the program, for instance who sees salaries or who can delete documents, are separate from those in Windows. Both have to be set.
Moving to another computer
When moving, trouble comes from rushing: the software is installed on the new computer, a folder is copied, and a few days later someone notices that a week’s worth of documents is missing. An order that avoids this:
- Write down the exact version of the software on the old computer and check the documentation on whether to install the same version on the new one or go straight to the latest.
- Check with the vendor how the licence or activation code is transferred. Some licences are tied to the computer, and the transfer has to be requested before the move.
- Pick a time when nobody is working and close the program on every workstation.
- Make a backup with the program’s own function (save, archive, export, whatever the vendor calls it) and, separately, a copy of the whole data folder. Put them on a USB stick or a NAS, not only on the old computer.
- Prepare the new computer: fixed IP, cable, UPS. Then install the software and, if needed, the database service, following the vendor’s guide.
- Restore the data with the program’s function, open the company on the new computer and check the last documents entered before the move.
- Point the workstations to the new address. If the new computer takes over the old one’s IP, and the old one leaves the network, workstations configured by IP can reconnect without changes. Those configured by computer name have to be updated.
- Do not wipe the old computer for a few weeks. It is one more copy, in case something is missing.
An automatic backup that can actually be restored
The copy has to leave the computer that holds the data without depending on someone remembering. A few rules:
- use the program’s backup function or the database’s own backup tool. Copying files while the service is running can produce a copy that will not open. If the program has no scheduled backup, a Windows scheduled task can stop the service, copy the data and start the service again, at night. Whether that method suits your software is something to confirm in the documentation;
- the copy does not stay on the same disk. It goes to a NAS, to a disk that is not permanently connected or to a cloud service, and at least one copy is kept outside the office. The full rule is in the guide Business backup: the 3-2-1 rule;
- copies from several days are kept, not only the latest. If the database breaks on Tuesday and you notice on Thursday, Wednesday’s copy is broken too;
- someone gets a message when the backup fails and actually reads it;
- the backup folder is not shared with write access for everyone, otherwise ransomware encrypts it along with the database.
A scenario, as an example: a company with five computers keeps the database on the accountant’s machine. The software makes an automatic backup every evening into a “Backup” folder on the same disk. The disk fails. On paper, the company had a backup. In reality it had two copies on one failed disk. With a daily copy on a NAS and a weekly one on a disk kept in another building, the same scenario would have ended with at most one day of work to redo.
The restore test
A backup that nobody has restored is an assumption. Once a month and after any change (a new version of the software, a new computer, a new place for the copies), take the latest copy and restore it to another computer, never over the database people are working in. The accountant opens the company and checks the latest invoices and the latest trial balance. Write down the date, which copy you restored from and how long it took to get usable data.
If the restore depends on a single person or on a password only they know, better to find out now. How to organise a monthly test is in the guide What a restore test looks like.
Network setup, moves and backup for accounting software can be taken over as part of the company’s IT management, together with the rest of the computers.
FAQ
Accounting software on a network
What does “client-server” mean for accounting software?
One computer runs a database service, and the program on every other computer sends it requests over the network. The workstations never open the data files directly. The other model is the shared folder, where each workstation opens the files over the network. The software’s documentation says which one it uses.
Can I keep the database on a NAS?
It depends on the software. A client-server program needs a computer that runs the database service, and an ordinary NAS does not run it. For shared-folder programs, some vendors support a NAS and others do not. Check the vendor’s documentation before moving the data. A NAS is still a good place for backup copies.
I reinstalled Windows without saving the database. Can it be recovered?
Sometimes. Do not install or copy anything else onto that disk, because every write can overwrite the old data. Look for other copies first: a USB stick, an external disk, a backup folder on another computer, an export sent by email. If there are none, a data recovery lab can try to get the files off the disk, with no guarantee that it will succeed.
How often should the backup run?
At least once a day, after working hours, keeping copies from several days. Before an update or a move, a manual copy is worth making too. The underlying question is how much work the company is willing to redo if the database breaks right now.
Have you ever restored your accounting database?
Want to move the software to a new computer or find out whether its backup can be restored? We can talk it through.