Well, the best way to do this is to use a single version in LimeLM. Because you want the customers to all use the same key whether they're on 1.x or 2.x.
Does that make sense?
Query about migrating licensed users.
srinivasHello,
So the scenario is something like this:1. We have an application and we are planning to release it with different versions, lets consider version 1.0 and 2.0 over a gap of some months.2. So, in our dashboard we have created 2 versions for our app, both having a different .dat file and guid.
So, our client buys the license L1 for version 1.0. Some months later, we roll out version 2.0, and we want this same user with licence key L1 to be able to use our app without hassle. But since the guid and .dat file that will be rolled out with the new app will be different is there a way to migrate this user to the newer version without anything extra needed from the client side? In general, we should be able to migrate all our old licensed users to the newer version.
Please let me know how we can achieve this asap. It would be of great help!
Regards,Srinivas
srinivasHello,
Ok. But, what about the import keys option that is available in every version ? Isn't it for importing old licensed users?
I don't know what you're asking. Are you asking about the import product keys functionality? That's only about importing data from dead, defunct, poorly designed, or in-house licensing products. It's not about moving data around inside LimeLM.
If you want to use a product key for multiple versions of your app, then you don't need to import or export data. Just create a single version in LimeLM and use the product keys for both versions of your app. The version name doesn't matter.