Migrating WinMentor to a new server: a complete guide without data loss
How to move WinMentor from an old server to a new one (or to the cloud) without losing a single record. Complete checklist + rollback plan.
Mihai Istrati - CTO Azuvio · 2026-05-23 · 8 min · ERP & Integrations
The migration that must not fail
Moving WinMentor to another server is a critical operation: one hour of downtime is bearable, but losing a month of transactions is a catastrophe. This guide covers standard migration (local network) + Enterprise (SQL Server).
Step 0: Decide why you are moving
Good reasons: old server (>5 years), poor performance, need for modern remote access, IT consolidation, compliance (RAID, automated backup).
Bad reasons: "because I can". If the current server works fine, don't move it.
Step 1: Preparation (1-2 weeks before)
1. Document the current configuration:
- Exact WinMentor version (Service → About)
- Installed modules (inventory, payroll, agents, etc.)
- Installation path, database path
- List of users + permissions
- Customisations (custom reports, modified forms)
2. Notify the team: date and time of migration (preferably weekend or night)
3. Prepare the new server:
- Windows Server (or Windows 10/11 Pro for small networks)
- Minimum 8 GB RAM (16+ recommended for WinMentor Enterprise)
- SSD for the database
- SQL Server installed (for Enterprise)
- Network with static IP
Step 2: WinMentor license key
Contact your WinMentor distributor and announce the migration. The USB dongle is moved physically, but soft licenses must be REACTIVATED on the new server. The distributor generates a new key in 1-3 days (usually with a transfer fee of €50-150).
DO NOT start the migration without confirming you have the new key ready, otherwise, you will be locked out after the move.
Step 3: Complete backup on the old server
24h before the migration:
1. WinMentor backup (Service → Save database)
2. Full SQL Server backup (for Enterprise), full + transaction log
3. Copy all folders: installation, databases, custom reports, forms, configurations
4. Copy registry keys related to WinMentor (HKLM\Software\WinMentor)
5. Save everything to an external disk + cloud (minimum TWO copies)
Step 4: The actual migration (4-8 hour window)
1. Notify the team: WinMentor offline starting at time X
2. Force logout all users (for local network)
3. FINAL backup on the old server (transactions may have occurred in the meantime)
4. Install WinMentor on the new server, the identical version to the old one
5. Activate the license with the new key
6. Restore database from the final backup
7. Copy custom reports + forms into the corresponding folders
8. Reindex + database integrity check
9. Test connection from 2-3 client stations
Step 5: Configure client stations
On each client PC:
1. Modify the WinMentor shortcut → path to the new server (UNC \\newserver\winmentor)
2. Or modify the configuration file (winmentor.ini)
3. Test login + test transaction
4. Check printers (custom forms may have absolute paths)
Step 6: Integrity check (CRITICAL)
Before declaring the migration a SUCCESS, verify:
1. Current month balance = identical to the old server
2. Sales + Purchases ledger for the last month = identical
3. Accounts Receivable + Accounts Payable balances = identical
4. Stock levels per warehouse = identical
5. Payroll reports = identical
If DIFFERENCES appear → STOP migration → rollback to the old server → investigate.
Step 7: Rollback plan (essential)
Before migrating, decide:
Rollback trigger: what constitutes failure (>5% balance differences, user lockout, license error)
How to revert: the old server remains ON but disconnected from the network for 7 days, in case of problems, reconnect and you are back in 30 minutes
Communication: who notifies the team in case of rollback
Step 8: Post-migration (first 2 weeks)
1. Monitor daily the new server's performance
2. Verify automated backups are running on the new server
3. Keep the old server powered on but disconnected for another 14-30 days
4. Document lessons learned for the next migration
"I want zero-downtime migration"
For companies that cannot accept even 4 hours offline (e-commerce, 24/7 retail): WinMentor alone does not support this, but modern architectures with Azuvio on top of WinMentor can act as a buffer (orders enter Azuvio, are persisted, and pushed into WinMentor once the migration is complete). Zero transaction loss.
Conclusion
WinMentor migration is a simple operation if well-planned. The critical point = new license key confirmed BEFORE starting. The second = multiple backups + rollback plan. With these ready, actual downtime = 4-6 hours, minimal risk.