I have a managed package that is being actively developed in an Individual Developer Edition org. It has been installed and is in use in a couple of customer orgs already.
I would now like to move towards an app exchange listing. Via the ISV Partner Program Partner Portal I can generate a Partner Developer Edition org.
The Partner Developer Edition org seems like a better place to actively develop the managed package. It will be tied in with the Partner Portal and the CRM ISV Organization (Business Org) that will have the License Management App (LMA) installed.
Should I try and transition the managed package development into the Partner Developer Edition org?
Is this even possible, or will I lose the current namespace prefix and need to start a new managed package?
Starting a new managed package would be a pain as the existing customers would need to be migrated to the separate managed package.
Maybe the best I can do is link the existing Developer Edition org to the AppExchange Publishing Organization (APO) org.
From Partner Development & Test Environments:
Can I upgrade my existing DE org to Partner Developer Edition?
No, Partner Developer Edition is a brand new 20-user DE org. If you want to migrate your work from DE to Partner Developer Edition, you will need to use the Force.com IDE or Packaging. acceptance of our agreement, which outlines these orgs are NOT for production use.