This should have been a core functionality of Plesk since the early days. I have clients with multiple subscriptions (a relic from the Plesk 9 days) who are still stuck with them on Plesk 12 because it is too inconvenient to manually merge all their domains and subscriptions into one.

No ability to have more than one IP address per subscriptions and now this BS. Come on now Parallels? Every site nowadays needs SSL. Get with the program.

@Riz

I've managed to move subscriptions between customers without any issues in Plesk 12.

Let's get a few things right though: A Subscription is actually the domain & associated subdomain(s), the database(s) used, and mail used by said domain. A Customer is the owner of one or multiple subscriptions. The customer can easily manage multiple subscriptions, domains, or whatever else you want to call it.

If it's billing and better client administration you're interested in, go check PBA-S, it's great for new plesk deployments and can easily help your clients manage their current subscriptions. Granted, it does need proper configuration in the beginning, and you MUST import your existing clients manually if you want them to manage their own domains, but after that, it's simply great!

I agree. This is is srely needed. Anyone who manages lots of domain needs to be able to move domains within subscriptions.

It is v12 guys...

Yes this was a very useful feature.

This is a really needed feature. By mistake I created a lot of domains in the same subscription instead of one domain per subscription and I had a lot of domains in one window to manage. I need to move this date between subscriptions (web spaces) easily.

@Anonymous

Hm, which other panels you were moving domains between subscriptions? i.e. were you able to move addon domains between accounts in WHM/cPanel?

Domain is a collection of files in user's account and under user's privileges. While we know docroot - we have no idea where are the other files (which are commonly placed outside). We often cannot tell for sure which database(s) are used in a site. There is also mail involved. Once moved, new privileges need to be assigned which may be quite impacting for a site. Once file locations changed, it breaks every script using absolute paths in its code (common enough for older sites). So this is not super-easy.

Moving domain shall not be confused with moving complete subscription (or "account" in other panels), which is whole different story, and it is easy indeed. This function is available in Plesk for a while already.

This seems like a no brainer, it is part of the other control panels or at least the ones I have used. An admin account should be able to move control of anything now if it actually has to physically move anything isn't important just seems like it would be a matter of ownership and permissions.

The idea is highly suggested and will be very useful.

Clearly not often required, but last week I would have used it twice, if such an function exists.

Why? Following:

User gets an Subscription.
A year later the user would like to add another Domain.
The Tool on the new domain needs an higher PHP-Version or an own IP. BUT the old Domain(s) should stay as they are.

So now you have to do a lot of things (renaming current URL, creating new subscription, copying files, copy DB...)
It would be nice to have just one click or a kind of wizard, helping out with this steps :)

Changed file paths that may cause a problem for *some* websites is an issue that should be handled by webmaster or experienced administrator and out of scope in this question. We are talking here about any meaningful way to move domains between subscriptions (including main domain) or simply merging them. One of the reasons is move from Plesk 9 model - now it's impossible to apply correct hosting plan limits to clients, because they have multiple subscriptions, so providers have to deal with overuses manually.

And I agree that it is clearly understandable that files and folders will be moved to new subscription home directory.

That you feel changed paths is a non-issue is good for you, but for regular shared hosting it is not a non-issue. WordPress, Joomla and almost all other CMS systems have directory path's listed in either their configuration file or in their databases.

It is also not always an easy fix. For example WordPress has some paths saved in serialized form, which have a string length prefixed. If you change the path using search and replace, the string length also changes which has to be reflected in the serialized data.

It is _not_ as simple as running search and replace on a file/database.

We regularly receive requests from customers to merge accounts - usually because they upgrade a subscription to one that allows them to host multiple domains and they want to take advantage of that.

Even if the process was manual (back up the old domain and restore it into the desired subscription) that would be fine. The issue about web paths is a non-issue - partly because we tell customers not to hardcode, but mostly because it's quite an easy fix that is under our/customers control (i.e. not buried inside Plesk/PBAS). The biggest issue we have at the moment is how we would handle migrating over the other features - mail (including lists), databases, applications, etc.

Sergey, as I understand it you can currently rename domains (have been able to for some time) which also caused file path changes. In other words, that's never been a deterring factor in the past.

Merging subscriptions and/or moving domains between subscriptions would be very handy. Particularly when migrating from a Plesk 9 server since individual subscriptions is not even close to what the client was accustomed to before. The closest comparison (in terms of viewing domains within the panel) would be a single subscription with the Client's resource limitations and all domains within that one subscription.

Ability to merge one subscription as a secondary domain of another account would be very handy. Changing document root from /httpdocs to a custom one would be logical and expected in my opinion. If a site is hard coded with file paths (why would you do this?) it will break but most would be compatible, i'm a frequent user and fan of the custom document root functions in plesk. You could also map the old ftp user as a sub-ftp account under the new subscription and link to secondary domains document root so change to would be seamless for ftp user perspective. mail accounts could also be merged as they are unique.

Relocated files are not the only issue here (but is indeed a biggie). Other issues are the lack of per-domain mail settings, for example catch-all's are currently subscription-based instead of domain-based.

What I dearly miss, is the possibility to add a domain name subscription in business manager from a subscriptions existing domains.

I wonder how other CBM users handle billing when a user adds a domain name to an existing hosting subscription but that domain naver gets billed...

Please tell a little how you would see it working?

i.e. if sites are relocated to a different folder (core limitation of a subscription), they could fail because of changed file paths and will require some fixes in site code and configuration. Would it be accepted?