By HTL 365 · · Updated
If you want to know how disciplined an accounting firm’s IT is, look at how they handle CCH ProSystem fx Engagement.
Engagement is a client-server application. The central file room lives on a server, staff take binders offline on their laptops, and everything has to stay in sync. Each upgrade touches the server, every workstation and every binder in between. A messy upgrade can cost audit teams days.
Why it’s a good test
Wolters Kluwer supports only recent versions of Engagement. A firm that falls a major version behind, with no plan to catch up, is running software that may no longer get fixes or support. It’s rarely a deliberate choice. Usually it means IT is reacting instead of planning.
A simple upgrade plan
- Check the system requirements early. New versions can require newer Windows, SQL Server or .NET versions on the server and workstations. Find out before upgrade week.
- Pick the window. Schedule around audit and tax deadlines, when the fewest people are working in binders.
- Get binders home. Ask staff to synchronize any binders they’ve taken offline before the server upgrade, so nothing gets stranded on an old version.
- Back up first. Take and test a backup of the Engagement server and file rooms before you start.
- Upgrade the server, then workstations. Push the workstation update to everyone in a set window so mixed versions don’t linger.
- Test with real binders. Have someone from audit, tax and advisory open, edit and sync a binder before you call it done.
Coordinate with every practice area
Audit lives in Engagement, but tax and advisory teams touch it too, along with the Microsoft 365 and document management tools around it. Tell everyone what’s changing, when, and who to call. That’s the difference between an upgrade nobody notices and a Monday morning of help desk tickets.
Our team has supported accounting firms through many Engagement upgrades. If yours keeps slipping, or keeps going badly, we can help you get on a predictable schedule.