Great information, thanks for the insight. We have heard (and read) that making the production org the APO can cause significant debilitating issues with the Lead objects. Can anyone speak from experience or offer best practices here?
Here are some articles on the subject:
LMA Guide: https://developer.salesforce.com/docs/atlas.en-us.workbook_lma.meta/workbook_lma/lma_overview.htm?language=en
specifically these pages:
Installing the LMA:
Before you install the LMA, you need to decide which organization is your License Management Organization (LMO). Because the LMA is an integral part of the sales, billing, and marketing of a managed package, putting the LMA in the wrong organization makes it difficult to manage licenses as a part of the sales and marketing process.
Integrating with Sales and Marketing:
Do not create workflow rules, triggers, or validation rules that required custom fields on the license or lead objects. Do not impose any conditions on updating or creating license or lead records. Doing so will block creation of the license or lead records by the LMA, resulting in the loss of data concerning the packages installed by your customers.
Avoid mandatory fields
Don't define before-create triggers or validation rules on lead
Is there a trigger on the lead or license object in the LMO? If so, Remove it
Is there a required custom field on the lead or license record? If so, Remove it
Is there a validation rule on the lead or license record? If so, Remove it
Is there a workflow rule on lead or licenses? If so, Remove it