)
Transferring Shopware licences: moving account, licence host and Composer token cleanly
The three places a Shopware licence is tied to
1. The shop in the Shopware Account. At account.shopware.com every shop is set up as a domain. The plan (Rise, Evolve, Beyond) and every extension bought or rented from the Store are attached to that domain. Whoever owns the account owns the licences.
2. The licence host in the administration. Under Settings > System > Shopware Account, the licence domain field states which domain from the account this installation is licensed for. Under Extensions > My extensions > Shopware Account, the administration is logged in to an account. Both must match the account that holds the shop.
3. The Composer token. If the shop is run properly with Composer and deployments, Store extensions do not come from the administration but from the Composer registry packages.shopware.com. Access runs through a token created per shop in the Shopware Account and stored in the project's auth.json. The token belongs to the account it was created in.
Most problems after an agency switch arise because place 1 is moved while 2 and 3 still point to the agency. The shop keeps running until the next update or deployment.
Inventory before the switch
Before anything is transferred, you need the complete picture. We settle these questions in the first week of every takeover:
Which account holds the shop? Log in with your own credentials at account.shopware.com and open Shops in the merchant area. If your shop is missing, it is almost always in the agency's partner account.
Which extensions are installed, and where do they come from? Not everything listed under My extensions has a Store licence. Three other cases are typical: the agency's own developments, third-party plugins with their own licence outside the Store, and plugins uploaded as a ZIP at some point that have not received updates since.
Which licence type does each Store extension have? Purchase, rental or subscription, with term and next renewal.
Which plan is booked, and who is the contracting party with Shopware? Rise, Evolve and Beyond are separate contracts. If the agency is listed there, that contract has to be switched too.
How is the shop deployed? Through Composer and a pipeline, by uploading in the administration or by copying files to the server. This determines whether place 3 matters at all.
This list shows what has to be transferred and what cannot be. Custom developments and third-party licences do not run through the Shopware Account. Settle those directly with the agency or the vendor.
Step 1: Transfer the shop in the account
The transfer always starts in the account that currently holds the shop. If that is the agency, they carry out this step.
In the releasing account, go to Merchant > Shops and select the domain.
Open the licence transfer wizard at the top of the domain.
Enter the recipient's details: customer number, company name and contact person of your Shopware Account. Have these ready before you ask the agency.
Choose the scope: the whole shop including its domain, or individual licences. When switching agency, the whole shop is almost always right. Linked licences such as Advanced Features move with the extension.
Submit. Shopware's sales team reviews the request within the following working days.
What blocks the transfer: a negative balance on the shop. The current owner settles open amounts first. The collective invoice for the current month goes to them and cannot be reissued afterwards. So agree beforehand who pays which month.
Step 2: Switch the administration to your account
As soon as the shop has arrived in your account:
In the administration, open Settings > System > Shopware Account and check that the licence domain field contains exactly the domain registered in your account. Without https://, without a path.
Under Extensions > My extensions > Shopware Account, log out the agency's login and log in with your account.
Check that all licences under My extensions show as licensed and that updates are displayed.
The licence host is independent of the APP_URL in the server configuration, by the way. A shop can run under a different URL from the one it is licensed for. That is intended on test systems and usually an oversight on live shops.
Step 3: Replace the Composer token
This is the step most often forgotten, because it is not visible in the administration.
The project contains an auth.json file with an entry for packages.shopware.com. The token in it was created in the agency's account. As long as it is valid, everything works. If the agency deletes it, or it becomes invalid after the transfer, the next composer install aborts with Invalid access token and the deployment fails.
How to replace it:
In your account, open the shop, click any extension and choose Install via Composer.
Generate a new token and store it securely.
Replace the token in auth.json on the server and in the secret variables of the deployment pipeline. Alternatively, the command-line tool shopware-cli creates the auth.json directly for a domain of your account with account merchant shop configure-composer.
Run a test deployment on staging before anything happens live.
auth.json does not belong in the Git repository. Shopware excludes it by default through .gitignore. If you find the token in the repository during a takeover, it tells you something about how credentials were handled there in general.
Common error messages after the transfer
Licence host unknown
The licence domain in the administration does not match any domain in the account the administration is logged in with. Correct the licence domain under Settings > System > Shopware Account, then log out and back in under My extensions.
Wrong combination of licence host and Shopware Account login
The administration is still logged in with the agency's login while the shop is already in your account, or the other way round. Log out and log in with the account that now holds the shop.
Invalid access token during deployment
The Composer token in auth.json still belongs to the old account or has been deleted. Generate a new token in your account, see step 3.
Extension shows as unlicensed
The licence was not transferred, it ran on a different domain such as an agency test domain, or it was never a Store licence. Check in the account which domain holds the licence. Within one account, licences can be moved to another domain with Transfer licence.
Plan, GMV and costs
For the switch it matters how Shopware bills. Merchants with more than €1 million gross merchandise volume (GMV) a year through the shop who use the Shopware Account and Store need one of the Rise, Evolve or Beyond plans. The plans themselves are also priced by GMV. Since 14 April 2026, Shopware reports GMV automatically from version 6.7.8.
For the transfer this means: check whether your plan matches your actual revenue, and who booked it with Shopware. A plan the agency booked through its partner account is transferred together with the shop. Contract details such as term, conditions and GMV limit are then clarified directly with Shopware.
Clean up: cancel licences nobody needs
Going through the list almost always reveals extensions that are paid for but no longer used. Important: uninstalling a plugin in the administration or removing the Composer package does not end a paid subscription. Cancellation only happens in the Shopware Account. Otherwise you keep paying for something that is no longer installed.
Special cases
The shop domain changes. Rename the domain in the account instead of creating a new shop: under Shops, select the domain, use Rename shop domain in the shop information and verify the new domain with the generated token. All licences then apply to the new domain. You have to enter the licence domain in the administration again, and maintain the Shopware version in the shop information by hand.
Test systems. In the shop information you set whether a domain is a live shop or a test shop. Mark staging domains as test shop. How a test system is built properly is covered in Shopware staging and backup.
Shopware 5. Licences for Shopware 5 plugins cannot be transferred to Shopware 6 where the plugin is a separate version for Shopware 6. If a switch coincides with a migration, recalculate plugin costs.
Changing the partner
A merchant account has exactly one integration partner, and Shopware requires your confirmation before a new partner is assigned. If the shop is already in your account, changing the partner is the easy part. If the old assignment does not clear by itself, Shopware's customer team helps at customer@shopware.com.
Checklist
Own Shopware Account with a company email, not a personal address
List of all extensions with origin (Store, third party, custom, ZIP) and licence type
Plan and contracting party with Shopware clarified
No negative balance, billing for the handover month agreed
Shop including domain transferred to your account and confirmed by Shopware
Licence domain in the administration checked, administration logged in with your account
New Composer token generated, auth.json and pipeline variables replaced, test deployment successful
Unused subscriptions cancelled in the account
Staging domains marked as test shop
New agency confirmed as partner
How we do it at arboro
When you switch to arboro, the licence question is the first work package, before anyone touches the code. We build the complete extension list with origin and costs, coordinate the transfer with you and the current agency, switch the administration and Composer token over and verify it with a deployment on staging. We show you unused licences with their monthly costs so you can decide what to cancel. The whole process is described on Switch your Shopware agency.
For ongoing care after the switch: Shopware & Shopify support. If a move from Shopware 5 is also due: Shopware 5 migration.
Frequently asked questions
No. The transfer only changes which Shopware Account holds the licences. Products, orders and plugin settings live in your database and are not affected. What has to be adjusted afterwards is the licence host and login in the administration and, for Composer installations, the token in auth.json.
Almost always because auth.json still contains the Composer token from the agency's account. Generate a new token in your account under Install via Composer and replace it on the server and in the pipeline.
If the shop is in their partner account, yes: the transfer starts in the releasing account. If the agency does not respond, Shopware agency won't hand over access explains how to proceed.
No. Uninstalling in the administration or removing the Composer package does not end a paid subscription. Cancellation happens only in the Shopware Account.
The Community Edition is free. Under Shopware's rules, merchants with more than €1 million GMV a year through the shop who use the Account and Store need one of the Rise, Evolve or Beyond plans.
Licences, licence host, Composer token: we switch it all over.
When you switch to arboro, the licence question is the first work package. We take over your shop while it keeps running, at a fixed price.
)