Best practice for upgrading to NAV 2013 to nav 2018 with Mergetool (Code and database)

Elyes
Elyes Member Posts: 8
edited 2021-02-03 in NAV Three Tier
Hello,
Previously when I have been doing upgrades it has always been best practice to import both the old standard version, the old custom version and the new standard version into the same client, so that the text files you exported would have the exact same "layout".

But since we can no longer import old versions of FOB's into 2018, then this method is no longer useable. Or is it?

What is the best practice for upgrading from NAV 2013 to NAV 2018 using Mergetool? Not so much in terms of the steps to do (they are more or less as they have always been), but in terms of how to export the text files we need to import into Mergetool for the compare?
Thanks in advance

Answers

  • SanderDk
    SanderDk Member Posts: 507
    Why do you need MergeTool (It is a greate tool) but why not use the powershell Cmdlet?
    For help, do not use PM, use forum instead, perhaps other people have the same question, or better answers.
  • Elyes
    Elyes Member Posts: 8
    Hello
    I am a beginner in navision development!
    Do you have best practice for upgrading from NAV 2013 to 2018 (database and code)
    Thank you
  • SanderDk
    SanderDk Member Posts: 507
    The best practice is to follow the Microsoft guide:
    https://docs.microsoft.com/en-us/dynamics-nav/upgrading-to-microsoft-dynamics-nav
    For help, do not use PM, use forum instead, perhaps other people have the same question, or better answers.

Categories