Options

Doubt Data Migration from Nav 5.0 W1 to Nav 2009 R2

victor73victor73 Member Posts: 55
Hello,
this is the first time that we are migrating a customer from Nav 5 W1 SQL to Nav 2009 R2 SQL, we've been doing it for versions before Nav 5, I have a big DOUBT: reading the Upgrade toolkit manual I read the following:
"Moving from Microsoft Dynamics NAV 5.0 to Microsoft Dynamics NAV
2009
It is not necessary to perform a data upgrade to move from Microsoft Dynamics NAV
5.0 to Microsoft Dynamics NAV 2009
. To take advantage of the RoleTailored client in
Microsoft Dynamics NAV 2009, you must carry out an object upgrade from Microsoft
Dynamics NAV 5.0 SP1. You can follow some of the steps that are described in this
manual to perform an object upgrade. See Upgrading from Microsoft Dynamics NAV
5.0 to Microsoft Dynamics NAV 2009 Quick Guide for a list of the steps"

So This means that I don't have to performa any upgrade but simply convert the NAV 5 sql DB with the new NAV 2009 R2 Client???

I will appreciate your help
Thanks

Comments

  • Options
    postsauravpostsaurav Member Posts: 708
    Hi,

    The upgrade can be of two types as far as i know -
    1) Only Executable Upgrade (.exe).
    2) Object Upgrade.

    So This means that I don't have to performa any upgrade but simply convert the NAV 5 sql DB with the new NAV 2009 R2 Client???

    To answer your question, if you will open your Navision 5 Database into 2009 or Later version that will be just executable upgrade.
    You will not be able to use features from new version as for example there is a system indicator in Navision R2 which you will not find if you process the above steps.

    You can get all latest features when you will do a complete upgrade that is object upgrade, which mainly consist of bringing down the customization on your database to the newer version. As you specified that for NAV 5 you are using SQL Database that SQL migration step is not required.

    But the steps left are object upgrade, and data migration. Let me know if you require anything else.

    Thanks & Regards,
    Saurav Dhyani
    http://saurav-nav.blogspot.in/

    Thanks & Regards,
    Saurav Dhyani

    Do you Know this About NAV?


    Connect - Twitter | Facebook | Google + | YouTube

    Follow - Blog | Facebook Page | Google + Page
  • Options
    victor73victor73 Member Posts: 55
    Maybe I made a mistake making the question...
    When the Upgrade toolkit says: "It is not necessary to perform a data upgrade to move from Microsoft Dynamics NAV
    5.0 to Microsoft Dynamics NAV 2009"
    My question is: the data migration isn't really necessary?

    Note: I've already done the object migration using the developer toolkit , what I have to do know is the Data Migration
    When migrating from previous versions (as 3.60, 3.70, 4.03) you must use a migration data tool via two fobs that must be installed (Upgrade4002009.1.fob in first part then Upgrade4002009.2.fob in the last part), what I understood is that such tool isn't necessary when migrating data from nav 5.00...is that correct?

    Thanks
  • Options
    mohana_cse06mohana_cse06 Member Posts: 5,503
    Yes, data upgradation FOB's are not needed while upgrading from 5.0 to 6.0..
  • Options
    victor73victor73 Member Posts: 55
    Thanks a lot, so I understood correctly?
    So the steps to follow as reported on Microsoft upgrade quick guide are:


    Action Prepare for the data conversion
    1. Make a copy of the database on which you will perform the conversion.
    2. Verify that both your solution developer’s license file and customer’s license file have been upgraded to Microsoft Dynamics® NAV 2009.
    3. If the database has roles and permissions set up, then create a superuser with a blank password if one is not provided. Log in as the superuser when you perform the upgrade.
    4. Make a backup of the entire database before you start.
    5. Test the database for everything except table/field relationships.
    6. Test the database for table/field relationships.
    7. Compile all objects and resolve what to do with those objects that do not compile.
    8. Install Microsoft Dynamics NAV 2009 and start the Classic client.
    2. . Upgrade C/SIDE® on Microsoft® SQL Server® if you are upgrading an SQL database.
    If necessary, upgrade to SQL Server 2005 or SQL Server 2008.
    Convert your existing SQL database in Microsoft Dynamics NAV 2009 with the Classic client.

    3 Open the old customized data with the Microsoft Dynamics NAV 2009 Classic client.
    Create a new database in Microsoft Dynamics NAV 2009 that is twice the size of your old database.
    Restore the backup of the old customized database into the new database.

    Alternatively, you can open a copy of the existing database with the Classic client, convert the database, and expand it to be twice the size of the old database.
    4. Delete all objects except tables.
    Delete all forms, reports, dataports and codeunits from the database but NOT the tables.
    5. Import the new customized objects that you created in the compare and merge process.
    In the Import Worksheet window, click Replace All, and then click OK
    .
    6. Compile all objects in the new database.
    7. For each company, initialize the company in the upgraded database.
    Run codeunit 2, Company-Initialize.
    Close the company and open it again.
    Open form 531, Setup Checklist, to update the checklist for the Microsoft Dynamics NAV 2009 data structure.
    8. Upgrade data common to all companies.
    Upgrade Security Roles and Permissions
    Upgrade Database Key Groups


    Is that right?

    Thank you for your support
  • Options
    mohana_cse06mohana_cse06 Member Posts: 5,503
    If these are given in Microsoft Upgrade Qucik Guide then they are correct..
  • Options
    victor73victor73 Member Posts: 55
    Thanks I will follow such document
    Bye
  • Options
    David_SingletonDavid_Singleton Member Posts: 5,479
    This is very interesting information. I know that MS did say many years back that an upgrade form 5.00 to 2009 would be a "code only" upgrade, but somehow I just assumed that a data upgrade would also be necessary.

    Firstly thanks Victor and Mohana for this thread.

    Next I would like to ask how far this data compatibility goes. For example at the local level is it possible to do an object only upgrade from 5.00 US to 2009 R2 US. Did all countries follow this rule.
    David Singleton
  • Options
    kinekine Member Posts: 12,562
    E.g. in Czech Rep. depends on if customer was using EastPack in version 5, because it is part of the DB in version 2009, but was not part of the NAV 5 when released in CZE. It means there could be additional "migration", depends on functionality used (but it is same situation, like when customer in older version have functionality, which is replaced by standard functionality in new version).
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    ChowdaryChowdary Member Posts: 148
    Thanks for the post
    Pleasure in the job puts perfection in the work
Sign In or Register to comment.