Loading

Migrate License Management App to new License Management Organization FAQ

Publiceringsdatum: Dec 14, 2022
Beskrivning
The prerequisites are as follows:

1. The LMA must be installed in the new LMO:  Install the LMA
2. Review and provide a written statement that you acknowledge the following: LMA package is installed in the New LMO.



To move your LMO to a new org, please provide the following details:
 

Developer (Packaging) Org Details:-

Developer org Id:
Admin user Id (or username) that is requesting the migration: (Starts with 005)
Package Name: 
All Package Id: (Starts with 033 if you are able to locate it)
 

Old LMO Details:-

Existing LMO Id:
Admin user Id (or username) that is requesting the migration: (Starts with 005)


Target LMO (New LMO) Details:-

New LMO Id: 
Admin user Id (or username) that is requesting the migration: (Starts with 005)

 

Confirm you understand the following:


1. After LMO is confirmed migrated to your new org, you should install your package in a test org so the package record is created in your new LMO, then you must manually refresh the licenses. The package and license records do not automatically move to the new org.   

2. Do not upload any new versions until the migration is complete. You can upload a new version of the package once the migration is complete and distribute the new install link to your customers. When the customers install the package, new leads and licenses are created in the new LMO.

3. The LMA Migration focuses on moving all "Active" Production Org License Records to the new LMO. Sandbox Licenses will not migrate over. 

4. I have read the FAQ below and understand what happens after a LMA migration.
Lösning






FAQ:

1. Will we have to manage all renewals that are currently in the original org from the new org? Is it possible to keep some in the original LMO, and add new licenses to the new LMO? 

[A] Licenses can only live and work in one LMO, all renewals and licenses can only be managed from the New LMO once the migration is complete. 

2. How long will it take on your side to move the LMO? I know you said it depends on number of packages/versions - but can you give me an estimate of time per package/license/etc? 

[A]  The license refresh may take some to process due to unforeseen background jobs, maintenance patches and large loads on the instances. There is no ETA when it will be done but on average it takes 4 hours. Please open a new case if there is any issue.

3. In the past, we have had to request that Salesforce refreshes our licenses from your side - when clicking the button, because of the number of licenses per package, it has historically timed out. Is this something you suspect may happen again? About how long does the normal (button-click) process take vs the Salesforce job? 

[A] This is diffcult to determine.  We do not have statistics on the duration of the process. 

4. How do we get the new products into our COA? They currently live in a separate COA, but if we are going to sell, invoice, etc out of one org, we would like to enter all COA orders into our COA. 

[A] This is support by the Partner Operations Team. Please open a case in the partner community requesting assistance with the COA.

5. At what point does the AppExchange link for install push the licenses into our LMO? In other words, how do we time this switch over so that as customers are installing, we don't leave any licenses behind in the old org? 

[A] Once the LMO is migrated, new installs will push licenses into the new LMO. Even if some licenses went to the old org, refreshing will migrate them to the new org. 

6. Since the two companies likely share some common customers, we will likely be doing some account merging once all the products are serviced from the same LMO. As long as we relate the licenses to the merged account, there should be no LMA issues there, correct? 

[A] There should not be any issue.

7. Why are some licenses not migrated after refreshing the license?

[A] Licenses with the Org Status that is Deleted, Hold, Suspended (https://help.salesforce.com/articleView?id=000176370&type=1) are irrelevant and may come over into the new LMO but the numbers will not be consistent. Additionally Licenses associated with Sandbox orgs will not be migrated over. 

8. Will the Lead records be brought over with the License Refresh?

[A] Yes, the Lead records are also brought over.

9. Are licenses associated to sandbox orgs migrated over into the new LMO?

[A] No, currently the LMA migration does not move these licenses over at this time. A workaround is to ask your customers to refresh their sandbox(select the production org as source), install the package manually or use the Push Upgrade feature (https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging_push_about.htm) to generate a license in the new LMO.
Note when cloning an existing sandbox, the license for the new sandbox is created in the OLD LMO.  

10. Will the license count between the old and new LMO be the same?

[A] No, This can occur due to new package installs or orgs in the new LMO that have been deleted, hold and suspended etc. Therefore the numbers will not match. You can create a report with the following the criteria to see all your Active True licenses in the new LMO.

- Object - License
- Criteria:
    Sandbox equals false
    Package equals Package Name
    Org Status not equal to SUSPENDED,DEMO,deleted,free,hold,SIGNING_UP
    Org Status not equal to

11. What is the impact of creating new packages in our packaging org while LMA migration sync is in progress? 
 
[A] There should be no impact. Essentially Tier 3 updates 1 field with the LMA ID that is associated the package (033). Once that’s done, it takes a few minutes to replicate the change to all instances. It is very rare that a package is created at the same time during a LMA ID update. Support can always update that field again and the change will replicate again. Additionally, we advise not uploading any versions until support gives confirmation that it is done. 

12. Can I request to move extra license, leads or other records from the old to new LMO?

[A] The LMA Migration focuses on moving all Active Production Org License Records to the new LMO. This an automated process that occurs in the background and cannot be updated nor changed. R&D is exploring new features to update the process and we encourage to post these Ideas on the Success Community (https://success.salesforce.com/ideasearch).

13. What happens to the license records in the old LMO?

[A] The licenses in the old LMO are never going to be updated by the automated process since the connection is going towards the new LMO. The other records that did not get migrated will just be stale records for you to use or archive. For example, the sandbox license in the old LMO is irrelevant and will get regenerated in the new LMO when you do a push upgrade, refresh the sandbox w/package or if the customer installs/upgrades the package. 

 
Knowledge-artikelnummer

000381485

 
Laddar
Salesforce Help | Article