Hello, i’m still very new in MBS-Navision. May i know how to migrate from Navision version 3.70 AP to Navision version 4.00 AP. Thank You
Hi, The upgrade toolkit 4.0 is a comprehensive tool to help you do upgrades from 2.6 or 3.x to 4.0. You can find it on MBS PartnerSource. It contains documentation, upgrade path, and several tools to make the upgrade process easier. Also, because Navision 4.0 was released recently, you’ll have to make sure you use the LATEST version of Navision and the latest upgrade toolkit (there was a critical update released 2 weeks ago). In general, we recommend to do upgrades only if you an experienced developer and certified in Navision, but you can give a look…
Navision 4.0 Upgrade Toolkit: https://mbs.microsoft.com/partnersource/products/navision/downloads/migrationtools/upgradetoolkit400.htm?printpage=false
Thanks David Godbout.
Migration is a tricky process, but since you hopefully will do it first in a test environment it might also be a healty exercise.
First thing you need the appropriate migration tool and a standard 4.00 database (Cronus db will do) - you should be able to find it in partnersource, if you don’t ask your NSC; if you are the NSC, ask Microsoft support.
If the 3.70 database has customizations that must be mantained in the new version, replicate them in the standard 4.00 database - there are many ways to do this - from reimplenting everything from scratchs to have them automatically reproduced by the compare-merge tool. As usual virtue lays in the middle. [:)]
Once the customized 4.00 version is completed and tested (as much as you can test it on a Cronus database), you may try the first migration, that, if anything, will porvide you with better data to test with. This will be just the first of many tries, but the process will be the same for the last and real one.
Let’s go:
-
export all the objects from the customized 4.00
-
make a complete backup (objects + data) of the original database
-
create an empty 4.00 database and restore the backup in it
-
in the MS migration tool you will find some fobs - find the fobs for migration from 370 to 400, step 1 - there might be one for WW and one for localized objects - refer to the tool documentation to see wich ones you need and in which sequence. The fobs contains codeunits and reports which prepare data to be transformed as needed by the new structure - you may have to write your own codeunit or report for customized data and add them to the tool
-
run the imported migration tool as descripted in the tool documentatio; errors might occur, you have to deal with them
-
remove all the objects but tables from the database
-
import the customized objects (see step 1)
-
compile everything and try to solve the compilation errors
-
import the fobsin the migration tool marked as step 2 - again you may have to add some objects of your own
-
run the step 2 following the instructions in the documentation
-
delete the tool objects - your database is converted
To better understand how the tool works and which additions you may need to make to it, you may try first to migrate a standard 3.60 into a standard 4.00 and look at the tool structure and code in the process
so … what the difference about WW and one for localized objects ??
Stan, exactly what do you mean? The question is here about the AP (Asian Pacific) version.
PS: Next time please don’t reply to a two year old thread. Instead create a new, eventually refer to the old. But this thread has already been marked as answered and therefor you cannot expect to get any answer.