Upgrading your accounting or job cost system is one of the riskier projects a contractor undertakes. It touches payroll, billing, job cost, and often dozens of integrations. Done well, it is a non-event. Done badly, it can delay a pay application cycle or corrupt data that took years to build.
Whether you run Sage, Viewpoint, or another platform, the planning principles are the same. Here is a roadmap that keeps surprises small.
Start With Why and When
Know the reason for the upgrade. Common drivers include vendor end of support, security fixes, a needed feature, a move to cloud hosting, or an operating system that the old version cannot run on. The reason sets the urgency.
Then choose the timing carefully. Avoid payroll year-end, major billing cycles, audits, and the start of a big project. Ask your accounting team when they can tolerate downtime and work backward.
Inventory What Touches the System
Before changing anything, list every connection:
- Payroll and time capture, including field timecard apps
- Project management and document platforms
- Bank files, positive pay, and payment portals
- Reporting tools, spreadsheets, and database queries
- Custom reports and macros that someone built years ago
- Remote access methods and any third-party add-ons
Surprises usually come from the integrations and custom pieces nobody remembered. Interview the accounting staff, not just IT.
Build a Test Environment
Never upgrade production first. Create a copy of the system and data, run the upgrade there, and have real users test real tasks. Include:
- Month-end close steps
- Payroll processing in a test run
- Pay application generation
- Vendor payment runs and bank file creation
- Key reports the controller and project managers rely on
Write down issues and decide which are blockers. Make sure the test environment is protected like production, since it holds real financial data.
Protect the Starting Point
Take a verified backup immediately before the upgrade, and confirm you can restore it. Keep that backup separate from your routine rotation so it is not overwritten. If the upgrade fails, this is your path back, and you do not want to discover problems with it at 2 a.m.
Also record current settings: user roles, security configuration, integration credentials, and scheduled jobs. Upgrades sometimes reset these.
Review Security During the Upgrade
An upgrade is a good moment to improve security, not only to move versions.
- Review the user list and remove accounts that are no longer needed
- Verify roles and segregation of duties, such as separating vendor setup from payment approval
- Move away from shared logins and default administrator accounts
- Confirm the database server is patched and not exposed to the internet
- Ensure remote access uses multifactor authentication
- Check that audit logging is turned on and retained
Plan the Cutover
Write a cutover plan with times, names, and steps. Include:
- A freeze period when no one enters data
- The sequence of steps and who performs each
- A verification checklist, such as trial balance tie-outs and open payables comparisons
- A rollback decision point, with a clear criterion for when to abandon the upgrade
- A communication plan for staff and key vendors
Run a rehearsal if you can. The first real run should not be the first run.
After the Upgrade
Do not declare victory on the first day. Watch for problems through at least one full payroll and one month-end close. Keep the old system or backup available, read-only if possible, until you are confident. Update documentation, including the network diagram and your recovery runbook, so the new version is reflected.
Collect feedback from users. Small friction points often point to missed configuration steps.
Common Mistakes
- Skipping the test environment to save time
- Upgrading right before a deadline
- Forgetting bank and payroll integrations
- No verified backup, or a backup nobody has restored
- Leaving old accounts and test users in the new system
Support When You Need It
Ironfield Cyber supports construction accounting platforms and the infrastructure behind them. We can help plan testing, backups, and security configuration around an upgrade so your finance team can focus on the numbers.