Upgrade NAV 2009R2 to 2017 - Data Migration

Nelson2017Nelson2017 Member Posts: 8
edited 2017-08-24 in NAV Three Tier
Hi all,

i am doing an upgrade from NAV 2009R2 over 2015 to 2017. What is the right way for the data migration process? I want to merge the application objects only once with 2017. So i am not able to run the upgrade toolkit in 2015, because i won´t have application objects for 2015. Can i run the second step of data migration direct in 2017 (with the upgrade objects for 2013 or 2015) or is it possible to run step 2 in the 2015 database without the merged objects?

Thank you in advance!

Answers

  • davmac1davmac1 Member Posts: 1,283
    unless you want to heavily modify the 2015 upgrade objects, your best way is to add the custom fields only to the demo database and use that set of objects for the 2015 step 2. You only need your custom data to come over. Then have all your changes you are keeping merged into the NAV 2017 objects.
  • Nelson2017Nelson2017 Member Posts: 8
    edited 2017-08-24
    Could you give me a short explanation of the single steps and the right order?

    I did the following steps:
    1. Import and run Upgrade toolkit objects step 1 from 2015 in 2009r2.
    2. Delete all Objects except tables (did the upgrade toolkit by itself)
    3. Open and convert Database in 2015, Schema Synchronisation
    4. Open and convert Databse in 2017, Schema Synchronisation

    The custom fields are still in the tables of the converted database.

    EDIT:
    Oh, now i see what you mean: I should add the custom fields to an empty 2015 database, export all objects from that database and import it into my converted 2015 database. Now, i can run the data migration part 2, am i right?
  • mohana_cse06mohana_cse06 Member Posts: 5,503
    Yes, you need to create 2015 final fob to import in converted db
Sign In or Register to comment.