Mistakes to avoid during NetSuite implementation
Introducing new business processes can prove challenging for any organization. Here are some common mistakes to avoid to ensure your NetSuite implementation is a big success.
When you are making a major transition from legacy systems to a cloud-based platform there are many ways that the migration could fail. Here are examples of mistakes some businesses make, along with advice to ensure your NetSuite implementation is a success.
To help you out on your implementation journey download our Checklist for Success: Anderson Frank NetSuite Implementation Checklist
Choosing the wrong NetSuite implementation partner.
The industry your company works in needs be taken into consideration when you choose the partner to work with to implement a NetSuite system.
You need someone who has experience working with a company like yours. Different partners will have experience in different industries. NetSuite implementation in a manufacturing and distribution company will be different to a business services organization.
Don’t be afraid to ask for references, either. Speak directly with other companies that have worked with the partner and find out first-hand how their transition went. This will confirm that you have chosen the best partner for your business.
Not performing a thorough data cleanse before starting the migration.
Think about your current systems. Are they perfectly in order? Do you have old data that needs to be archived? Any workarounds that everyone has got used to that should have been cleaned up years ago? Loads of data lying around in the wrong places that there you’ve never had time to go back and sort out?
You must have everything cleaned up, mended and archived before you even think about migrating data from old legacy systems to your shiny new system.
If you don’t clean everything, all the issues that you have now will travel across to the new system. Except, it could be worse! All the handy workarounds you have been using suddenly won’t work.
Often, after a new system implementation, people will blame the system for not working properly and long for the old one back. One common reason for this is the data that was migrated wasn’t cleaned effectively.
Not spending time with your NetSuite implementation partner to document your current business needs and mapping out the future.
It’s understandable to want to move straight on to the new system that you were first shown when you chose your solution, but immediately wanting all the positive changes the new platform brings without a plan will have you heading for potential issues.
This is one of the biggest mistakes companies make when starting a business process migration.
If you race ahead, only touching on how your business processes are performed now, you will feel the pain and increased cost later, when something that was missed has to be added into your system build at a later stage.
Without really examining what you currently do, there’s a chance that you’ll just replicate the systems that your company is currently using, potentially missing out on new interesting process opportunities within the NetSuite platform that will make your business run better. Take the time to understand, and get to know, the NetSuite platform, and all of its capabilities.
NetSuite software can offer your business systems that support not only finance but HR, payroll, CRM, inventory, supply chain, manufacturing, marketing, and e-commerce.
Take time before you start the NetSuite implementation to plan for the future, and see what your business will need then. As your company grows, NetSuite will grow with you. You need to make sure your organization has thought about what it has in its business plan for the next five, or even ten, years.
Ask for help from your NetSuite partner. They know what the software system can do and what it offers to an organization. You may not want or need every feature that is available but be sure you understand what’s possible before you commit to the project.
Ignoring what the current system is actually being used for by your staff and missing important business needs.
When deciding on the outline of the system requirements make sure that everyone who actually uses the system is invited to discuss what they use the current legacy systems for in their day to day work.
It’s amazing how many businesses will implement a new system based on what the management team ‘think’ the current systems are used for. Ask what each user needs, as it may be a surprise what is actually happening inside the business, rightly or wrongly.
Not creating a test account in a NetSuite sandbox and spending time exploring or testing the system.
Your employees that will be using NetSuite every day need to have an opportunity to explore and use the system in a safe environment. A NetSuite sandbox offers you that opportunity.
A sandbox is an isolated test account with your real business data included in it. Any changes, mistakes or problems are contained safely away from your real live system. Your users will be able to learn what the new platform can do, as well as how they will use it to complete their daily duties.
Having access to a NetSuite Sandbox is an additional cost on top of your implementation. But not checking the system out thoroughly could cost you a lot more in the long term.
Users need to be given time away from their work to have an opportunity to be involved in the NetSuite implementation process. Including your employees at this stage will mean they have an understanding of the system. It also allows the opportunity for them to ask questions and offer input into the implementation. This will produce two positive outcomes:
- Your users will be familiar with the system when it goes live, cutting down the resistance to change that can occur with most new system launches.
- They will find hidden flaws and missing actions early in the implementation, saving the business future costs by getting mistakes corrected before launch.
Ignoring the need for access to a NetSuite implementation team or not employing experienced NetSuite professionals.
Implementation of a NetSuite system isn’t a single activity that you don’t need to think about once it’s in place. Unfortunately, it’s not that simple. Your company is going to need at least one person who understands NetSuite and is able to look after and develop your system in the future. If you’re a larger company then you may need a whole team. You’ll need an experienced NetSuite Administrator either full-time or to build a relationship with a contractor who will keep your NetSuite system ticking over perfectly.
In the future, as your company grows, you will want changes made to the system and then you will need access to a NetSuite Developer to create new or improve current, processes. A NetSuite Consultant or Business Analyst is essential for helping your company plan and use NetSuite to its full potential.
Offering the minimum amount of training.
It may sound obvious, but you must spend time and money training your staff thoroughly to use the new system. If you don’t, it won’t take long for old processes to re-emerge because they are more comfortable for the users. Look out for the sneaky use of those old Excel spreadsheets!
NetSuite is designed to offer straightforward user interactivity but everything feels difficult if you have only been shown something for an hour.
Having your teams actively engage and welcome a new system is unlikely to happen instantly, but good training and support will help the transition happen much more smoothly.
Deciding to move your business into the cloud and implement NetSuite isn’t something that any business does lightly. So, don’t head into your NetSuite implementation process with failure just over the horizon. Being careful and not making these mistakes will go a long way to limiting problems and ensuring your implementation project is a complete success.
Download a Checklist for Success: Anderson Frank NetSuite Implementation Checklist