My NAV/LS Nav database is too customized
. Customizations should have little to nothing to do with upgrading if it is done correctly, and with the right tools. Your customizations will come forward into your new NAV/LS Nav version.
My NAV/LS Nav database is too large. Though the size of a NAV/LS Nav database does lead to certain challenges, we have successfully upgraded databases that are over a Terabyte in size. Our arsenal of tools to aid in data migration recently reduced a 42-day data migration to approximately four hours.
It’s better to do upgrades by hand instead of using upgrade tools. A well-executed upgrade for NAV/LS Nav should be largely automated and rely as much as possible on the Microsoft-supplied upgrade tools. It is impossible for a developer to review millions of lines of code by hand and hope that human error and fatigue doesn’t play a major factor in the resulting upgrade.
I use kitting extensively, and it’s not available in the new versions. While certain applications, like kitting, have been removed, there are new ways to handle the business functionality. Assemblies are the new way of doing kitting, and we’ve upgraded many companies who use kitting to assemblies without difficulties.
Any NAV/LS Nav Developer can do upgrades. This is probably the single biggest reason that many NAV/LS Nav upgrades take too long, cost too much, are never completed, or result in serious post go-live issues. Upgrades are different from other development projects in nearly every way. The requirements, methodology, tools, and the professionals who plan and execute them should be tailored to the single goal of a successful upgrade. Our upgrade team has over 10 years of experience in doing upgrades. We are upgrade specialists.