Feature Suggestions

Please provide here your suggestion for new functionality for Plesk. We encourage you to review and vote for suggestions of others. The top-ranked suggestions are likely to be included in the next versions of Plesk.

Please write in English so that voters from all over the world can read and support your request.

For technical assistance, contact Plesk support
For questions, bug reports, discussions and free assistance, check our Forum and Facebook page
For additional information, see Documentation, Knowledge Base and Blog
Follow us on Twitter for more news on Plesk development

Off-topic posts will be removed from here

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Ability to store domain mail content in the domain folder

    Please add the ability to store domain mail content in the domain folder like in cPanel /home/$user/mail/domain.tld/emailuser/

    In this case, it will be possible manually create a backup for website and mail content just by copying /home/$user/ folder and after restore this folder on the destination server.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add possibility for migration from ISPmanager 6 to Plesk

    At the moment it is possible to migrate only from the following ISPmanager versions to Plesk using a CLI method:

    ISPmanager 4 Pro
    ISPmanager 5 Business

    Please add a possibility also to migrate from ISPmanager 6 to Plesk using a CLI method

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Include the hability to migrate Mattermost chat/data of the domains to the new server when using Plesk Migrator Tool

    When migrating a domain to a new server the Mattermost's data/chats present in the old server should also be migrated to the domain in the new server when Plesk Migrator Tool is used, or create a tool that makes it possible.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow selecting specific mailboxes for migration

    Please allow selecting specific mailboxes for transferring with Plesk Migrator

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Allow migrations of accounts between servers that share an external Smartermail server

    As above.

    Currently, it just fails as it tries to create the mail account on the receiving server which already exists on the mail server.

    At the least, you could allow migrations to exclude the entire mail domain and then make an account import tool to bring them into the receiving server.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Database user permission is set according to the database server type

    Migrator should take into account the database server type (remote or local) and change user permissions accordingly. Currently, users that was set on the source with permissions to connect locally to a local database are migrated to the target with the same permissions, despite the fact, that on the target database server is set as a remote. That leads to inability to connect to remote database for that user on the source after migration and migrator change the permission accordingly.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. plesk migrator should lock the domain and service to suspend while migrating

    solution idea 1. rename the index.php per default to index_.php after mirgration is done rename to index.php

    solution idea 2.suspend the domain, i think than its not possibile to access it.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. plesk migrator should plan the scheduled tasks at the end of everything

    the cron could cause putting stuff in the database while the mirgrations of very large databases is running.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  1 comment  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Mail Importing improvement

    Within the "Mail Importing" section it would be helpful to show percentages of work (and other stats) and a remove button to hide old unnecessary import requests.
    Best regards.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Ability to migrate messages of SmarterMail using file copying function

    Currently migration of mail messages performed when SmarterMail v100 is used performed via IMAP protocol. This is slower then simply copying file. Please add ability to migrate messages via simple copying too to speed up migration.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migrations  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base