Accounting and job cost platforms such as Sage and Viewpoint hold the financial heartbeat of a contractor: payroll, payables, billing, job cost, and equipment. Upgrading them, moving to a hosted version, or migrating to a different product is a major project. Done well, it improves security and efficiency. Done poorly, it can interrupt payroll, corrupt data, or leave old systems exposed.
This post provides a planning framework. It does not replace your vendor's documentation or implementation partner, who know the specifics of your version.
Start with the reason
Clarify why you are changing. Common drivers include a vendor ending support for your current version, a need for remote access, integration with project management tools, or security and compliance requirements. A clear objective helps you decide scope, timing, and success criteria.
Know your current environment
Document what exists before touching it.
- Software version, modules in use, and customizations.
- Database and server details.
- Integrations with payroll, banking, project management, and reporting tools.
- Custom reports, scripts, and macros that staff rely on.
- User accounts, roles, and permissions.
- Where backups are kept and how often they run.
Surprises during migration usually trace back to forgotten customizations and unofficial reports.
Back up first, and verify
Take complete backups of databases, configuration files, and attached documents before any change. Verify that you can restore them in a test environment. Store at least one copy offline or otherwise protected. Never begin an upgrade assuming the backup works.
Build a test environment
Run the upgrade or migration first on a copy of production data in an isolated environment. Use it to:
- Confirm the process completes without errors.
- Check that reports match expected totals.
- Test integrations, such as project management sync and bank files.
- Let key users, particularly payroll and accounts payable, try real workflows.
- Estimate how long the real cutover will take.
Keep test data protected. It is a copy of your real financial records and deserves similar security.
Plan access and permissions
Migrations are a chance to clean up. Do not simply copy every old permission. Review roles and apply least privilege.
- Remove accounts for former employees and unused logins.
- Eliminate shared accounts.
- Enforce multi-factor authentication where the new environment supports it.
- Separate duties for vendor setup, invoice entry, and payment approval.
- Limit administrative rights to a few named people.
Handle security of the new environment
If you are moving to a hosted or cloud model, ask:
- Where is data stored, and how is it encrypted?
- How is access authenticated, and can single sign-on or MFA be enforced?
- What backup and recovery guarantees exist, and how can you export your data?
- How are security incidents communicated?
- What are the terms for data return if you leave?
If you remain on servers you manage, harden them, patch them, and restrict network access to only what is necessary.
Schedule around the business calendar
Avoid cutover during payroll runs, month-end close, year-end, or critical billing periods. Pick a window that allows time for validation and rollback. Tell project managers and field supervisors what to expect, including any downtime.
Cutover day plan
- Confirm final backups.
- Freeze entries in the old system.
- Execute migration steps as rehearsed.
- Validate totals and key records against the old system.
- Test integrations and bank interfaces.
- Authorize users in stages, starting with a small group.
- Keep a rollback decision point with clear criteria.
After go-live
- Keep the old system in a protected, read-only state for a defined period for reference, then retire it securely.
- Disable old integrations and credentials.
- Monitor for errors and unusual activity during the first pay cycles and month-end.
- Train users on changes, including any new approval steps.
- Update documentation, including the integration map and backup procedures.
Retire the old system properly
Old servers often linger, unpatched and forgotten, holding sensitive data. Set a decommission date. Archive what is needed, wipe or destroy drives, cancel unused licenses, and remove the system from monitoring and inventory.
Common mistakes
- Skipping the test migration.
- Migrating all old permissions blindly.
- Overlooking integrations that depend on the old system.
- Performing the cutover during payroll week.
- Leaving the legacy system online indefinitely.
Support from Ironfield Cyber
Ironfield Cyber works alongside your software vendor or implementation partner to handle backups, environment hardening, access cleanup, and secure retirement of old systems. If you are planning a migration, we can help you add the security steps to the project plan.