mibuso.com

Can some one share how you resolve license issues if client want's to change Dynamics NAV partner, but he have some solutions which is developed in add on object range?

There are no license issues; the customer keeps the current license. If he can still use the solution made by the previous partner is a legal issue between the previous partner and the customer. If the solution is MS registered as a granule then the new partner won't be able to change the objects in question.

It depends. Either the old partner has a "developer" granule of his certified AddOn then the new partner could modify and support that AddOn (if the two partners find an agreement) or the certified AddOn has to be supported by the old partner while anything else will be supported by the new partner.

Then if the client, for example, want's to migrate from 5.0 version to 2009, then the migration can do only the old partner or the new one needs to have old partners developers license.

It's not so simple - as einsTeIn.NET wrote it depends: what modifications were made, where, how, what object ID region was used, are there "real" add-ons in use,... And again let's not forget the legal issue - contract terms, NDA's,...

If you have individual modifications in the certified AddOn then maybe yes. Or your new partner finds an agreement with the old one about a partner's granule of that AddOn.

Good point!

You see it's not an easy decision if it makes sense to switch to another partner. You have to consider many different things and be sure in what you exactly want to do and why.

If a partner has developed a locked add on that only they can work with and then sold it directly to you as their customer, then it would appear that they did that just to keep you as a customer. Partners like this are companies that you should never work with. Partners should retain customers because the customers are satisfied with their services, not because of black mailing techniques.

Talk with your current partner and if they are unable to come to a resolution where the new partner can access the objects, then you need to dump them anyway. You should in this case work out how to get the functionality migrated to a new object range.

I recommend getting a mediator in these cases. This should not be between a customer and a partner.

I've done some of these projects as a mediator, sometimes leading to a partner switch, somtimes to fixing the relationship.