[Picflick]

Hi,
I’ve installed MVX and MVX Pro on my staging website and receive this error on the backend:
“The MultiVendorX Pro API Key has not been activated, so the plugin is inactive! Click here to activate MultiVendorX Pro.”
But when I navigate there, it shows me it’s activated: https://prnt.sc/BorJ9nMWj0BI
Please advise because none of my existing memberships are listed – https://prnt.sc/TTXqY0gAbssh
Thanks, PicFlick

[Sangita Support Squad]

Hi there,

To access the Pro features, you’ll first need to activate your MultiVendorX Pro license on your site. Please use your API credentials from the following page to activate the license:

https://multivendorx.com/my-account/api-keys/

Once the license has been activated successfully, you will be able to use all the Pro features.

If you have any further questions or need any assistance from our end, please let us know. We’re always happy to help.

[Picflick]

I showed you a screenshot of the page in our wp-admin where it says that the license is activated, yet no pro features are available. There is also no ‘activate’ button to reactivate it with the API keys.

As per your email, when navigating to https://multivendorx.com/my-account/api-keys/ there is no option to remove the existing activation – see https://ibb.co/8JzCmr3

[Sangita Support Squad]

This does seem unusual.

Could you please try deactivating MultiVendorX Pro and then activating it again? After that, check whether you’re able to activate the license successfully.

If the issue still persists, please share temporary admin access with us so we can investigate it further and assist you more effectively. When sharing the credentials, kindly mark your reply as private to keep the information secure.

We look forward to your update and are happy to assist further.

[Picflick]

That still didnt work. As requested, credentials below.
I must add that it is incredibly frustrating how there’s consistently issues with MVX. You advised that that upgrade path would be seamless and simple, yet I cant even progress past the 1st step of updating the plugin itself. This brings serious reliability concerns with using the plugin, especially with V5.0 which I raised when you announced it in December 2025.
Can you please sort out this issue and advise the exact steps followed, because I need to replicate it on my live website and will surely encounter the same issues.
Regards,
PicFlick

[Picflick]

This reply has been marked as private.

[Sangita Support Squad]

Hi there,

First of all, we sincerely apologize for the inconvenience and confusion caused.

We investigated the license activation issue and identified the cause. It turns out that this is not actually a problem with the plugin itself.

For staging sites, license activation is not required. Licenses are only intended to be activated on live/production sites. Because of this, the behavior you experienced on your staging environment is expected.

You can continue testing the plugin on your staging site without activating the license. Once you’re ready to deploy to your live site, you can activate the license there as usual.

To help prevent similar confusion in the future, we will also discuss adding a clearer indication within the plugin when it is running on a staging environment.

Once again, we sincerely apologize for the inconvenience this caused. If you have any further questions or encounter any other issues, please don’t hesitate to reach out. We’re always happy to help.

[Picflick]

I cant continue testing because my memberships were not migrated over. Please see: https://ibb.co/DD5MMLVg

So this is a problem!

To explain the steps I followed:
1. Upgraded MVX
2. Upgraded MVX Pro
3. Navigated to Memberships to view if my existing memberships were there and nothing shows

So none of my membership levels were migrated over. Over the past 6 months, all your marketing for MVX5.0 promises that the migration path from the previous version is simple, easy, and will work.

While you fix this for me, what other data objects do I need to check please.

Thanks, PicFlick

[Sangita Support Squad]

Hi there,

We completely understand your concern, and we’d like to explain the reason behind these changes.

Starting with **MultiVendorX Pro 2.0.0**, we completely redesigned the architecture of the Membership module. This update was necessary to align the module with the latest API structures and requirements of both **PayPal** and **Stripe**, ensuring better compatibility, improved reliability, and smoother subscription management going forward.

With the new architecture, whenever you create a membership plan and configure either the PayPal Marketplace or Stripe Marketplace payment gateway, a corresponding subscription product is automatically created within the selected payment gateway. When a customer purchases that membership, a matching subscription is also created on the payment gateway, and all future renewals are managed directly by the payment gateway itself.

Since the entire subscription flow and data structure have changed significantly in this new implementation, the previous membership plans are not compatible with the new system. For this reason, we were unable to provide a migration process for existing membership plans, as migrating them could have resulted in inconsistencies with the subscription data maintained by the payment gateways.

We understand that recreating the membership plans may require some additional effort, and we truly appreciate your understanding. These changes have been made to provide a more stable, secure, and future-proof subscription system.

If you have any questions or need any assistance while setting up your membership plans, please let us know. We’ll be more than happy to help you through the process.

[Picflick]

Hi,

This response is extremely concerning.

You’re effectively confirming that there is no migration path whatsoever for existing vendors, despite months of messaging around MVX 5.0 stating that upgrading would be straightforward.

My concern is not recreating the membership plans themselves. That is relatively minor. The real issue is that I have 100+ existing vendors on active legacy membership subscriptions. Are you saying there is no supported mechanism to migrate those vendors to the new Membership system?

I am not going to ask 100+ paying vendors to cancel and re-subscribe. Likewise, I am not prepared to manually recreate subscriptions or manually migrate vendors one by one. That is not a realistic solution. This is a fundamental upgrade requirement. If the Membership module has been completely redesigned, then there should be a supported migration strategy for existing vendors, particularly when the upgrade has been promoted as the future of the platform.

Can you please answer the following directly – How does MultiVendorX expect existing sites with active vendor subscription to migrate to the new system? What is MultiVendorX’s recommended approach?

At the moment, this effectively blocks my upgrade to MVX 5.0. A platform upgrade that leaves existing subscription businesses without a supported migration path is not an acceptable upgrade path.

Regards,
PicFlick

[Sangita Support Squad]

I completely understand your concern, and I appreciate your patience and understanding in this matter.

As mentioned in the previous reply, the module’s architecture has undergone significant changes with the update, which is why the behavior differs from earlier versions. That said, I understand how important this is for your workflow.

I have already shared your feedback and concerns with our development team, and we are actively reviewing the best possible approach. I will keep you informed of any updates and share further information as soon as I hear back from the team.

Thank you again for your continued cooperation.

[Picflick]

Hi,
Any feedback on the above please.
Thanks,

[Sangita Support Squad]

Hello,

We completely understand that this is a significant change for existing users, and we appreciate your concern regarding the migration process.

With the latest Membership module, we have adopted the newer subscription architecture supported by Stripe and PayPal. Due to the way these payment gateways handle subscription data, subscriptions created under the previous system cannot be automatically migrated to the new one. Unfortunately, neither Stripe nor PayPal provides a mechanism to seamlessly transfer existing subscriptions from the old architecture to the latest supported model.

We have carefully evaluated the possible approaches, and at this time, a direct migration of existing subscriptions is not technically feasible through the payment gateways themselves.

To help ease the transition, we can provide an option that allows you to manually assign an equivalent membership level to your existing stores so they can continue accessing the platform without interruption. and manage future upgrades or plan changes through the new subscription system without any issues.

However, please note that manually assigned plans are not recurring subscription plans. Due to the limitations of the payment gateways, recurring subscriptions cannot be assigned by the admin. If a store needs to be enrolled in a recurring paid membership plan, the store owner must subscribe to that plan themselves through the normal checkout process. This ensures that the recurring subscription is properly created and managed by Stripe or PayPal.

Once a store has subscribed through the new subscription system, they will be able to manage future renewals, upgrades, or plan changes without any issues.

We understand that this may require additional effort, and we truly appreciate your understanding. Our team is committed to assisting you throughout the transition and ensuring the process is as smooth as possible.

[Author]

Posts