--- title: "Can You Transfer a WordPress Plugin Licence?" date: 2026-06-20 author: "Imtiaz Rayhan" featured_image: "https://wpblocksuite.com/wp-content/uploads/2026/08/featured-transfer-wordpress-plugin-licence.png" categories: - name: "WordPress Plugins" url: "/blog/category/wordpress-plugins.md" --- # Can You Transfer a WordPress Plugin Licence? You can transfer some WordPress plugin licences. The vendor’s terms, account system, product, and transfer eligibility decide the answer. A transfer can move commercial ownership without changing the installed plugin. Verify billing, access, site connection, and acceptance separately. ## Can you transfer a WordPress plugin licence? Sometimes. Some vendors provide an account transfer workflow. Others permit sharing, site reassignment, or no ownership transfer. Check current product rules before promising a handoff. Never transfer access merely by emailing a key. ## Start with precise vocabulary - Ownership transfer changes the commercial account holder. - Sharing grants another account selected access. - Site reassignment moves capacity between site identities. - Account collaboration adds another authorised user. - Credential handover gives access without formal transfer. - Plugin migration moves code and settings. - Billing change updates who pays. - Renewal change updates future commercial responsibility. These events can happen together, but none guarantees the others. Name the required outcome first. ## Plugin code and commercial entitlement differ WordPress plugin code commonly uses a GPL-compatible licence. The official [plugin licensing guidance](https://developer.wordpress.org/plugins/plugin-basics/including-a-software-license/) explains that expectation. Commercial updates, support, downloads, and hosted services can still use account controls. A transfer concerns those entitlements. ## The vendor is the authoritative source Marketplace conventions do not create a universal transfer right. Read the seller’s current documentation and terms. Ask support when the workflow remains ambiguous. Keep the dated answer with the purchase record. ## Transfer eligibility can depend on product status - The subscription may need active status. - The order may need completed payment. - A refund request may block changes. - The product may exclude transfers. - A marketplace account may control ownership. - A bundle may transfer only as one unit. - A pending transfer may block another request. - The recipient may need an eligible account. Do not assume an expired purchase is transferable. Confirm eligibility before scheduling site handoff. ## WooCommerce provides a formal transfer workflow Its [subscription transfer guidance](https://woocommerce.com/document/managing-woocommerce-com-subscriptions/transfer-a-subscription/) describes sending a transfer to another WordPress.com account. The recipient must accept it. That workflow applies to eligible WooCommerce.com subscriptions. It does not define rules for every plugin seller. ## A WooCommerce transfer moves commercial control WooCommerce says acceptance moves ownership, billing, renewals, support, and update access. The recipient manages the subscription afterward. Record which capabilities moved in your case. Product changes can alter future details. ## A WooCommerce transfer does not move everything Its documentation says installed files and site account connections do not automatically transfer. Treat technical access separately. The site may need reconnection under the new owner. Verify updates and extensions after acceptance. ## Sharing can fit better than transfer WooCommerce also documents [subscription sharing](https://woocommerce.com/document/managing-woocommerce-com-subscriptions/share-a-subscription/). Sharing gives another account access while the original owner keeps billing responsibility. Use sharing for collaboration when permanent ownership should not move. Review revocation and support access. ## Site reassignment can fit better than transfer A vendor may let you deactivate one site and activate another. Commercial ownership remains unchanged. This suits migrations within one owner. It does not complete a client ownership handoff. ## Account collaboration can fit better than transfer Named collaborators can manage support or downloads without moving billing. Their permissions vary by vendor. Prefer named access over shared passwords. Remove collaborators when their work ends. ## A billing change is not necessarily a transfer Changing a card or invoice address may leave account ownership unchanged. Confirm the legal and operational owner. Record both payer and entitlement owner. They can be different organisations under an approved arrangement. ## A key handover is weak evidence Sending a key does not prove vendor-approved ownership. The original account may retain recovery and billing control. Keys can also spread through email archives. Use the vendor’s supported transfer or sharing workflow. ## Define the desired end state - Who owns the entitlement? - Who pays future renewals? - Who receives invoices? - Who can download updates? - Who can open support requests? - Which sites consume capacity? - Who controls vendor account recovery? - Who can cancel or transfer again? - Who maintains the installed plugin? - When does responsibility change? A vague request to transfer the licence hides these decisions. Resolve them before changing account state. ## Inventory the entitlement before transfer - Exact vendor and product. - Order and subscription identifier. - Current account owner. - Plan, term, and renewal date. - Current price and billing status. - Site allowance and active assignments. - Bundle and add-on dependencies. - Open support cases. - Transfer restrictions and eligibility. - Current site connection method. This inventory prevents hidden dependencies. Keep secrets outside ordinary handoff notes. ## Confirm the recipient identity Verify the recipient’s organisation, account email, and authorised contact. A mistyped address can expose valuable entitlement. Use an organisation-controlled account where possible. Confirm recovery and multifactor protection before transfer. ## Do not use a personal account by default An employee can leave with account recovery control. Personal ownership also complicates billing and future handoff. Choose the recipient account deliberately. Document exceptions and a future remediation date. ## Check recipient account conflicts The recipient may already own the product or use another marketplace identity. Duplicate records can confuse support and renewals. Ask the vendor before merging or duplicating subscriptions. Preserve both order histories. ## Check the renewal timing A near renewal can create disputed charges during handoff. Decide who pays before initiating transfer. Record current price, tax treatment, payment method, and renewal date. Do not expose card details. ## Check outstanding refunds or disputes A pending refund, chargeback, or billing dispute can change entitlement status. Resolve it before promising access. Coordinate finance and technical owners. Keep commercial evidence beside the transfer record. ## Check open support cases A transfer can change who sees tickets or may contact support. Export allowed case history when necessary. Remove unrelated customer data. Tell the recipient which unresolved work remains. ## Check site capacity and assignments List every production, staging, development, and retired identity. Confirm which assignments belong with the recipient. Do not transfer an agency-wide entitlement accidentally. Separate unrelated clients before handoff when the vendor permits. ## Multi-site packages may be indivisible WooCommerce says a multi-site subscription cannot be split during transfer. The entire subscription moves together. Sharing or a new entitlement may suit one client better. Compare future ownership and renewal needs. ## Bundles need dependency review A bundle can include products used by several sites. Transferring the bundle may affect unrelated operations. Map each component and assignment. Ask whether individual products can transfer separately. ## Add-ons need parent entitlement review An add-on may require a parent plugin or service. Transfer both when the intended workflow depends on them. Confirm version compatibility and renewal alignment. Avoid leaving the recipient with an unusable fragment. ## Lifetime licences still need transfer rules No renewal fee does not mean free reassignment. The vendor can still restrict account ownership or site count. Check the purchase terms and current process. Record what support and updates accompany transfer. ## Expired licences need explicit confirmation An expired entitlement may retain installed code but lack transfer, downloads, or support. Vendors handle expiry differently. Ask whether renewal must occur first. Decide who bears that cost. ## Marketplace purchases can follow marketplace rules The original seller may not control account transfer. Marketplace identity and order systems can govern access. Use the marketplace’s official workflow. Avoid opening duplicate seller accounts without guidance. ## Prepare the site separately 1. Back up the site and configuration. 2. Record the current plugin version. 3. Record local licence status. 4. Record the vendor account connection. 5. Test current update access. 6. Identify connected cloud services. 7. Schedule a controlled handoff window. 8. Prepare rollback responsibilities. Do not uninstall working code merely to transfer entitlement. Follow product-specific reconnection instructions. ## Prepare the recipient separately 1. Create or verify the approved account. 2. Enable supported multifactor protection. 3. Confirm account recovery ownership. 4. Verify billing responsibility. 5. Confirm authorised technical contacts. 6. Review the vendor transfer instructions. 7. Schedule acceptance availability. 8. Store evidence in approved systems. ## Initiate through the vendor workflow Select the exact entitlement and recipient. Review every confirmation screen before submitting. Capture a secret-free record of initiation. Note any acceptance deadline or cancellation option. ## Acceptance is a separate control A sent transfer may remain pending. The recipient does not own it until the vendor records acceptance. Do not close handoff at initiation. Track pending status and verify the final account. ## Avoid sending repeated transfer invitations Duplicate invitations create confusion and increase misdelivery risk. Confirm the current pending state first. Cancel an incorrect transfer through supported controls. Escalate promptly when cancellation is unavailable. ## Verify commercial ownership after acceptance - The recipient sees the correct product. - The original account reflects the transfer. - Billing responsibility matches the agreement. - The renewal date and term remain understood. - Downloads are available as expected. - Support access matches vendor policy. - Site allowance remains correct. - No unrelated entitlement moved. ## Verify the site connection after acceptance - The production site reports valid status. - The correct account owns the connection. - Authenticated updates remain available. - Required hosted services still work. - Staging treatment remains understood. - No old account retains unnecessary access. - The vendor portal shows the intended site. - The internal register matches both systems. A commercial transfer is incomplete operationally until these checks pass. Record any vendor-approved exceptions. ## Reconnect only when documentation requires it Unnecessary disconnection can interrupt updates or services. Follow exact vendor instructions for the transferred product. Take a pre-change snapshot. Confirm successful reconnection and remote identity afterward. ## Rotate credentials when exposure occurred A formal transfer may not invalidate copied keys or tokens. Ask the vendor about supported rotation. Inventory every connected site before rotation. Verify them again after replacement. ## Remove former collaborator access Transfer does not always remove account users, vault entries, or site administrators. Offboard each access path separately. Review vendor sessions and recovery contacts. Preserve emergency access under the new owner. ## Update the entitlement register Record old owner, new owner, effective date, acceptance evidence, billing state, and site status. Link the approved agreement and vendor confirmation. Never store raw secrets in the transfer narrative. ## Update finance records Stop duplicate renewal reminders and charges. Confirm invoice ownership, tax records, and future approval routes. Retain historical invoices according to policy. Do not move unrelated financial data. ## Update maintenance responsibilities Owning a licence does not assign plugin maintenance automatically. Name who tests, updates, monitors, and escalates. We looked at that in [how long to keep an unused licence](https://wpblocksuite.com/blog/keep-unused-wordpress-plugin-licence/). Set the next review date. Include staging and recovery responsibilities. ## Plan for a rejected transfer The recipient may reject or ignore the invitation. The vendor may also deny eligibility. Keep current ownership stable until acceptance. Choose sharing, reassignment, or purchase only with approval. ## Plan for an incorrect recipient Contact vendor support immediately. Provide order and transfer evidence through secure channels. Do not publish account details while seeking help. Record remediation and any exposure assessment. ## Plan for transfer reversal Some workflows may not support automatic reversal. Confirm cancellation and retransfer options before initiation. A later reversal may require recipient cooperation. Put that responsibility in the handoff agreement. ## Use a transfer agreement for business handoffs - Exact entitlement and order. - Agreed recipient account. - Effective responsibility date. - Billing and renewal responsibility. - Included site and support access. - Excluded products and services. - Required technical reconnection. - Acceptance and verification duties. - Failure and rollback process. - Evidence retained by both parties. This record supports the vendor workflow. It does not override vendor terms. ## Keep client data out of vendor notes Transfer requests need account and product evidence, not complete site databases. Share only necessary information. Redact keys, payment data, and unrelated customer details. Use secure channels for required secrets. ## Know the honest weak case Permanent transfer may be wrong for temporary collaboration. Sharing can preserve ownership and simplify later revocation. Site reassignment can suit a simple domain migration. Choose the smallest change matching the real outcome. ## Use the plugin licence transfer checklist 1. Define ownership, billing, support, and site outcomes. 2. Identify the exact product and entitlement. 3. Read the vendor’s current transfer rules. 4. Confirm transfer eligibility and restrictions. 5. Inventory bundles, add-ons, and site assignments. 6. Verify the authorised recipient account. 7. Secure recipient recovery and authentication. 8. Resolve renewal and billing timing. 9. Prepare site and rollback evidence. 10. Initiate through the official workflow. 11. Track recipient acceptance. 12. Verify commercial ownership afterward. 13. Verify downloads, support, and updates. 14. Reconnect the site only when required. 15. Remove obsolete account and site access. 16. Update finance and entitlement records. 17. Assign future maintenance responsibility. 18. Retain secret-free completion evidence. ## Frequently asked questions Can every premium WordPress plugin licence be transferred? No. Transfer eligibility and process depend on the vendor and exact product. Is sharing a licence the same as transferring it? No. Sharing can grant access while the original account retains ownership and billing. Does a licence transfer move the installed plugin? Not necessarily. Code, settings, site connection, and commercial ownership are separate. Can a multi-site subscription be split during transfer? WooCommerce says its multi-site subscriptions transfer as one unit, not separate seats. Should I email the licence key to the new owner? No. Use the vendor’s supported transfer, sharing, or account process. ## The verdict Verdict **Transfer only through supported controls:** vendor eligibility decides whether ownership can move. **Verify the whole handoff:** acceptance, billing, downloads, support, site connection, and access remain separate checks. A precise transfer protects both owners and keeps maintenance recoverable. [Review WP Block Suite’s $299 lifetime licence](https://wpblocksuite.com/#pricing).