In this guide 6 sections
List everything the office PC does, copy the database to a cloud server, then run real invoices through the copy before you switch. Pick a quiet evening for the cutover, leave the old PC untouched as a fallback, and check printers, scheduled jobs and accounting exports the next morning.
Write down what the office PC really does
Billing software on one PC does more than its menu shows. Someone set up a nightly copy of the Access .mdb file to a USB stick years ago. Another person exports a sales CSV every Friday for the accountant, yet nobody remembers either task until it quietly stops.
Sit with the daily user. Open Task Scheduler, the Startup folder, the ODBC data sources and the printer list. Then note which shared folders and UNC paths the program touches while an invoice is saved.
Record the database engine and its version, such as SQL Server Express or MySQL, plus the program version, the licence key and the Windows user the service runs under. This sheet becomes your test plan. Keep it short. One page is plenty.
- Database engine, version and file location
- Scheduled tasks, batch files and backup scripts
- Printers, label printers and the paper sizes used for invoices
- Export folders read by the accountant or a bank upload
- Licence key, dongle or machine lock tied to this PC
Copy the database and stand up the cloud server
Close the program first. Copy the database files in full, and never while the program is open. A half-written file will restore as a corrupt one, and you will not learn that until the day you need it. Test the restore.
Create a Windows Server instance of the edition the vendor supports, install the program, restore the copy and open it as a test user. Then restrict RDP to named people behind a VPN, and switch on daily disk snapshots.
Check the clock, time zone and regional date format. Invoice dates, day-end closing and the financial-year rollover all depend on them, and a new cloud server often starts on UTC while your office does not.
Test with real invoices before anyone relies on it
Take ten recent invoices of different kinds, including one with a batch number and an expiry date, and one raised against a purchase order. A credit note, a part payment, a discount-line invoice and one for a customer with a very long name make a good mix. Re-enter each one on the cloud copy and compare totals and tax lines against the printed originals, line by line, with a second person reading aloud.
Print them to PDF and to paper. Printers are where most moves go wrong. A cloud server cannot see the USB printer on the front desk, and a redirected one may print the logo shifted by a centimetre. Map a network printer or use a print redirect and then check the margins, the logo and the invoice number sequence.
Let the cashier who bills every day try it for an afternoon. Slow screens show up fast. So do laggy barcode scanners and a missing Crystal Reports runtime.
- Totals and tax lines match the originals
- Invoice numbers continue from the last one issued
- Reports for the last month open without errors
- Printing works from each billing desk
- Login speed is acceptable on the office connection
Choose a cutover evening and keep the old PC alive
Pick a quiet evening. Choose one after the last invoice of the day and well away from month-end, when the accountant is not waiting on a trial balance. Stop all billing, take a final database copy, restore it to the cloud server and run the same ten invoice checks again. Only then tell staff the new address and give each desk its own login.
Do not wipe the old PC. Lock the program with a note on the screen. If the cloud server fails on day one, you return to a machine with a known database and lose a few hours, not a week of entries.
Write the decision point down in advance. If billing cannot run by nine the next morning, the team goes back.
Check the links that fail quietly
Exports fail silently. The file lands in a folder that no longer exists on the new server, and nobody notices until the ledger looks short at month-end. Run an export on day one.
Check SMTP email sending, PDF invoice mailing, scheduled reports and the backup job as well. Restore last night’s backup to a spare folder on the server and open it in the program, because a backup nobody has ever restored is only a hope.
After two clean weeks, retire the old PC. Pull its drive, label it with the date and keep it in a drawer for a month in case an old invoice needs a second look.
Office PC move worksheet
A one-page worksheet in three blocks. The first lists what the old PC does, with columns for task, who depends on it, where it runs and what replaces it. The second is a test table of ten invoices holding original and new totals, tax lines and print result. The third is a cutover timeline with a rollback decision time and the owner who makes that call.
Open a blank worksheet to printQuestions owners ask
Can billing software that runs on one PC work on a cloud server?
Usually yes, if the vendor licence allows installation on a server and the program does not depend on a local dongle or a machine-locked key. Check the licence terms first, then test the program on a trial server before you commit to the move.
How long should the cutover take?
For one application with a modest database, the final copy and restore often fit inside an evening. The test copy you made earlier tells you the real time, so plan the window from that figure and add a margin.
What if the internet line at the office is slow?
A remote desktop session needs little bandwidth, but a line that drops hurts every billing desk at once. Test during busy hours, and keep a mobile hotspot as a standby. Slow Wi-Fi often causes more trouble than the server.