Migrating Saga to a new server — how to do it without data loss (2026 guide)
Switching computers or moving Saga to a dedicated server? Here is the complete 8-step procedure, including a verification checklist.
Mihai Istrati — CTO Azuvio · 2026-05-21 · 7 min · ERP & Integrations
When migration is necessary
Three main scenarios:
Old computer is too slow — Saga runs smoothly on SSD + 16GB RAM, but suffers on an old HDD with 4GB RAM.
Moving from desktop to multi-user server access — for a company with 3+ simultaneous users, a Windows server with shared Saga is the only high-performance solution.
Physical location change (office move) — the old computer is retired or sold.
Steps for a correct migration
Step 1 — Full backup on the old computer. See the Saga backup guide. Save `\DATE\`, `\CONFIG\`, `\TEMPL\`, `\ARHIVA\`. Copy to an external HDD + cloud sync (double safety).
Step 2 — Export the Saga license. Saga is licensed per computer (usually via a `license.dat` file or an online key). You need Saga support to "release" the license from the old computer before activating it on the new one. Call support or use the Saga portal (if you have an online account).
Step 3 — Install Saga on the new computer. Download the latest version from sagasoft.ro (using your credentials). Install it in the same path (`C:\SAGA\`) to avoid configuration adjustments.
Step 4 — Activate the license on the new computer. Using the activation code from support, validate Saga on the new hardware.
Step 5 — Restore the database. Copy the backed-up folders from Step 1 over the empty folders installed in Step 3. Note: close Saga completely before performing the copy-paste.
Step 6 — Verify database integrity. Open Saga, open a few companies, and check: the current month's trial balance (must match the old computer), the last invoice issued, and the last tax return filed. If the figures do not match → restart using a newer backup.
Step 7 — Configure automatic backup on the new server. DO NOT skip this step. Set up a script + cloud sync from day 1, not in 3 months "when you have time".
Step 8 — Test print + invoice issuance. Issue a test invoice, print it, and check template alignment. Different printer drivers on the new computer can break formatting.
For multi-user server deployment
If you are moving Saga to a Windows server with 3+ simultaneous users:
Server with Windows Server 2019/2022 (not Windows 10/11 — which has a 20-session limit)
Saga installed in multi-user mode (requires special config — check the guide on sagasoft.ro)
Shared folders with granular permissions on `\DATE\` (read+write for accountants, read-only for managers)
Incremental daily backup with Veeam / Acronis Cyber Protect / Windows Backup Server
UPS (Uninterruptible Power Supply) — sudden power failures corrupt DBF databases.
The most common mistake
Moving the database without releasing the license from the old computer → Saga will not start on the new computer ("license already active elsewhere") and the old computer is already scrapped or given to an employee. You will have to contact support, prove the situation, and pay a re-issuance fee (approx. 50-150 EUR). Always release the license BEFORE decommissioning the old computer.
Modern alternative: SaaS layer over Saga
For rapidly growing companies that no longer want to manage Saga infrastructure, the modern solution is: Saga remains on a minimal local server (1 computer, for the accountant only), while the operational side (multi-channel orders, automated invoicing, dashboards, multi-user) lives in the cloud on Azuvio. See the Saga ↔ Azuvio connector. Migrating Saga infrastructure becomes 10x simpler because all operations are decoupled.
Conclusion
Correct Saga migration = 8 steps + 30-90 min of work + 0 surprises. Mistake #1: license left on the old computer. Mistake #2: backup not configured on the new server. See also "How to backup the Saga database" for complete resilience.