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 2013, then this method is no longer useable. Or is it?
What is the best practice for upgrading from NAV 2009 R2 to NAV 2013 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?
You are right about the NAV 2013 changes to the versions, but to get around this can the Mergetool now export with Code conversion to and from NAV 2013. With this “pre-processing” of the NAV 2013 source code can merges be done without additional merges based on the changes for NAV 2013 source code.
How do I set this “pre-processing”? I saw it as part of the Export (with or without NAV7 Code Conversion) - but isn’t there any way to do it without exporting and importing again? Is there any way to run the Code Conversion on a version already imported?
Could you please help me in how to use Mergetool in migration project of Nav2013 to Nav2013 Rollup 13. Could you n please send me the detailed step how to use mergetool. Please Help Nilesh