Upgrading Sage Estimating is rarely difficult in itself. What makes an upgrade stressful is doing it at the wrong moment, or discovering on bid day that a report or an integration no longer behaves the way the team expects. A little planning keeps the upgrade a non-event, which is exactly what an estimating department wants it to be.
This isn’t a guide to any particular release. Each version has its own release notes and system requirements, and those should always be your starting point. What follows is the general approach we have found works well for preconstruction teams of any size.
Pick the window before anything else
The single most important decision is when. Look at the bid calendar for the next couple of months and find a stretch with no major submissions. For many contractors that means avoiding the end of a quarter, the weeks before a large public bid, or seasonal peaks in their market.
Once you have a window, protect it. Let project executives and estimators know the dates well in advance so nobody schedules a pricing push in the middle of the changeover.
Take stock of what you rely on
Before installing anything, make a list of everything that touches your estimating environment. It is usually longer than people expect:
- The databases in use, including any older or regional ones still referenced
- Custom reports and report layouts your team prints or exports
- Spreadsheet views, estimate templates and user preferences
- Connected tools, such as eTakeoff Bridge for takeoff quantities, and any links to accounting or project management systems
- Workstation and server specifications, operating systems and database server versions
Check each item against the system requirements for the new version. Where there is a connected product, confirm the supported combination of versions with Sage or your business partner before you commit to a date.
Test on a copy, not on the live database
We always recommend a full backup first, followed by a test upgrade on a copy of your database. Ideally this happens on a separate machine or test environment so the production system stays untouched while you evaluate.
Then open a handful of real estimates in the upgraded copy — ideally a mix of recent bids from different types of work — and compare them with the originals:
- Do the totals match, including markups and add-ons?
- Do assemblies calculate the same quantities from the same inputs?
- Do your custom reports run and produce the same numbers and layout?
- Do exports and integrations send data where they should?
- Can your estimators find the tools and views they use every day?
Any differences are far easier to investigate at this stage, when nothing is riding on the answer. Keep notes on what you find so the rollout plan can address it.
Plan the rollout to people, not just machines
An upgrade is also a change to how people work, even if the change is small. A few things help the first week go smoothly:
- Brief the team. A short walkthrough of anything that looks or behaves differently saves a lot of interrupted work later.
- Name a go-to person. Estimators should know who to ask when something looks off, rather than working around it quietly.
- Upgrade workstations together. In a multi-user environment, having some people on the old version and some on the new one invites confusion. Plan to move everyone at once where you can.
- Keep the backup accessible. Retain the pre-upgrade backup until the team has comfortably completed a few bids on the new version.
What to do with estimates in progress
If an estimate is mid-flight when the upgrade window arrives, talk with the lead estimator before deciding. Sometimes it makes sense to finish and submit that bid first; sometimes the estimate can move over cleanly and continue. The right answer depends on the deadline and how much is riding on the bid, and it’s worth making that call deliberately rather than by default.
After the upgrade
Once the team is working normally, take a few minutes to close the loop. Update your internal notes on the environment, record the version and date, and note anything you would do differently next time. That short record makes the next upgrade noticeably easier, especially if different people are involved.
Upgrades go best when they are treated as a small project with an owner, a date and a checklist. If you’re planning one and would like help thinking through the timing or testing, we’re glad to lend a hand.