Move your WordPress business forward without throwing away what you already built
Moving marketplaces, checkout systems or licensing infrastructure does not need to mean abandoning existing customers overnight. WPBay supports a phased approach: move new sales first, validate the new setup, transition legacy buyers strategically, and expand only when you are confident.
- Keep your existing channel running
- Import Envato product details
- Transition legacy buyers gradually
- Create migration coupons
- Move to WPBay licensing
- Introduce subscriptions
- Test before expanding
- No marketplace exclusivity
Staying where you are can feel safer than changing anything
You have customers. Purchase codes exist. Updates are already going somewhere. Maybe recurring payments are running through another provider.
Even when the current setup is frustrating, switching introduces uncertainty.
What happens to existing buyers? Will licences continue working? Do customers need to buy again? What happens to renewals? Will support explode?
Those are reasonable concerns.
The mistake is assuming migration has to be one giant irreversible event.
WPBay exists because I needed to make this move myself
I am Szabi, founder of WPBay and the developer behind CodeRevolution.
I spent more than a decade selling WordPress software through CodeCanyon. I built products, shipped updates, supported customers and became deeply dependent on a marketplace model built mainly around one-time purchases.
When those sales started declining, I had to make the same decision other established sellers face: keep depending entirely on the existing channel or build something more sustainable.
Aimogen Pro was moved from Envato into a subscription-based business on WPBay. That experience directly shaped WPBay’s migration tools.
Most migration fear comes down to continuity
The files are usually not the scary part. Customer access, licences, renewals and support are.
Will existing customers suddenly lose access?
They should not. Legacy purchase validation can remain operational while your WPBay integration handles new WPBay buyers.
Do I need to invalidate my old licence keys?
No. A phased migration can continue recognizing legacy licences while WPBay licences are introduced for new and migrated customers.
Do existing subscribers need to enter their card again immediately?
Not if you leave their existing subscription running. Move new billing first and transition legacy customers separately when appropriate.
How will old customers continue receiving updates?
Your product can retain its existing update path for legacy customers while WPBay’s SDK delivers updates to licences sold through WPBay.
Does every old customer record need to be imported?
Not necessarily. Decide what actually needs to move instead of copying years of legacy data simply because it exists.
What if I don’t like the new setup?
WPBay is non-exclusive. Test one product while your existing sales channel remains active instead of making an all-or-nothing bet.
Four principles behind a safe WPBay migration
Planned
Understand licences, products, pricing, subscriptions and customer access before changing the production setup.
Phased
Move one product and new transactions first rather than switching an entire business overnight.
Validated
Use WPBay developer mode and sandbox licences to test activation, plans and updates before customers depend on them.
Adapted
Keep whatever legacy compatibility you still need while gradually adopting WPBay’s licensing, subscriptions and customer workflows.
Separate what can be imported from what needs a transition plan
A trustworthy migration starts by being specific. Product migration, customer migration, licensing migration and payment migration are different things.
Envato sellers already have dedicated WPBay migration tools
WPBay was built with Envato authors in mind because that is exactly where its founder came from.
You do not need to manually recreate every product listing from scratch, nor do you need to pretend that your existing buyers never existed.
Move in stages instead of betting the whole business on cutover day
The objective is simple: each stage should be reversible until the next one has proved itself.
Audit what you have today
List every product, licence type, plan, recurring subscription, legacy purchase-code format, update server, support entitlement, coupon and external integration connected to the current system.
Choose one product first
Do not start with your most complicated product unless you need to. A smaller real product lets you test WPBay under production conditions with much lower business risk.
Create or import the WPBay listing
Envato authors can use the product-import workflow. Other sellers can create the listing normally, including screenshots, documentation, files, pricing and support information.
Design the new pricing model
Decide whether you want one-time purchases, monthly subscriptions, yearly subscriptions, product plans, multiple site allowances or a combination of these.
Integrate WPBay licensing and updates
Use the WPBay SDK or REST API for WPBay purchase validation, site activations, plan detection and WordPress updates. Keep legacy validation in place if existing customers still depend on it.
Test using developer mode
WPBay provides developer testing licences and sandbox activations so you can test integration without buying your own product or consuming normal customer licences.
Submit the product for review
The WPBay team reviews new products before publication. Resolve any technical, packaging, security or listing issues before the new sales path becomes customer-facing.
Send new customers through WPBay
Start generating fresh WPBay purchases while your legacy buyers remain untouched. Validate checkout, licence activation, downloads, support and update delivery under real conditions.
Transition legacy buyers strategically
Once the new system is proven, introduce migration coupons, upgrade paths or subscription offers to existing customers. The right approach depends on what those customers originally bought.
Expand the migration
Repeat the proven workflow across additional products instead of redesigning the migration every time.
Run legacy and WPBay customers side by side during the transition
A product can know where a customer’s entitlement came from and validate it through the appropriate system.
Legacy customers
Customers who purchased before your WPBay launch.
- Existing licence keys remain valid
- Existing entitlement rules stay intact
- Legacy subscriptions can keep renewing
- Existing update mechanism can remain available
- No forced repurchase on migration day
WPBay customers
Customers purchasing through your new marketplace setup.
- WPBay purchase codes
- WPBay licence activations
- Product plan detection
- WPBay automatic updates
- One-time or recurring billing
Your old customers do not need to stop existing because you changed platforms
One of the worst migration strategies is replacing the licensing endpoint and immediately treating every old purchase code as invalid.
Instead, make entitlement origin explicit.
Legacy customers can continue through the legacy validation path while WPBay buyers use WPBay purchase codes and the WPBay SDK or API.
Over time, selected legacy customers can be moved into the WPBay model through clearly defined upgrade or migration offers.
plan_type so your product can unlock the appropriate features.
Do not promise a magic transfer of payment credentials
A subscription is more than a row in a database. It is connected to a payment processor, payment method, mandate, billing history and customer authorization.
That means migration should distinguish between the customer’s software entitlement and the system actually charging their card or PayPal account.
WPBay can become the billing platform for new subscriptions immediately. Existing recurring customers can continue billing through the previous provider until you have an appropriate reason and method to transition them.
WPBay does not advertise a universal one-click import of card numbers, PayPal billing agreements or payment tokens from arbitrary third-party platforms. Whether a payment method can be transferred depends on the payment providers involved and the specific migration arrangement.
Give existing customers a reason to move instead of giving them an ultimatum
Your existing users already paid you. Migration should respect that relationship.
Validate old purchase codes
For Envato migrations, WPBay can use legacy purchase-code status as part of the customer transition workflow.
Offer migration coupons
Give existing buyers a meaningful discount when they choose to enter the new recurring or licence model.
Connect migration to new value
A transition is easier to understand when the new plan includes continued updates, new features, more licences or another concrete benefit.
Allow a transition period
You do not need every customer converted in the same week. A long tail of legacy licences is normal.
Communicate clearly
Explain what is changing, what stays the same, what the buyer needs to do and what happens if they do nothing.
Honor existing rights
Do not retroactively remove benefits a customer legitimately purchased merely because your commercial model changed.
What WPBay takes off your plate for new marketplace sales
Once a customer purchases through WPBay, the marketplace becomes the commercial seller for that transaction.
Checkout and payments
WPBay operates the marketplace checkout and standard payment-processing infrastructure.
Buyer-facing taxes
Applicable VAT and customer-facing transaction taxes are handled under WPBay’s Merchant of Record structure where required.
Customer invoices
Buyers purchase from WPBay and receive their marketplace invoice or purchase documentation from WPBay.
Recurring billing
New monthly and yearly subscriptions can be billed and managed through the WPBay marketplace.
Licensing infrastructure
Use WPBay purchase codes, activation limits, plans, SDK helpers and API endpoints instead of building the new licence backend from scratch.
Automatic updates
Valid WPBay licences can receive plugin and theme updates through the normal WordPress update experience.
Refund workflow
Marketplace refund requests and transaction adjustments are administered through WPBay.
Affiliate promotion
Products can benefit from WPBay’s marketplace affiliate system without each seller building a separate tracking and payout platform.
Marketplace discovery
Your new sales channel becomes part of a marketplace where customers can browse and discover WordPress products from multiple developers.
WPBay moves the marketplace layer. You still own the product.
WPBay handles
Infrastructure connected to standard WPBay marketplace transactions.
- WPBay product marketplace
- Marketplace checkout
- Standard payment processing
- Customer billing
- Applicable buyer-facing VAT/tax handling
- Customer invoices
- WPBay subscription billing
- WPBay purchase codes
- WPBay licensing infrastructure
- WPBay update delivery infrastructure
- Marketplace refund administration
- Affiliate infrastructure
You remain responsible for
The software business and product-specific continuity.
- Your software code
- Product maintenance
- Compatibility
- Security of the product
- Documentation
- Product-specific support
- Accurate migration communication
- Legacy licence compatibility you choose to retain
- Legacy payment systems still serving old customers
- Your own accounting and taxes on WPBay earnings
Your migration readiness checklist
Do not cut over because the calendar says so. Cut over because these questions have answers.
plan_type unlocks the correct functionality.
Questions sellers ask before moving to WPBay
Do I have to stop selling on Envato or my existing website?
No. WPBay is non-exclusive by default. You can launch WPBay as an additional sales channel while keeping your existing storefront operating, subject to the terms of the other platforms you use.
Can WPBay import my Envato products automatically?
WPBay includes an “Import From Envato” workflow in the seller dashboard. You can provide an Envato Personal Token, view your Envato items and use their information to populate the WPBay product upload form. You should still verify the imported information, upload the appropriate current files and complete the WPBay submission process.
Can my old Envato purchase codes still be useful?
Yes. WPBay has migration tooling that can validate Envato purchase codes and create WPBay coupon offers based on legacy purchase/support status. This can be used to create a smoother path from an old purchase to a new WPBay licence or subscription.
Do all my existing customers need to move immediately?
No. A phased migration is usually safer. Existing customers can continue under their existing entitlement while new customers purchase through WPBay. Legacy customers can then be transitioned gradually where appropriate.
Can I keep supporting old licence keys?
Yes. Your own plugin or theme can continue recognizing its legacy licensing system while also integrating WPBay licensing for WPBay customers. How you implement dual compatibility depends on your existing codebase.
Can WPBay automatically import every active subscription from another platform?
You should not assume so. Moving subscription records is different from transferring the payment credentials or billing agreements that actually allow future charges. Existing subscriptions can remain on the original billing system while new subscriptions are created through WPBay, with legacy customers transitioned separately.
Will customers have to re-enter their card details?
Not simply because you start selling new licences on WPBay. Existing customers whose subscriptions remain on the legacy payment provider can continue billing there. If you later move an individual customer to a new WPBay subscription, that customer may need to complete the new checkout depending on the migration path available.
Can I test WPBay licensing before going live?
Yes. WPBay’s developer mode provides a developer testing purchase code and sandbox licence activations. Sandbox activations expire automatically after 24 hours and can also be revoked manually for repeated testing.
Can I migrate only one product first?
Yes, and for many established sellers that is the sensible approach. Launch one product, test checkout, licensing, updates, customer communication and support workflows, then expand when you are comfortable.
Can I change from one-time purchases to subscriptions?
Yes. WPBay supports one-time purchases and monthly or yearly subscriptions. Your treatment of existing customers should still respect what those customers originally purchased, so migration offers should be clearly communicated rather than silently changing an existing licence.
What happens to updates after I migrate?
WPBay licences can receive automatic plugin or theme updates through the WPBay SDK. During a transition, you may also retain the previous update mechanism for legacy customers if they still depend on it.
Does WPBay handle customer payments and VAT after migration?
For new standard marketplace purchases processed through WPBay, WPBay acts as Merchant of Record. It handles checkout, customer billing, payment processing, applicable buyer-facing VAT/tax handling, invoices, refunds under the platform policies and subscription billing where relevant.
Will WPBay migrate my business for me?
The amount of assistance depends on your current platform and technical setup. WPBay provides migration tooling, documentation and direct support, including dedicated Envato workflows. For unusual licensing or business setups, contact WPBay before making assumptions about what can be imported automatically.
Start with one product. Prove the new setup. Move forward from there.
A good migration should feel less like rebuilding your business and more like giving it a second path forward. Keep what still works, move what benefits from moving, protect existing customers and let the new system earn your confidence.