Before You Replace Lawson V10, Part 1: You Might Not Actually Need a New ERP
Why Most Customers Looking at New ERPs Are Solving the Wrong Problem
After hundreds of implementations, the conversations with V10 customers all start the same way now. A CIO who has been running Lawson for twenty plus years calls and tells me they’re starting to vet replacement vendors. They’ve already booked demos with Workday or Oracle, and sometimes the budget conversation is already underway.
When I ask why, the answer almost always traces back to the same handful of reasons. Sometimes it’s that they want something new. Sometimes the 2030 sunset is weighing on them. And sometimes they figure that if they’re going to do the work anyway, they may as well evaluate everything on the market.
For most of these customers, that line of thinking leads to a much bigger and more expensive project than the one they actually need. The next version of the system they already have is sitting right there, and it was built specifically to carry forward what their team already knows how to do. Before anyone goes to market for a new ERP, it’s worth asking whether they’re solving the right problem.
What Customers Are Really Telling Me When They Want to Replace V10
The same CIO who is now telling me they want to look at Workday is also the CIO who has been working hard to extend Lawson all the way out to 2030. Year after year they pay for support, train new staff on the platform, and invest in a system they say they want to leave behind. What that pattern tells me is that they actually like Lawson. They like how their team uses it. They appreciate the way it handles the workflows their business depends on. And it does what it needs to do without a lot of drama. The 2030 deadline gave them a forcing function, and now they’re confusing “I have to make a decision” with “I have to make a different decision.”
If you genuinely disliked the platform, you would have moved off of it already. The fact that you held on this long is the data point that matters most.
The Difference Between an Upgrade and a Replacement
Most of the V10 customers I talk to assume that moving to CloudSuite FSM takes roughly the same lift as implementing a brand new ERP from a different vendor. Same scope. Same timeline. Same training burden. Same change management headache. If you start from that assumption, comparing FSM against Workday or Oracle does start to make sense, because the cost of switching to either really does look identical.
That assumption is wrong, and it changes the whole calculation.
Moving from V10 to CloudSuite FSM is a version upgrade, which means the bones carry forward and the data model stays the same. Workflows your team already knows continue to work the way they expect them to. The chart of accounts you have spent years refining does not have to be rebuilt from scratch, and the reports you depend on do not have to be reinvented. Your end users walk into the new system and recognize most of what they see, because the underlying logic is the same logic they have been working with for years.
What you get on top of that foundation is a modern platform with capabilities that did not exist when V10 was originally designed. The timeline to get there is dramatically shorter than a net new implementation, and the change management lift on your end users is a fraction of what a full replatform would require.
I like to call it a mini implementation. You get the chance to take advantage of new technology, redesign processes that have not aged well, and clean up workarounds that have accumulated over the years. All of it happens on top of a system your team already knows.
Coming Next
Some CIOs will still want to evaluate other systems before they commit to any direction, and for some organizations that exercise is worth doing. If that’s the road you’re going down, the next question is a real one. What should you actually be looking for in that evaluation, and what are you letting dazzle you into the wrong decision? Part 2 of this series gets into exactly that.