Accounting and job cost systems are the financial spine of a contractor or energy services company. When it is time to upgrade, whether to a newer version of the same product or to a different platform, the project tends to be driven by the software vendor's timeline. The business questions get settled late, usually under pressure. Settling them first makes the difference between a smooth cutover and a painful month-end.
Decide what is actually changing
Be precise about the type of change.
- Version upgrade: same product, newer release.
- Hosting change: moving from on-premises to a vendor-hosted or cloud arrangement.
- Platform change: moving to a different product.
Each carries different risks. A version upgrade may break customizations and reports. A hosting change affects performance, access and backups. A platform change touches everything, including how people work.
Questions about data
- What data comes with us? Decide how many years of history to migrate in detail versus summary balances. Detail increases cost and risk, while too little history can hurt audits, lien questions or warranty claims.
- Who validates the data? Assign someone from accounting, not only IT, to reconcile balances, open items and job cost totals before and after.
- What happens to the old system? Plan to keep read-only access for a defined period, and understand the licensing and storage that requires.
- Where is the clean-up? Duplicate vendors, inactive jobs and old cost codes migrate happily unless you remove them first. Use the move as a reason to tidy.
Questions about access and security
An upgrade is a chance to reset permissions that have drifted for years.
- Who needs which roles in the new system? Rebuild roles by job function rather than copying old ones.
- Which accounts belong to former employees or shared logins? Retire them before migration.
- Will multi-factor authentication be enforced, especially for remote access and any hosted environment?
- Who holds administrator rights, including the vendor and any consultants?
- How will the vendor's own access to your data be controlled and logged?
Segregation of duties deserves attention too. The person who sets up vendors should not also approve payments, and changes to vendor bank details should require independent verification.
Questions about integrations
Contractors rarely run accounting alone. List every connection.
- Project management and document platforms
- Payroll and time capture
- Bank files for payments and positive pay
- Equipment and fuel systems
- Reporting tools and spreadsheets that pull from the database
- Estimating software
For each, find out whether the integration will still work, who owns it and how it will be tested. Spreadsheets with direct database connections are an especially common casualty because nobody remembers they exist.
Questions about testing and cutover
Test with real scenarios
Run a parallel test using a copy of production data. Process a payroll, a pay application, a vendor payment batch and a month-end close in the test environment. Have the people who normally do those tasks perform them. Their questions will find gaps that a technical checklist will not.
Time the cutover carefully
Avoid month-end, quarter-end, year-end and payroll deadlines. Agree on a freeze period for entries and confirm who communicates it to project managers and field staff.
Plan the rollback
Decide in advance what conditions would cause you to go back and how. Keep a verified, restorable backup of the old system taken immediately before cutover. A rollback plan never used is cheap insurance.
Questions about people and cost
- Who will train users, and in what format? Field staff who only touch time entry need different training than controllers.
- What internal time will the project require from accounting? It is usually more than expected.
- What are the ongoing costs, including support, licenses, hosting and add-ons?
- Which vendor commitments are in the contract and which are verbal?
A simple readiness checklist
- Written scope and decision on history to migrate.
- Named business owner and data validator.
- Cleaned vendor, job and cost code lists.
- Role and permission design approved.
- Integration inventory with owners.
- Test plan covering payroll, billing, payments and close.
- Cutover date outside critical deadlines.
- Backup and rollback plan verified.
- Training scheduled before go-live.
Working with a partner
Ironfield Cyber supports contractors and energy companies through software changes, from permissions design to backup and cutover planning. If an upgrade is on your calendar, we can review your plan with you and flag security and continuity gaps before they become go-live problems.