Remove huge production add on from NAV2009R2

thomast
thomast Member Posts: 102
edited 2014-02-27 in NAV Three Tier
Hi all you clever people,

How should I go about removing a huge production add-on from NAV2009? Its a production add-on with more than 300 custom tables and modifications to more than 250 standard nav tables. It even has its own BOM structure - basically it boycuts the entire manufacturing functionality in std. NAV.

My customer has used this module for a year but wants it removed but I am very concerned about overwriting the entire database with standard NAV2009 objects! For example, this module (which I do not know very well myself) could have created data all kinds of places in NAV and If I force std. objects into it, I'm afraid of being haunted by strange errors for the next couple of years.

What do you think? Is it possible to remove such an add-on or would a reimplementation be better?

Thanks!!!

Thomas.

Comments

  • tinoruijs
    tinoruijs Member Posts: 1,226
    Removing such big add-on seems impossible to me.
    Reimplementation for sure.
    You have to go through all processes at the customer site and see how standard NAV has a fit or a gap.
    Tino Ruijs
    Microsoft Dynamics NAV specialist
  • davmac1
    davmac1 Member Posts: 1,283
    I agree.
    You could look at this as a migration, and take the opportunity to move them to the current release if they are going with standard.
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • JohnHunter
    JohnHunter Member Posts: 45
    I agree too, fresh and clean, what can be better
  • jglathe
    jglathe Member Posts: 639
    Hi,

    I have done such a transplantation once. What you do is salvage all transactions without the item-related part. You also throw away all fields that you don't want to keep. Basically you create a new (preferably tested) codebase, and a cutting toolkit. Set up - cut - backup - import into new codebase.

    with best regards

    Jens
  • Rob_Hansen
    Rob_Hansen Member Posts: 296
    Holy crap - 300 custom tables? That's a massive add-on! The amount of time to deal with all the data issues (including custom fields in all the modified base tables) could be a nightmare. I'd approach this one as a reimplementation on base NAV myself.
    Rob Hansen
    http://www.epimatic.com
  • thomast
    thomast Member Posts: 102
    Thank you so much guys!!! Re-implementation it is!

Categories