It fails earlier, when the business waits too long to test the risks that could disrupt operations.
Being concerned about ERP migration is a sign you understand the stakes.
If something goes wrong during a migration, it doesn’t show up in a project status report, it shows up in real life - the branch, the yard, the counter, the delivery run. And ultimately, in a conversation with the customer who expected something to arrive.
That’s why the risk must be dealt with before you go-live, not discovered on the day.
We’re not here to tell you it’s all going to run 100% smoothly. But we are here to tell you it can be managed, and there’s a difference!
You can change the system. You can’t stop the business.
That’s the reality that shapes how migration needs to be planned. Not around a project timeline or go-live date but around the way your business runs day to day.
Data needs to be checked. Integrations need to be tested. Stock values need to be compared. Real processes need to be worked through before go-live, not the morning of, so the pressure points are found before they reach the people running the business.
That’s why operations should never be treated as just a workstream in an ERP project. If the process is unclear, the yard feels it. If the data is wrong, the counter feels it. If the handover breaks, the customer feels it.
Too many people judge ERP migration by the go-live date, and this is where many ERP migration conversations go wrong.
Of course, the date matters. Everyone needs to know when the business is moving. But a go-live date tells you when the system switches. It doesn’t tell you whether the business is ready.
A system can go live while your people using it still feel unsure. A process can look fine in a workshop and still feel clumsy on a busy morning.
Go-live isn’t the finish line. By then, the biggest operational questions should already have been found, challenged and worked through.
Our view is simple: no one should be asked to trust a process they’ve only seen in theory.
This is where we think ERP migration has to be more honest and why testing must follow the way orders moves through the business. The point is to find what could go wrong before go-live becomes the place you discover it.
Jordan Parker, one of our Migration & Implementation (M&I) Consultants, makes this point clearly. A single clean sales order doesn’t tell you enough. The real test is the messier scenario: the website order with a discount code, the service item, the payment integration, the receipt type, and the knock-on effect in accounts.
As Jordan puts it: “The whole point of this is that it’s not a tick box exercise.”
And if testing only proves the easy version of the process, it hasn’t gone far enough. The awkward scenarios need to be worked through while there’s still time to fix what doesn’t hold.
The same thing applies to data. Stephen Jackman, another of our M&I Consultants, brings the same thinking. In a good migration, you're not working with an empty system. The first data cut gives you something recognisable: your customers, your products, your suppliers, your pricing, your stock. Your team can look at a customer they know, a product they sell, a stock position they rely on - and ask better questions. Is this right? Will it hold up on a busy morning? Does it support the next person in the process?
By go-live, the major operational questions should’ve already been answered. Repeat testing gives you evidence that the processes have been tested before the customer feels the change.
That’s the point of doing migration properly. It brings risk forward, where it can still be seen, questioned and controlled.
Good testing reduces uncertainty. But confidence in a migration doesn't come from a test plan alone.
It comes from knowing that when the team needs reassurance, when the data needs another look, or a process doesn't feel quite right - someone is there.
For businesses that have been through a difficult migration before, that matters. A bad migration leaves people wary of the next one. It makes leaders question whether the business has the appetite, the time, or the internal confidence to go through it again.
When we think about ERP migration projects, we think of them as a working relationship that gives our customers confidence as the project moves along. In practical terms, this looks like: regular touchpoints, open conversations about data, questions answered as they appear, and a clear sense that someone is there to help the customer through the work.
During an ERP project, GenetiQ brings the migration, integration and implementation expertise. You bring the knowledge of how the business runs: the people, the branches, the workarounds, the exceptions, the data, the decisions.
A strong migration partner gives you enough structure, contact and challenge to bring the right risks into the open before go-live.
For operations leaders, that’s the difference!
If ERP migration is on your mind, the question to ask isn’t: “will this be risky?”
Of course it will involve risk. You’re changing the system your operation depends on.
The better question is: “when will we find the risk?”
Will it show up early, in testing, data reviews, process conversations and integration checks?
Or will it show up when the branch is open, the yard is busy, the team is under pressure and the customer is waiting?
That’s the difference between a migration that feels controlled and one that feels like a leap.
So, before you judge the project by its go-live date, ask what has been proven before that date arrives.
Have the messy scenarios been tested? Has the data been questioned? Have the integrations been checked? Have the people who understand the process been close enough to challenge what doesn’t feel right?
Because go-live should confirm readiness. It shouldn’t reveal the lack of it.
If ERP migration feels risky, start with the people who manage that risk every day. Speak to GenetiQ’s migration specialists about how to protect the way your business runs through the move.