Sage Abra Suite: Announcing the retirement of Sage Abra Suite

Sage is committed to providing the highest quality products and services to our customers. As a technology developer and provider, we understand that technology evolution allows our customers to establish and maintain competitive advantages and achieve operational efficiencies. We've recently undertaken a full review of our portfolio. As a result of this review, we have made the decision to retire the Sage Abra Suite product as of December 28, 2020. This decision will enable us to focus our time and resources differently to ensure we continue to deliver market leading solutions for our customers.

What does this mean for you?

With the retirement of Sage Abra Suite, Sage will no longer provide updates, security fixes, tax and legislative updates after the September 2020 release. Additionally, access to the support center for assistance will not be available as of December 28, 2020.

What do you need to do?

We understand this announcement will require a shift to a new system, as such we aim to facilitate your transition in the most seamless way possible. Please contact either a Sage business partner or Sage account manager for additional information.

  • Please correct me if I'm wrong, but this implies that current Abra Suite users will not be able to complete their year end process next year (2020).

    No updated tax reports, no ability to file W2 or ACA forms and no help from Sage, even though they've paid their maintenance.  Will Sage prorate the support for those that will not be migrating to HRMS?  With the 20% price increase for both the software and support, many are looking to alternative solutions that are more cost efficient.

    Anyone else have the same interpretation?  Does Sage have an answer for those customers that are asking?

  • I have no idea either.  We are looking at alternatives also - and we've been on the product for more than 20 years!  We have tried the SQL version (which is just FoxPro hooked into a SQL Server database) and it's bad - really bad!  Nothing but problems for out payroll department.  Support was unable to help also - so we reverted back to 9.2 (at least it was a known problem set we could work around).

  • Yikes, that sounds painful.  What version of the SQL version did you try?  Did you switch (and then switch back to 9.2 occur within the last three years?

  • Correction: Did your switch to HRMS (and then your switch back to 9.2) occur within the last three years?

  • To answer quickly...yes within the last 3 years.

    We followed the classic FoxPro track 7.x, 8.x, 9.x of Sage Abra Suite and have the Payroll and HR module.  We've built all kinds of custom front end code to import timesheets, gather GL data from Sage to drive our Accounting profit and loss system, etc, etc, etc.  It's 20+ years of stuff.  Not a big deal to convert all that to work with SQL, so we plunged forward with a migration. 

    It was a disaster - HRMS is 2 separate modules.  HR and Payroll are technically separate (not integrated like in Sage Abra Suite).  So if you update an employee in HR, you have to run a Sync command to update the Payroll module.  If you forget, you could pay people wrong.  The GL side of payroll was a mess too.

    It was no fun for anyone!  Sage Support was bad too!