Prepare the asset inventory

Agree what is included and who receives it in the contract. Keep the exact store item separate from the code and services it depends on:

Inventory for a Chrome extension handover
AssetWhat to identifyRecipient check
Store itemItem ID, current publisher and intended recipientOpen the correct item with the agreed access
Source and buildSource version, dependencies and build instructionsReproduce the intended build
Domains and listing assetsIncluded domains, descriptions, images and access arrangementsVerify the agreed assets and usable access
Backend and integrationsServices, APIs, operator and continuity arrangementsComplete the agreed product action
Analytics and supportHistorical records, ongoing access and responsible peopleCheck each agreed source and responsibility

The store listing definition helps distinguish the public item from the rest of this inventory. For the preceding buyer review, use how to assess a Chrome extension’s value.

Follow the store transfer process

The guidance below is current as of November 2026, checked on 1 November.

Item transfer to another developer account:

  1. Read Google’s developer registration guide. If the recipient needs a new developer account, follow its registration instructions.
  2. For an item moving to another developer, use the official support form linked by that guide.
  3. Keep the request, support response and recipient check with the exact item ID in your handover record.

The public registration page does not list the transfer form’s current fields or a completion time. Follow the current official instructions; if transfer options are not displayed, ask Chrome Web Store developer support for the route.

Publisher access and the older group-publisher model:

Google’s Share ownership guidance says the distinction between individual and group publishers no longer applies. To add access to the publisher that owns the item:

  1. Select that publisher from the top-right pull-down in the Developer Dashboard.
  2. Open Settings and find the members table.
  3. Choose Invite member and a role; Google sends an invitation email.

The Admin role manages members and roles. Record whether you are granting access within a publisher or requesting an item transfer to another account; these are different routes.

Transfer project assets and access

Work through the inventory independently of the store request. For each asset, record delivery, the recipient’s check and the remaining action. Agree responsibilities and acceptance conditions in the contract.

Illustrative handover record, not a completed transaction:

Example separating receipt from verification
ItemObserved statusCheck still open
Store itemTransfer request sentSupport response and recipient access
Source bundleArchive receivedReproduce the intended build
AnalyticsHistorical export receivedVerify any agreed ongoing access

For migration, repairs or build work, agree a separate extension development scope.

Verify the extension after transfer

Use this acceptance check:

  1. In the recipient’s Developer Dashboard, select the intended publisher and open the correct item.
  2. Match the item ID, store URL and published version. Check the review status next to the item, following Google’s status instructions.
  3. Test the agreed product action in the recorded browser and build, including required backend services.
  4. Save the results, capture date and remaining owner/action for every open inventory row.

Close each row after its agreed check. Keep a store request, usable publisher access and an operational product as separate statuses.

Extcorp discusses its extensions for sale and the included handover materials privately. Send the item or acquisition criteria and the transfer questions you need to settle.

Discuss an extension acquisition

Extcorp is independent of Google and Chrome Web Store.