Microsoft Dynamics NAV (Archived)

Changing NAV Partners and License Argument

(0) Share

Report

Posted on by Community Member

Hi, we are interested in changing NAV Partner

We are using NAV 2009 R2 and NAV 2015 (new)

In 2009 with have customization.

My questions are:

1) Can we purchase BREP from the old partner and halfway switch to the new partner without incuring any costs?

2) Upon switching to the new partner, does the customization belongs to us or to the old partner? Would the new partner be able to inherit the customization or need to develop new ones?

3) Can we forget about 2009 and start afresh in 2015?

Much appreicated

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

Community Member on at

Like (0)

Report

Hi,

1) You can purchase the BREP from old or new partner. That is not an issue at all.

2) Customization remains in your database. Hence no need to develop the same again. However new partner might take some time to go through the existing customizations, if it is complex.

3) You can easily go with fresh 2015, provided you are already using and satisfied with it and do not need any customizations from existing NAV 2009 version.

Hope this helps.

Was this reply helpful? Yes No
mmv 11,471 on at

Like (0)

Report

Hi,

In addition, you need to upgrade to the NAV 2015 license.

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (1)

Report

1) You can technically purchase the BREP from old partner, but when you switch to a new partner you would require support from a new partner, but he will not have any BREP revenue from you until next year :-). From the other hand, the old partner would have BREP revenue and has a right not to support you anymore if you switch to a new one. There is no sharing halfway BREP procedure in Microsoft. So it is rather a question to new partner if he wants to support you without BREP payment. To me, it would be more honest to transfer to new partner and pay BREP to him.

2). Normally the customization belongs to both parties, however it depends on your agreement and type of the license for the customization. Usually it is so that you are able to use the customization, but not able to sell it to others. Also, theoretically, customizations might be located in such a range of objects that only old partner can have development access to that. Better check with a new partner that he is having access to those.

3). It depends on the types of the customizations and efforts and budgets you had invested in the project of NAV 2009. If you had used role-tailored interface and RDLC reports, you can as well use those in a new project. If you had used classic interface, a lot still needs to be done. Sometimes it is easy to start from scratch and reinvent all the processes. Sometimes the feature you had customized is already presented as a standard functionality in a newer version. But usually there is something valuable in the old database that you can take with you to a new one. Analyze the list of customizations with a new partner and decide.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Alexander, appreciate your prompt reply. Assuming the new partner does not have access to the old partner customization, what can we do? Are customization FOB objects that can be opened by anyone with a developer's license?

Was this reply helpful? Yes No
Suggested answer

Miguel Llorca Gómez 7,019 User Group Leader on at

Like (1)

Report

Of course, all the code is "in" your database. With a developer license you can view and edit them (unless if you are talking about a certified add-on). The big issue is that in most cases, the code is not well commented, etc.

If you are thinking about moving to NAV 2016, my recommendation is to make a full review of your processes, and try to maximice the use of the standard functionality :-)

Good luck!

Was this reply helpful? Yes No
Verified answer

Alexander Ermakov 28,096 on at

Like (1)

Report

In worst case, there might be a situation when the old partner had registered a special add-on in Microsoft in a certain range of objects, which might be unaccessible with the standard developer's license of a new partner. Technically it can be resolved in four ways:

- either yor new partner is performing attack on the code of old partner and tries to renumber the objects into accessible range (not always legal :-) )

- either you have good relationships with old partner and he assists in this transition period

- either you write an official letter to Microsoft claiming that you had paid your old partner and now you want to have access to that developments (it depends on your contract model)

- skip this functionality and develop a new one with a new partner

From my own experience, we had successfully went through all of that cases, so all are possible :-).

Was this reply helpful? Yes No
Gabor Faludi 302 on at

Like (1)

Report

Typically the addon ranges are the issues. That would be the thing that ties you to X or Y partner. Lack of documentation will add cost to the bill .

g.

Was this reply helpful? Yes No