Before You Replace Lawson V10, Part 3: What If You Didn’t Like V10 to Begin With?

The first two parts of this series were aimed at customers who like Lawson but think the 2030 deadline forces them to leave. There is a different group I want to talk to in this one, and these are the customers whose minds were made up years ago. They had a rough V10 experience and have been waiting for a reason to leave, and the 2030 deadline finally gave them one. When someone mentions CloudSuite FSM, their immediate reaction is some version of “why would I move to a newer version of the system I already disliked?”

I understand the instinct. After hundreds of implementations though, I can tell you that the things customers blame on Lawson are usually about something other than Lawson. They got attached to the platform along the way, and unless you diagnose what they actually were, switching vendors won’t fix any of it. You will carry the same dynamics into the new system and find yourself frustrated all over again about eighteen months in.

Where Most V10 Complaints Actually Come From

When I sit down with a customer who tells me they’re done with V10, the conversation usually goes one of four directions, and almost none of them lead back to the platform itself.

The first is configuration that nobody has touched since the original go-live. The PO matching tolerances were set during implementation by a consultant who didn’t fully understand the business, and no one has touched them since. The security classes were drawn up in a hurry to get the system live, and no one has reviewed them in years. The chart of accounts has had segments bolted on every time the business changed, with no one going back to clean up the structure underneath. That kind of damage doesn’t get fixed by changing platforms, because the same configuration patterns would create the same headaches in any ERP on the market.

The second is institutional knowledge that walked out the door. The people who knew how V10 was set up at your organization left over the years, and the people who replaced them inherited a system without an instruction manual. They are working around things they don’t understand because no one is left to explain why those things exist. Documentation and continuity gaps travel with you, and replacing the platform while the same gap exists is just a recipe for repeating them.

The third is hidden functionality that has been there the entire time. I have worked with V10 customers who don’t know the Excel Add-In exists. I have worked with customers who never set up departmental security and end up giving every user the same access to data they shouldn’t all be seeing. I have worked with customers whose end users can’t see forms that would solve their problems because someone never updated the security class. They feel limited by the system, but those limitations are self-imposed. The capabilities are there in the system already, and someone just needs to turn them on.

The fourth is implementation that was never actually finished. Maybe the original project ran out of budget. Maybe the consultant disappeared after go-live. Maybe the team ran out of bandwidth to come back and complete the second wave of optimization that was always planned. The system has been carrying that unfinished business for years, and every workaround that got built to compensate has become permanent infrastructure.

Before you decide V10 is the problem, it’s worth being honest about which of these four buckets your real frustrations actually fall into.

What CloudSuite Actually Changes, and What It Doesn’t

CloudSuite FSM is genuinely different from V10 in ways that matter. The interface is modern and far less code-driven, and new users navigate it without the steep learning curve V10 demanded. FSM finally has a real mobile experience that V10 never delivered. The reporting tools are stronger out of the box and don’t require the same dependence on third party tools. SaaS delivery means the constant cycle of server upgrades and patches becomes someone else’s problem. For customers whose complaints fall into the platform-limitation category, FSM addresses them in a meaningful way.

Frustrations about how your system was set up don’t disappear when you change vendors. Neither do frustrations about who is left to support it or what your team knows how to do with it. They move with you into whatever platform you choose next. The vendor on the contract changes, but the dynamics underneath stay the same.

Diagnose First, Decide Second

The right question to ask before any V10 evaluation is what actually went wrong, and whether the next system is going to fix it. Most customers skip straight to the vendor comparison without doing that diagnosis, and they end up with the same problems and a different logo on the contract.

At GForce Technology Consulting, we have helped a lot of organizations work through this exact question. Our consultants have lived in both the legacy Lawson world and the modern CloudSuite world, and they can tell you whether the issues you’re experiencing are platform issues or something else entirely. Sometimes the answer is yes, it’s time to move on. Sometimes the answer is that the system has been quietly capable of solving your problem all along, and nobody ever showed you how.