
Duplicate records and poor data quality can reveal more than a messy database. They can expose gaps in the way a business works. Ben Langley, founder and CEO of Suite Generation, talks to Joanna England about why process mapping and data cleaning belong together, and what businesses can improve before moving to a new ERP.
Part 4 of 5 in the series Phase zero – before you implement.
This interview has been edited and condensed for clarity.
Poor data quality: key takeaways
- Document existing processes before deciding how a new ERP should support them. A business analyst can do this work.
- Reviewing the data checks what people describe and can reveal exceptions they forgot to mention.
- Poor data quality, such as a duplicate customer record, can point to a weakness in the process that created it.
- A new system does not fix poor data quality on its own, so process improvement and data cleaning belong side by side.
Why start by documenting existing processes?
Ben: You need to understand what the business actually does before deciding how a new system should support it. A business analyst can speak to the people doing the work and document the steps they follow.
That gives managers something concrete to review. Often, it reveals activities that people elsewhere in the organisation did not know were happening.
It also creates an opportunity to improve things before the ERP implementation begins. Some processes have accumulated over the years without being questioned. Writing them down lets you see where the unnecessary work might be.
Can you rely on people to describe everything accurately?
Ben: People know a great deal about their jobs, but they can forget things. They may describe the work they do every day and leave out an exception that only appears occasionally.
That does not mean they are being unhelpful. They might be busy, or a particular situation simply does not come to mind during the conversation.
This is where reviewing the data becomes valuable. It gives you another way to understand what has been happening. You can compare the process someone describes with the records that process has produced and investigate anything that does not make sense.
What might poor data quality reveal?
Ben: Take a simple example: two customer records with slightly different names. You ask whether they represent the same customer, and it turns out they do.
The next question is why there are two. Perhaps someone could not find the original record and created another one.
Now you have discovered more than a duplicate. You have found a weakness in the way customer records are created or located. If you only clean up the records, you have dealt with the result. You also need to understand the process that allowed the problem to happen.
The customer example is simple, but the principle applies more widely: information can expose an exception or a weakness that a process conversation has missed along the way.
How can poor data quality affect business decisions?
Ben: If activity for one customer is split between two records, your reporting may not show the full relationship. You might look at each record separately and miss how important that customer is to the business.
Bringing the information together could change your understanding of which customers are most profitable and where you should focus attention.
That is why data cleaning has value beyond preparing an import file. It can reveal something useful about the business you are running today. The quality of the records affects what you can see and, in turn, the decisions you make.
Won’t the new ERP sort out those problems?
Ben: Moving to another system does not automatically make the underlying information better. If the data is poor, the new system still has to work with it.
You may also find that the information does not fit the processes you want to introduce. NetSuite expects data to support structured processes. It is different from working in a spreadsheet, where people can move information around to make something work.
That is why I put process improvement and data cleaning alongside each other. They are separate activities, but each helps you understand what needs attention in the other.
What can a business improve before it changes systems?
Ben: Once you understand the existing process, you can look at whether all the steps and systems are necessary. You may be able to simplify parts of the technology stack or reduce manual effort while still using the software you already have.
That does not remove the need for an ERP if the business needs one. It means you approach the change with a clearer view of what should be carried forward and what can be improved beforehand.
It also makes the requirements conversation more precise. You can explain how the business works, including the exceptions, instead of expecting the implementation team to discover everything after the project has started.
Frequently asked questions
Not automatically. Data quality issues move across with the data: if the records are poor, the new system still has to work with them, and the information may not fit the structured processes you want to introduce.
A gap in the process can cause them. For example, someone may create a second customer record because they could not find the original. Cleaning up the duplicate deals with the result; the weakness in how records are created or located also needs fixing.
Cleaning the records deals with the result; understanding the process deals with the cause. Process improvement and data cleaning are separate activities that each show what needs attention in the other.
If one customer’s activity is split across two records, reporting may not show the full relationship, which can change your view of which customers are most profitable and where to focus.
Related reading
- Before you buy an ERP: Ben Langley on getting the business ready
- Your ERP team already has a day job: how to plan the workload
- Outsourced customer master data management
- GOV.UK: The Government Data Quality Framework
About Ben Langley
Ben Langley is a NetSuite consultant and the founder and CEO of Suite Generation – 30+ implementations, multiple OneWorld accounts, and over 200 automations built inside NetSuite. Follow him on LinkedIn for more thought leadership on ERPs and NetSuite.
Author

Joanna England is Marketing & Growth Operations Lead at Suite Generation and an award-winning tech and business journalist with more than 25 years' experience. A former Editor-in-Chief of Insurtech Insights, Fintech Magazine and Insurtech Digital, she was named one of MPVR's Top 30 Journalists in Fintech & Insurtech in 2023.
Follow us on LinkedIn
New NetSuite field notes, UK pricing guidance and implementation practice, as we publish them.
