I’m trying to upgrade Immorpos 35.3 to new software, but the process isn’t going smoothly. After starting the upgrade, I ran into issues that I don’t understand, and now I’m worried about causing data loss or system problems. I need help figuring out the correct upgrade steps, common compatibility issues, and how to complete the Immorpos 35.3 software upgrade safely.
Stop the upgrade for now.
Do these steps in order.
-
Make a full backup first.
Export your database.
Copy the app folder.
Copy config files.
If it runs on SQL Server, take a fresh .bak. If it uses MySQL, dump it with mysqldump. Keep one copy off the machine. -
Check the vendor’s upgrade path.
A lot of POS systems do not support jumping from 35.3 straight to the newest build. You often need 35.3 to 36.x, then 37.x, then current. If you skip steps, migrations fail and data gets weird. -
Read the upgrade log.
Look for plain errors like:
database schema mismatch
missing runtime
license validation failed
32-bit to 64-bit conflict
service account permission denied -
Test on a clone.
Restore your backup to a spare PC or VM.
Run the upgrade there first.
If it breaks, your live data stays safe. -
Verify prereqs.
Check OS version.
Check .NET or Java version.
Check DB engine version.
Check disk space.
I like 2x free space vs DB size for upgrades. Safer that way. -
Disable AV for the installer if the vendor says so.
I’ve seen installers get blocked and leave half-upgraded files. Super annoyng. -
If you already started and it failed, do not keep retrying blind.
Grab the exact error text and post it.
Screenshot it if needed.
The key part is the first failure, not the 20 errors after it.
If you share the error message, your database type, and what “new software” means, same product newer version or a replacement system, people here can point you to the next step fast.
I’d add one thing to what @waldgeist said: figure out whether this is actually an in-place upgrade or a migration to a different product. Those are not the same thing, and vendors love using the same words for both.
If it’s a replacement system, don’t let the installer touch the old live database at all. Export customers, items, inventory, sales history, tax tables, and payment mappings into flat files first, then validate the imports with row counts. People skip that part and only notice later that half the SKU aliases or old receipt references never came over. Been there, it was a mess.
Also check peripherals before you focus only on the software. POS upgrades break weird stuff first: receipt printers, cash drawers, barcode scanners, pole displays, card terminals. If the “new software” needs OPOS/JPOS or different drivers, the core app might install fine and still be unusable at the register.
One place I sorta disagree with @waldgeist: I would not disable AV unless the vendor specifically documents it and you can isolate the machine. Too easy to create a diffrent problem while fixing this one.
Post the exact error, your Windows version, DB type, and whether Immorpos 35.3 is 32-bit. That narrows it down fast.
Before you touch the upgrade again, make a restore test, not just a backup. A backup you have never restored is basically a hope file.
I partly disagree with @waldgeist on one point people often miss: compatibility mode is usually not a real fix for POS upgrades. If Immorpos 35.3 only runs because of old DLL behavior, forcing the installer through can leave you with a system that opens but corrupts transactions later.
What I’d check next:
- Clone the machine or image the drive first.
- Check Event Viewer right after the failure. Application and System logs usually tell more than the installer popup.
- Confirm .NET, Visual C++ runtimes, SQL/native client versions, and Windows permissions.
- See whether services are failing to start after install.
- If this is on a live register, test on a spare PC first, same peripherals attached.
For the new software, pros: better support, security, maybe hardware support. Cons: driver headaches, import mismatches, license surprises, workflow changes.
Post the exact error text and install log. That’s where the real answer usually is.