To Upgrade or to Re-implement Dynamics NAV? That is the Question | BDO Connections 2016
2 likes695 views
The document discusses the differences between upgrading and re-implementing Microsoft Dynamics NAV. Upgrading involves moving historical data and existing customizations to a new NAV version, while re-implementation only moves master and opening balance data and requires redeveloping customizations. The document outlines key factors to consider for each approach, such as the version upgrade path, database size, customizations, budget, and timelines. It then describes the methodologies for performing an upgrade, which includes code, report, and data upgrades followed by testing, or a hybrid approach combining elements of both upgrade and re-implementation.
Ad
More Related Content
What's hot (20)
Similar to To Upgrade or to Re-implement Dynamics NAV? That is the Question | BDO Connections 2016 (20)
Ad
More from BDO IT Solutions (20)
Ad
Recently uploaded (20)
![Download Wondershare Filmora Crack [2025] With Latest](https://cdn.slidesharecdn.com/ss_thumbnails/neo4j-howkgsareshapingthefutureofgenerativeaiatawssummitlondonapril2024-240426125209-2d9db05d-250419-250428115407-a04afffa-thumbnail.jpg?width=560&fit=bounds)
To Upgrade or to Re-implement Dynamics NAV? That is the Question | BDO Connections 2016
- 1. To Upgrade or to Re-implement Dynamics NAV Presented by: Abhishek Agnihotri
- 2. Agenda • When is the right time to review current product and qualify for upgrade/re-implementation • Difference between upgrade and re-implementation • Key factors to be taken in to consideration • Understand the upgrade methodology • Understand the re-implementation methodology • Hybrid approach • Q &A
- 3. Time to review/think • You are currently using older version of Microsoft Dynamics NAV. • Your current NAV version is no longer supported by Microsoft. • Your current NAV version is no longer compatible with the latest Operating System or the latest software's. • You have reviewed the Microsoft Dynamics NAV 2016, you are impressed with the new functionality, user friendly interface and would like to take advantage of the new product. • The BIG QUESTION – How do I get there?
- 4. To Upgrade or to Re-implement Dynamics NAV Difference between upgrade and re-implementation
- 5. To Upgrade or to Re-implement Dynamics NAV Upgrade • You will get all historical data with already developed customizations from older NAV version in the new NAV version. • Upgrade is faster and less expensive than re- implementation unless the database carries heavy customizations that are outdated, poorly designed or replaced by standard functionality in the newer version. Re-implementation • After re-implementation, you will have only master data and opening balances. • The customization from older version need to be re- developed/moved from scratch in the new version.
- 6. To Upgrade or to Re-implement Dynamics NAV Upgrade • During an upgrade, if the customer is using any standard functionality in older version which is now dropped in newer version, that needs to be analyzed and if required need to re-developed in the new version. This could have some cost implications. • Upgrading can be simple and fast when performed by specialists with the relevant upgrade experience Re-implementation • Re-implementation requires more customer engagement, but the solution is more flexible. • Re-implementation can also be simple and less time consuming knowing the fact that you were already using older version of NAV and well versed with the product capabilities and your business.
- 7. To Upgrade or to Re-implement Dynamics NAV Key factors to be taken in to consideration Before making any decisions, you should take in to consideration the following factors: • System Upgrade Path – What is the version of the source system and is there a clear upgrade path to the target version (new version) available? • Database Size and Quality – How big is the database and how good is its quality? Do you need to purge or archive historical data? • Customizations & New functionality – Is the database heavily customized, Do you need all those customizations in the newer version? OR Would you like to benefit from new standard functionality instead of upgrading the old customizations?
- 8. To Upgrade or to Re-implement Dynamics NAV Key factors to be taken in to consideration • ISV Solutions – Are there any ISV solutions in your current system? Is the ISV solution available in the new version? What is the upgrade path to the new version with the ISV solution. • Integration with third party application – Are there any integrations with third party applications? Are the third party application compatible with the new version? • Budget – Does your budget allows you to invest in the new version?
- 9. To Upgrade or to Re-implement Dynamics NAV Key factors to be taken in to consideration • Timeline & downtime limitation for a cutover – How long will it take to get you to the new version? If you plan to upgrade what is the downtime limitation for a cutover. The bigger the database the longer the downtime during the Go Live. Question: How long will it take to do the data conversion from NAV 4.0 to NAV 2016 on a 50GB database with moderate customizations? a) 0 – 8 Hours b) 8 – 16 Hours c) 16 – 24 Hours d) 24 – 32 hours e) 32 – 40 Hours f) 40 – 48 Hours
- 10. To Upgrade or to Re-implement Dynamics NAV Key factors to be taken in to consideration In order to do the data conversion and upgrade from version NAV4.0 to NAV 2016, we need to fist upgrade to NAV2009 and then to NAV 2013 and finally to NAV 2016. Each version upgrade involves multiple steps and upgrade procedures that need to be run at specific times . Also to facilitate the data conversion we need to create 2 intermediate databases with the current customized schema for NAV 2009 and NAV 2013. • Resources – In order to get to the new version, you may have to buy additional servers, new compatible software's. This may involve your IT Person/ IT Vendor etc. Also you have to allocate resources to the new project for Analysis, testing, validation and Go Live.
- 11. To Upgrade or to Re-implement Dynamics NAV Upgrade methodology
- 12. To Upgrade or to Re-implement Dynamics NAV Upgrade methodology • Requirement & verification workshop – To define the project’s scope, timeline and planning • Project kick-off – Identify each party’s role, assign resources etc. • Code Upgrade – Done by your partner; involves code comparison/merging, re-implementing functionality. • RTC Upgrade – Done by your partner; Upgrading Forms to Pages, Report upgrades to the RDLC layout, Dataports transformation to XMLports, Designing Role Centres.
- 13. To Upgrade or to Re-implement Dynamics NAV
- 14. To Upgrade or to Re-implement Dynamics NAV Upgrade methodology • Data Upgrade – Done by partner; following the standard Microsoft data upgrade tool or extending the tool for custom data upgrade. If ISV solution is involved follow the upgrade guidelines provided by the ISV. • Unit Testing – Done by the partner. Involves compilation testing, data upgrade testing and basic functional testing • Full Functional Testing – Done by end user; involves full fledged functional testing, key reports and third party integration testing if any. • Go Live – Both end user and partner is involved in the process. Partner will perform a fresh data upgrade from the latest cut- over backup file. End user going to test the upgraded data, Install the new client, Check the security etc.
- 15. To Upgrade or to Re-implement Dynamics NAV Re-implementation methodology
- 16. To Upgrade or to Re-implement Dynamics NAV Re-implementation methodology • In a re-implementation project once the requirements are collected and gap-fit analysis is performed the end users will be busy with the verification workshops where they define the scope and plan the project. • The projects will be split in smaller tasks and the responsibilities are defined. • The major role of partner in a re-implementation project is redesigning and developing customizations. Master data and opening balances import. Partner will perform the Unit testing and delivers the customizations for functional testing. Partner will do the end-user training.
- 17. To Upgrade or to Re-implement Dynamics NAV Re-implementation methodology • Once the user training and user acceptance testing, is finished the partner will help the end user for the Go Live and support them in resolving any issues that comes up during the process.
- 18. To Upgrade or to Re-implement Dynamics NAV Hybrid Methodology • Hybrid approach is a combination of upgrade and re- implementation methodology. • This methodology is adopted if you are several versions behind the latest NAV Version • This methodology gives you an opportunity to review your existing customizations, ISV solutions and decide if you want to move all your old customizations to new version. You have the flexibility to drop an existing customization or ISV solution. • All the history data will be moved using standard and custom upgrade procedures.
- 19. To Upgrade or to Re-implement Dynamics NAV Hybrid Methodology • In todays fast paced changing environment most of the companies are adopting this approach. • This approach can become complex especially in a highly customized environment and you need highly experienced and trained professional to perform the task. • The data conversion might be very time consuming especially with larger database. To accommodate the data conversion you need to have good storage space on the server as the data conversion involves multiple steps and backup needs to be taken at each critical step.
- 20. Questions? Abhishek Agnihotri Senior NAV Consultant [email protected]