Sage 100

According to slides from yesterday's ( 2/19/2025 ) Quarterly Partner Webcast - Sage 100 2025 is expected in April 2025 while the first 2025 product update is listed as August 2025 which is a change the type prior years when the first product update would typically be released in June (Update: It looks like PU1 had been releasing in July most recently although at one point June was the target release date for PU1).

Now, you might ask yourself, Wayne ... who cares? And why is this a big deal? 

Well, Sage is now issuing practically no standalone bug fixes ( yea, yea - I know you got one for the last issue and it was super easy to get and you downloaded it without talking to anyone. I'm sure exceptions apply but can we agree the pace of download availability in the Sage Download KB is very slow and sparse )...

So here's why I believe it's a big deal.

A customer who installs 2025 in April 2025 now has to wait until August to get the first product update (which have morphed into mostly patches and fixes ).

Yes, I know that I can call Sage and they will fax me a legal waiver sheet to sign and I can get a pre-release fix. I've got a number of problems and concerns with that - the first being that I shouldn't be signing ( waiving my customer's rights ) away liability for a patch. The second being that these patches should be listed in the download KB so we don't have to be calling Sage to ask if they know about an issue and have a fix.

I didn't make the call yesterday so If I'm misinterpreting the slide deck in some way - in the words of SNL 50 legend Gilda Radner / Emily Litella - "never mind" ..

PS - There seem to be a lot of new (different) names on the presenters list from the call yesterday. Possibly the sign of continued shuffling of duties in the mid-market.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------

Ugh, @Wayne Schulz - that's a bummer to hear.  For clients who aren't super small and super generic, I usually wait for the .1 to come out, so that's now pushing those upgrades into the fall when things start picking up from everyone realizing if they want to spend it in this budget year, they need to get cracking.

I agree with you both. And to top it off, if we decide to wait to upgrade a client until PU1 comes out, and they have 3rd party enhancements, then we have to wait for the developer to have their product updated. (We all know some are quicker than others).

It could be 2026 before we can upgrade some clients to version 2025.

If the Sage 100 team shifts to two releases per year (major release and one minor), then they're officially doing exactly what they did for Sage CRM. It had 4-6 releases per year, and has since consolidated to two with a similar schedule (Feb/Mar for 20xx PU 1 and Aug/Sep for a 20xx PU 2).

I'm curious to see how the ISV community adapts to this. There have been some that seem to struggle to get add-on products ready for a new release within 6-9 months of a product release. Does this mean that those ISVs will support 2025 PU1 right before 2026 PU 1 drops? :-/ Sounds like a bad time for customers that need the major release in August but have add-ons from ISVs that won't have a fix ready for months afterward.