Implementing an entirely new ERP system can be like trying to "eat an elephant". With ERP user adoption you have to do it one bite at a time.
We almost always suggest a phased approach for our clients when we implement Microsoft Dynamics GP or Acumatica. Once people start to use the system, they understand the user interface and feel more comfortable, and then you can start to add new features. For example, accounting comes first, then add inventory.
However, a phased approach has to be done in a logical way.
Some software vendors, especially the ones that sell direct, will tell you to get started with just the core financials and "leave the rest until later," just so they can get their foot in the door. The reasoning is, "if we get them on this system now, they are less likely to keep it even if things get rough."
What they don't understand is that then they could be creating a disconnected environment. For example, the company could have General Ledger and Accounts Payable in one system, but the POS is still on the old system and not flowing into AP. It just doesn't make sense. You have to know which pieces fit together.
On the other hand, a phased approach does make sense if you are talking about adding new functionality. For example, if your company already has a separate CRM system, that can be put off until Phase 2.
You never want to take away functionality and make things more difficult for your users.
In other words, if they have an integrated CRM to their old system, you wouldn't want to put in the CRM system and leave the integration for Phase 2. You can't break what they already have.
The goal is to help your users see the value of the new system – one step at a time.
Get more tips on user adoption in the white paper, "
By CAL Business Solutions, Microsoft Dynamics GP and Acumatica Partner,