Documentation

License transfer due to restructuring

Last update: Fri May 01 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

When an Adobe Commerce license is restructured, account ownership is transferred to a new MAGE ID, which can disrupt deployments, upgrades, and Commerce Services. Updating extensions, access keys, Commerce Services configuration, and user access ensures continuity after the license transfer.

Description description

Environment

Adobe Commerce (all deployment methods)

Issue

Due to an Adobe Commerce license restructuring, a new account owner is assigned to your project/instance. To ensure a smooth transition and avoid any issues with deploying or upgrading code and utilizing Commerce Services such as Product Recommendations, Live Search, Catalog Service, and others, you will need to perform several steps.

Resolution resolution

Note: The steps mentioned below replace the standard account owner change procedure, as it specifically applies to cases involving Adobe Commerce license restructuring.

  1. You need to review any extensions in the old account and either:

    1. Transfer them to the new account. Be aware that the purchase history will be lost in the process. Open an Adobe Commerce Support ticket to request this. Indicate the MAGE ID of both the old and new accounts.

    2. Request a refund and repurchase them in the new account:

      1. For paid extensions, request a refund to the old account by opening a Support ticket with the Commerce Marketplace team, and then repurchase them in the new account.
      2. For free extensions, reacquire them in the new account.

  2. You need to generate new access keys to download your Adobe Commerce code and your purchased extensions.

    • Visit Adobe Commerce Marketplace to generate new access keys.

    • Update the Composer credentials based on your deployment type:

      • On‑premises deployments: Update the credentials in the auth.json file used by Composer.
      • Adobe Commerce on Cloud: Adobe recommends managing Composer credentials using the project-level and environment-level env:COMPOSER_AUTH variable in Adobe Commerce Console /< username> /< projectID> /-/settings/variables.
      • If Composer credentials are also present in a local auth.json file, ensure that they match the values configured in env:COMPOSER_AUTH. Mismatched credentials can result in incorrect entitlements or access issue.

  3. Generate and update Commerce Services API keys and SaaS project configuration.

    • Go to the Adobe Commerce API Portal and generate both production and sandbox API keys.
    • Update the existing API keys in all locations where the Commerce Services Connector is configured with the old keys.
    • If you have an existing SaaS project, it is tied to the previous MAGE ID. After updating the API keys, you must create a new SaaS project.
    • When the license is transferred to a new MAGE ID, data and telemetry from the previous SaaS environment are not carried over. The new SaaS environment begins collecting data from scratch.
    • If you are running Live Search, submit a support request to reindex the associated indices after configuring the new API keys and SaaS project.

  4. Re‑grant Shared Access for users on the new MAGE ID.

    • When the license is transferred to a new MAGE ID, Shared Access from the old MAGE ID is not carried over. The new license owner must manually grant Shared Access to the required users on the new MAGE ID.
    • Users must be informed of the new Adobe Commerce organization so they know which organization to select when submitting support tickets going forward.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f