• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Make service plan available for all...?

HHawk

Regular Pleskian
Hi guys,

We are currently migrating a ton of accounts from several Plesk 12.5.x servers to one single Plesk 12.5.x server. The new server already has a few accounts and also service plans available.

However the problem is, is that the created, or better said, available service plans are selectable for all subscriptions. If I try to change (Change Plan) a subscription's service plan, none of the service plans are being displayed.

Is there a way to make them available for all subscriptions in general? If so, please share.
Or maybe there is another way to do this, other then creating service plans for every single subscription and/or reseller...

Thank you in advance!
 
Im not perfectly sure whether I understand the question, but I think the underlying issue is the assumption, that migrator does not only migrate the subscription, but the service plans, too. That is not the case. Migrator only migrates subscriptions. If you want these subscriptions to be associated with the same service plan on the target server as they were set on the source server, you must first create the service plans on the target server and name them alike the source server, then migrate the subscription. Else subscriptions will be migrated and have the correct settings, but they will not be associated with the appropriate service plan.
 
No you didn't understand me correctly.

1. New server > created new service plans
2. Old server accounts > migrated to new server
3. Assign newly created service plans to the migrated accounts

However 3 will fail as it will show NO service plan whatsoever for the accounts.

Anyways, I think we will migrate these accounts to DirectAdmin. So consider this solved.
Only issues with the Plesk migration anyways and more issues with Plesk in general especially with the self-signed certificate and email clients.
 
I am sorry to hear that you are disappointed. I am sure that there is a solution for the issue. Sometimes it is difficult to understand what a problem is about. And it is even more difficult if not one, but two servers - as in migration - are involved. In your case my first guess would be whether the service plans are global service plans or whether they are associated with a reseller account? If they are global service plans I have not yet seen any issues with assigning plans to subscriptions.
 
Back
Top