Envestnet rolls back MoneyGuidePro upgrade after 19-day advisor backlash

Envestnet has pulled the new MoneyGuidePro and restored the legacy version for the thousands of firms that received the first phase of its 'generational release.' The rollback landed June 1, ending a 19-day stretch that RIABiz says frustrated advisors. The new version is withdrawn; the company says it could return later this month.

The Berwyn, Pa., firm kept the first wave small on purpose, a controlled rollout meant to surface problems quickly. Rose Palazzo, group president for Envestnet Financial Planning, told RIABiz by email that a small number of clients had issues, that those issues were resolved, and that the design was to fix problems in about a day. The accounts RIABiz collected from advisors describe a longer, rougher stretch. An editor's note alongside the article frames the episode as a case study in what happens when an industry built on trust becomes a software business releasing upgrades on shorter cycles.

Roger Whitney, principal of Agile Retirement Management, told RIABiz the system was slow and unstable; when clients did log in, the numbers did not make sense — materially different from what they had seen a day before the upgrade. His practice runs about $140 million across 94 households. A planning figure that will not hold overnight attacks the one thing a plan needs most: consistency.

For many RIA workflows, MoneyGuidePro is core planning software. The rollback therefore has a direct desk-level consequence: any plan built during the unstable stretch now carries an asterisk until a client reopens it and the numbers hold. The client may already have logged into a portal and seen a different projection than the one the advisor printed last week.

The 19-day gap matters because the failure appeared inside client portals, not only in the office. RIABiz's editor's note draws a parallel to the previous week's problems with Schwab's integration of TD Ameritrade accounts. In both cases, the issue is basic judgment about what clients are told while systems misbehave. The engineering gets fixed; the relationship damage takes longer.

Envestnet says the problems were small, resolved, and handled inside a controlled release. The advisors RIABiz consulted were less charitable, though the article also describes them as constructive and understanding of the pressures of software development. Their annoyance centered on silence and delay, not on the company's ambition or the code itself. The article does not say what changed internally during those 19 days or when the rollback decision was made.

RIABiz's account is specific about what bothered advisors most: zero communication and a slow response, more than any single software glitch. A broken calculator is understandable; silence while the calculator stays broken is what turns a software release into a client problem. The same distinction applies to any planning engine.

The price of a botched planning-engine release is not a support ticket; it is a meeting in which an advisor explains why a retirement projection changed overnight. Advisors in the first cohort bore that cost for nearly three weeks. Envestnet's controlled release likely kept the failure from reaching the whole installed base, which is a defense of the strategy, but the delay between detection and rollback is where the damage compounded.

For firms that run MoneyGuidePro as core planning infrastructure, the useful question to ask the vendor now concerns the next rollback, not the next launch. What triggers a stop, who gets informed, and on what schedule? Software will fail again. What clients see while it fails is the vendor's judgment in action. A firm that runs one planning engine should also know its fallback version, test it before any upgrade window, and confirm how fast it can switch back.

The episode argues for a low-tech habit inside the practice. If a client's plan lives in a software portal, export the key numbers before any major system upgrade and keep the date stamp. That gives an advisor a reference point when a vendor's new version starts showing different figures — and a record of what the client was told when. It is the kind of habit that looks unnecessary until a vendor recalls a release, and then it is the only number you trust.

Envestnet will likely get another chance with the generational release, possibly before the end of June. The clients who watched their figures shift without explanation will not study the patch notes. The advisor is the one left to explain it, and the explanation only holds if the next version keeps a single number from one meeting to the next.