Can a managed package be converted to unmanaged package by the vendor? If it is possible, how can it be done?


The package components would need to be moved to a different org (easy to do if they are already under version control as they should be) and a new unmanaged package definition created there.

But note that the unmanaged package components would not have a namespace so it would be hard to change an existing installation that used the managed package into one that used the unmanaged package.

  • An interesting thing to notice is that a managed package can coexist with the same packaged, unmanaged. Don't ask me how or why, but this happened once. We found some funny bugs because of this in our project (because of namespace issues). :D – Renato Oliveira Jan 15 '18 at 13:08
  • Thanks @RenatoOliveira. Cant the vendor make the same installed managed package unmanaged ? – Jaguar Jan 15 '18 at 13:14
  • Thanks @Keith C. We are discussing a possibility of what if our managed package vendor shuts goes out of business. What would be the ideal way to handle such case ? if provided we entirely work in their managed package. – Jaguar Jan 15 '18 at 13:14
  • @Jaguar What happens if they go out of business is indeed a good question to which I haven't seen a good answer. – Keith C Jan 15 '18 at 13:37
  • 1
    Pretty sure a vendor can make a separate unmanaged version of their package in the same packaging org where the managed version exists - so the result would be similar to salesforce.stackexchange.com/users/18269/renato-oliveira answer but you could just install as a unmanaged package. But you'd likely hit all sorts of namespace issues with fields being called the same thing minus the namespace, which can break dynamic SOQL etc, so you'd want to remove the managed version rather than have them co-exist – BritishBoyinDC Jan 15 '18 at 14:55

Not the answer you're looking for? Browse other questions tagged or ask your own question.