In 2005, Advent released the first version of Advent Portfolio Exchange (APX). This paved the way for enterprise users to take Advent more seriously, while reassuring rapidly growing firms that APX would service their future needs and provide support for legacy requirements. Initially, this change was fine with many of the Axys users that have historically comprised Advent’s established userbase, but after years of baseline Axys updates and Advent’s predominant emphasis on APX, the patience of some Axys users has worn thin.
Today Axys users likely fit into one of four camps:
- They are planning to move to APX in the near future.
- They understand their options well enough, but don’t think the benefits of moving to APX outweigh the costs.
- They simply don’t care about APX or competing products – just as long as Axys keeps doing what they need, everything is fine.
- They are frustrated by Advent’s perceived abandonment of their business segment and are either actively seeking a replacement to Axys or in the process of converting to a new system.
I have repeatedly been told that owning a self-hosted version of APX is 2-3 times more expensive than Axys, but don’t take my word for it. Advent’s pricing changes regularly. Call Advent and get a quote. Early on, APX conversions were very expensive, and some firms were quoted six-figure conversion costs. Although these costs have been reduced substantially, APX is still significantly more expensive than Axys.
In the past, conversions were much more complex and time-consuming. The primary issue seemed to be the normalization of a wide variety of Axys data. As APX has evolved, Advent and the conversion utility within APX have created efficiencies in the conversion process. In a recent conversation with a client, who is now considering the move from Axys to APX, I learned that Advent took copies of their Axys files and was able to demo APX 4.x with representative data from their firm in about a week.
In addition to the difference in the software cost, Advent recommends that APX users host the app in a traditional database server and application server configuration. Some users may opt to host IIS on a separate server as well. Currently, many small and medium businesses (SMBs) simply host Axys on their primary file server.
Why would a firm running Axys want to pay the premium for APX?
The answer is improved security, infrastructure, and functionality that meets the expectations of those with higher technological standards – historically enterprise users, not SMBs. APX promised this from day one, but APX v1 was, well, version 1. I sat in on a couple dog and pony shows for APX when it was first introduced. In one, the presenter abruptly but politely disconnected a conference call with one of their early “testimonial” users when the conversation went in an unexpected direction. At Advent’s conference in Orlando, more time than Advent would have liked was spent on the topic of APX latency, but these types of issues can be experienced with any v1 product covering as much ground as APX.
One of the most valuable benefits of Advent’s portfolio accounting systems is the maturity of their products. This maturity is the primary reason why so many things in Axys and APX work the way they should. Though much has changed at the core of Axys and APX, both of these systems can potentially run a report created on The Professional Portfolio (the precursor to Axys and APX) 25 years ago. Due to the continuity of Advent’s portfolio management systems, users of The Professional Portfolio and Axys have been able to jump into APX without a lot of training.
Last year, when I attended the Advent conference in Boston, a panelist from the Advent Users Group touched upon the issue of APX owners using APX like Axys. Her point was that you should use the newer features of APX v3, but as she mentioned it, I couldn’t help thinking how much the earlier versions of APX were like Axys. Aside from the SQL backend and other related platform benefits, it felt like you were still using Axys, only it was more complicated and clunky.
Even now, we see that the heart of Axys continues to beat inside APX, playing a critical role with respect to backward compatibility and legacy reporting. Over the course of its first five years, APX has matured significantly. That initial awkward period is behind Advent APX.
In the past 18 months, Advent has made significant strides towards fulfilling the promise of APX, introducing additional SSRS reports in APX 3.x and the ability to create dashboards in APX 4.x. I have finally heard mention of an API. Yes, APX is more complex than Axys, but now that more of the infrastructure has been built out, you can feel better about it. With these improvements, APX should make sense for a larger number of investment firms.
APX is a logical upgrade for Axys clients who:
- Want to minimize the need to retrain staff on a new portfolio accounting system.
- Understand that additional features, such as SSRS reporting and dashboards, come hand in hand with incremental complexity and the costs of an enterprise solution.
Those that don’t want to take on as much overhead may find solace in moving to APX on Demand (a SAAS offering), but in doing so they will have to sacrifice some of the flexibility and functionality available to self-hosted users of APX.
Final Score: APX 4, Axys 0
Looking at version releases of APX and Axys over the past seven years, it is easy to understand the focus of Advent’s primary resources. Though four minor releases of Axys have been made since APX came out, there have been no major releases. A major release implies a major change to the software, and at this point it doesn’t appear that a major Axys release is coming from Advent.
Last year’s acquisition of Black Diamond provides Axys users with another choice under the Advent umbrella, but I haven’t seen many users go from Axys to Black Diamond. While Axys improvements have stalled out, Advent’s full-throttle APX development has many of its Axys users feeling disenfranchised. From my own perspective, Advent appears to be losing some valuable clients through a failure to more actively communicate with their SMB client base.
If Advent wants to keep Axys clients as Advent clients, they should connect with their users and reassure them that they want to work with them. Still, Advent should also understand that for some, it may make more sense to move on.
About the Author: Kevin Shea is President of InfoSystems Integrated, Inc. (ISI); ISI provides a wide variety of outsourced IT solutions to investment advisors nationwide. For details, please visit isitc.com or contact Kevin Shea via phone at 617-720-3400 x202 or e-mail at kshea@isitc.com.
A couple weeks ago, I was sitting with some clients, discussing the merits of moving to 3.8.5 now or early next year. I let them know that Advent would likely announce a sunset of 3.5.1 and 3.6 later this year. They were still using Axys 3.6 and knew they needed to eventually move to Axys 3.8.5 to stay current. In our meeting, we reviewed the benefits of making the move, which included the various report updates, as well as compatibility updates for Adobe Acrobat 10, Office 2010, Windows 7, and Windows Server 2008. They decided to upgrade to Axys 3.8.5 immediately.
