How to sync content between source and destination servers after migration

Refers to:

  • Plesk 12.5 for Linux
  • Plesk Onyx for Linux
  • Plesk Onyx for Windows
  • Plesk 12.5 for Windows


2016-11-16 13:15:01 UTC


2017-03-23 14:39:15 UTC


Was this article helpful?

Have more questions?

Submit a request

How to sync content between source and destination servers after migration


How to sync files, emails and databases content between the source and the destination servers after migration?


The synchronization helps to update already migrated data with the data from the source server when DNS is not yet switched.

Starting from Plesk Migrator Extension of version 2.0, data synchronization for the migrated subscriptions can be launched from Plesk interface ("Re-sync" option, available from "Overview" and "Subscription List" tabs):


When re-sync is done, it will bring in only files and mail that were created or updated on sources after migration started. Databases are re-migrated completely.

Also, it is possible to synchronize the content via command-line:

Synchronizing all content

To sync all domains content use the following commands:


# cd /usr/local/psa/var/modules/panel-migrator/sessions/<session_dir_name>/
# /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator copy-content


cd C:\\Program Files (x86)\\Plesk\\var\\modules\\panel-migrator\\sessions\\<session_dir_name>
"%plesk_dir%/admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-content

If initial migration was done through GUI, it is required to modify config.ini file in order to synchronize content through CLI. Add the following line in both [plesk] for target and [source] for source server directives in %plesk_dir%\\var\\modules\\panel-migrator\\conf\\config.ini file:

windows-password-type = "plain"

As a result, config.ini will look like:

target-type = "plesk"
session-dir = "<session_dir_name>"
skip-log-priority-check = "1"
skip-migrator-updates = "1"
skip-set-session-directory-permissions = "1"
use-separate-log = "1"
source-type = "plesk"
sources = "source"
skip-rpc-agent-deployment = "false"
adjust-applications = "true"

ip = ""
os = "windows"
windows-username = "Administrator"
windows-password = "*******"
windows-password-type = "plain"

ip = ""
os = "windows"
windows-username = "Administrator"
windows-password = "*******"
windows-password-type = "plain"
session-dir = "C:\\panel_migrator"
copy-mail-content = "full"
copy-web-content = "full"
copy-db-content = "full"

data-import-type = "selected"
timing-policy = "false"
resync-content = "true"
operability-check = "true"

Otherwise, the following error will appear:

"%plesk_dir%/admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-content
[INFO] Initialize Plesk Migrator
[INFO] Load configuration
[ERROR] The encrypted password is specified in the configuration option 'windows-password' of section 'plesk'. Migration with encrypted passwords is not supported by CLI interface. Replace the encrypted password by plain one (also change the password type to "plain") or set up the plain password in the environment variable 'PLESK_WINDOWS_PASSWORD'.

Synchronizing content separately

Also the content can be synchronized separately. There are three types of content:

  • Mail content
  • Database content
  • Web content

During the Mail content synchronization, all mail content is copied from the source server. New mail on the destination server will not be overwritten.

During the Database content synchronization, the content of a user's database (MySQL/MSSQL) on the destination server is replaced by the content from the source server.

During the Web content synchronization, the files on the destination server are replaced by the ones from the source server.

For the specific type of the content, use the options copy-web-content , copy-mail-content , copy-db-content to sync web, mail and database content accordingly.

Note : such commands synchronize already migrated objects' content. If, during or after migration, a new database or mail account is created, it will not be synchronized.

To sync the content of certain domains only, use the following instruction:

  • Prepare the migration list containing domains that should be synchronized.

    The list format should be as follows:

    Customer: customer
  • Plesk Migrator should be pointed to that migration list directly when executed. For example, to sync web content:


    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator copy-web-content --migration-list-file <path-to-the-migration-list>


    "%plesk_dir%admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-web-content --migration-list-file <path-to-the-migration-list>

Additional information

For information about starting migration from CLI, refer to Plesk Migration Guide .

Have more questions? Submit a request


  • 0
    poh inah


    Can you say, what does mean these asterisks in the string below?

    cd C:\\Program Files (x86)\\Plesk\\var\\modules\\panel-migrator\\sessions\\*****
    C:\\Program Files (x86)\\Plesk\\var\\modules\\panel-migrator\\sessions\\*****>"%plesk_dir%admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-content
  • 0
    Anton Maslov

    @poh inah thank you for the comment!**** - means directory name for the specific session, changed to <session_dir_name> to make the article more

    **** - means directory name for the specific migration session, changed to <session_dir_name> to make the article more informative.

Please sign in to leave a comment.