Firstly, it is important to understand the unique needs of your organization and make the right choice based on that. With 19 go-lives in 2023, our experience shows that most companies choose from three scenarios: a full upgrade, a light upgrade, or a reimplementation.
What considerations should you make in this process? What are the pros and cons? You can read about it in this blog.
Full upgrade
A full upgrade involves transferring both the standard functions and the custom applications and configurations from your current Dynamics NAV system to the Business Central Cloud. This scenario is ideal for companies that wish to retain their existing data and customizations while benefiting from the improvements in the cloud.
What are the benefits?
With a full upgrade, you retain all crucial business data, resulting in a seamless transition and a short learning curve for existing users. This reduces the risk of business disruptions and provides flexibility in planning the go-live date.
What are the challenges?
However, with a full upgrade, there is a risk of transferring unnecessary legacy features (functions that are outdated or obsolete but still linked to a specific workflow) and 'contaminated' data to your new system. We recommend conducting a thorough data analysis and cleanup prior to the migration.
Light upgrade
In a light upgrade, you migrate only the standard NAV tables and data to Business Central, with the option to include certain custom fields and configurations. This scenario focuses on retaining essential functionalities while eliminating unnecessary custom elements. A key aspect of this approach is the preservation of the history of the standard data, allowing you to continue using and analyzing important historical information in the new system.
What are the benefits?
A light upgrade simplifies the system architecture and can lead to cost savings. It offers the ability to selectively migrate custom data, resulting in a cleaner and more streamlined database.
What are the challenges?
This approach may result in the partial loss of custom features, and users may need to adapt to a new way of working for certain processes. Additional user training and support can be helpful in this transition.
Reimplementation
Reimplementation involves setting up an entirely new Business Central Cloud environment from scratch, migrating only the most essential data. This scenario is suitable for companies looking to completely modernize their processes and make a fresh start with the latest technology.
What are the benefits?
Reimplementation provides the opportunity to scrutinize and improve existing business processes, starting with clean data. This leads to a more efficient and streamlined system.
What are the challenges?
The biggest drawback is the potential loss of historical data. Although a backup of historical data can be made, it will not be loaded into the new system. Additionally, this approach involves change management: you must be willing to invest in user training and give your team time to adapt to the new system.
The world of Microsoft Dynamics: Key Considerations
When deciding on the future of your systems, several crucial factors need to be considered:
Amount of customizations
The extent of customizations within your current system is a key factor. A full upgrade is often suitable for environments with standard functionalities or minimal customization. On the other hand, reimplementation is better suited for systems with extensive customizations that have significantly altered business processes.
Relevance of existing customization
Evaluate how essential your current customization is for operational efficiency. If your current setup aligns well with your evolving business processes, an upgrade may be sufficient. However, if your customization no longer fits your current business needs, reimplementation may offer more advantages.
Importance of existing data
It's crucial to retain important data. A full upgrade facilitates smoother data migration, while reimplementation provides the opportunity to start with a clean slate.
Accuracy of existing data
Examine the quality of your current data: are they accurate and regularly cleaned? Reimplementation offers the chance to clean up data, whereas a full upgrade requires a well-planned strategy for data cleaning and migration.
Transition timeline
The time available for the transition is crucial. An upgrade is generally faster than reimplementation, which requires more planning, data restructuring, and testing phases.
Conclusion
For adapting your ERP system, it is essential to start with the specific needs of your organization. The choice between an upgrade or reimplementation will then depend on factors such as the relevance of existing customization, the importance of existing data, and the time you can allocate for the transition.
Whatever approach you choose, the goal remains the same: to advance your organization with technology that aligns perfectly with your current and future business objectives. A well-considered decision will smooth the transition and lay a strong foundation for your organization's growth and efficiency.
Would you like advice on the approach that suits your company? Our experts at NORRIQ are ready to help.