{"id":1090,"date":"2021-07-23T12:45:16","date_gmt":"2021-07-23T12:45:16","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/transfer-tool\/"},"modified":"2021-07-23T12:45:16","modified_gmt":"2021-07-23T12:45:16","slug":"transfer-tool","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/transfer-tool\/","title":{"rendered":"Transfer Tool"},"content":{"rendered":"<\/p>\n
\n
\n
\n

Valid for versions 94 through the latest version<\/em><\/p>\n<\/div>\n

\n

Version:<\/h4>\n

82<\/h4>\n

84<\/h4>\n

88<\/h4>\n

90<\/h4>\n

92<\/h4>\n

94<\/h4>\n<\/div><\/div>\n
\n

Overview<\/h2>\n

This interface copies multiple accounts from a remote server to your cPanel & WHM server. To transfer accounts, you must<\/strong> obtain the following:<\/p>\n

    \n
  • root<\/code>-level privileges with the su<\/code> or sudo<\/code> commands.<\/li>\n<\/ul>\n
    \n
    Warning:<\/div>\n
    \n
      \n
    • \n

      Do not<\/strong> shut down or restart any processes on either server during the transfer and restoration process.<\/p>\n<\/li>\n

    • \n

      Do not<\/strong> start a transfer during a system update (upcp<\/code>) or start a system update during a transfer. The system update will fail.<\/p>\n<\/li>\n

    • \n

      The Transfer Tool<\/em> feature replaces<\/strong> the source server\u2019s files with the target server\u2019s zone files when the following conditions are true:<\/p>\n

        \n
      • \n

        The target server resides in the same Domain Name System (DNS) cluster as the source server.<\/p>\n<\/li>\n

      • \n

        The source server and the DNS nodes use the Synchronized Changes<\/em> DNS role.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

      • \n

        The Transfer Tool<\/em> feature does not<\/strong> transfer the DNS zone templates. If custom DNS zone templates exist on the remote server, the system ignores these zone templates when it recreates the account on the destination server. For more information, read the transfer process section below.<\/p>\n<\/li>\n

      • \n

        You must<\/strong> remove Domain Server (DS) records from the domain registrar before you transfer a domain that uses DNSSEC. After you transfer the domain, you need to re-add the DS records to the registrar for the domain. For more information about the process, read the DNSSEC key transfer section of our DNSSEC documentation.<\/p>\n<\/li>\n

      • \n

        Account transfers process AAAA records differently than A records.<\/p>\n<\/li>\n

      • \n

        The target server will not<\/strong> alter AAAA records that point to servers other than the source server or servers related to the source.<\/p>\n<\/li>\n

      • \n

        A target server without IPv6 enabled will strip locally-managed AAAA records that pointed to the source server.<\/p>\n<\/li>\n

      • \n

        A target server with IPv6 enabled will point any source-related AAAA record to the account\u2019s shared IPv6 address in the domain\u2019s locally-managed zone file.<\/p>\n<\/li>\n

      • \n

        In cPanel & WHM version 70 and later, the server disregards the Restrict document roots to public_html<\/em> Tweak Setting<\/em> setting during server transfers. The transfer tool retains any pre-transfer public_html\/<\/code> directory structures, even those that place addon and subdomains document roots outside of the primary website\u2019s document root. However, after the transfer, addon and subdomains that the restored user creates will adhere to this setting.<\/p>\n<\/li>\n

      • \n

        Do not<\/strong> use the skip-name-resolve<\/code> setting in your server\u2019s MySQL\u00ae configuration. This setting can cause problems on any server. It will create more<\/strong> problems on remote MySQL servers during account transfers.<\/p>\n<\/li>\n

      • \n

        The source and target servers must<\/strong> be able to communicate over port 2087<\/code> to use this feature. For more information about the ports that cPanel & WHM uses, read our How to Configure Your Firewall for cPanel & WHM Services documentation.<\/p>\n<\/li>\n

      • \n

        Due to networking requirements, you cannot<\/strong> run an IPv6-only cPanel & WHM server. You must<\/strong> have at least one IPv4 address.<\/p>\n<\/li>\n

      • \n

        This feature does not<\/strong> transfer Two-Factor Authentication (2FA) configuration information for an account. The user will need to reconfigure 2FA on the new server.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n

        \n
        Note:<\/div>\n
        \n
          \n
        • \n

          If you experience problems with session timeouts, increase the number of seconds in the Number of seconds an SSH connection related to an account transfer may be inactive before timing out<\/em> setting in the System<\/em> section of WHM\u2019s Tweak Settings<\/em> interface (WHM >> Home >> Server Configuration >> Tweak Settings<\/em>).<\/p>\n<\/li>\n

        • \n

          If one of the accounts that you wish to transfer uses Microsoft\u00ae FrontPage\u00ae on the remote server, we strongly<\/strong> recommend that you disable FrontPage for that account before you attempt to transfer the account. cPanel & WHM versions 11.46 and later do not<\/strong> support FrontPage, and the restoration process does not<\/strong> restore FrontPage-specific files and directories.<\/p>\n<\/li>\n

        • \n

          If you only<\/strong> possess user credentials and do not<\/strong> have root<\/code> access or privileges, use WHM\u2019s Transfer or Restore a cPanel Account<\/em> interface (WHM >> Home >> Transfers >> Transfer or Restore a cPanel Account<\/em>).<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n

          Important notes about account transfers from Plesk<\/h3>\n

          The system will not transfer any email addresses from Plesk to cPanel & WHM that contain a plus sign (+<\/code>) in the email username. The system will also not transfer any FTP accounts that contain an underscore (_<\/code>) in the username.<\/p>\n

          To transfer accounts from Plesk, first change any forwarded domains to physical hosting accounts. To do this, run the following command as the root<\/code> user:\n<\/p>\n

          \n
          \/usr\/local\/psa\/bin\/domain --update example.com -hst_type phys -login \"example\"<\/span> -hosting true -ip 127<\/span>.0.0.1 -passwd \"12345luggage\"<\/span><\/code><\/pre>\n<\/div>\n
            \n
          • \n
            example.com<\/code> represents the forwarding domain.<\/p>\n<\/li>\n
          • \n
            example<\/code> represents the new account\u2019s username.<\/p>\n<\/li>\n
          • \n
            127.0.0.1<\/code> represents the new account\u2019s IP address.<\/p>\n<\/li>\n
          • \n
            12345luggage<\/code> represents the new account\u2019s password.<\/p>\n<\/li>\n<\/ul>\n
            If you need to convert several forwarding domains into hosting accounts, open a support ticket and our migration team will contact you.<\/p>\n
            IP address transfers<\/h3>\n
            To transfer IP addresses from one server to another, use WHM\u2019s IP Migration Wizard<\/em> IP Migration Wizard<\/em> interface (WHM >> Home >> IP Functions >> IP Migration Wizard<\/em>).<\/p>\n
            If the IP address is the server\u2019s main IP address, you must<\/strong> also update your cPanel license\u2019s IP address. You can update your license\u2019s IP address through Manage2, if you use it, or through the cPanel Store.<\/p>\n
            \n
            Important:<\/div>\n
            \n
            You can only<\/strong> transfer a cPanel license to an IP address that does not<\/strong> already possess a cPanel license.<\/p>\n<\/p><\/div>\n<\/div>\n
            Transfer via Manage2<\/h4>\n
            If you purchased your license via Manage2, perform the steps in our Transfer a License documentation.<\/p>\n
            Transfer via cPanel Store<\/h4>\n
            If you purchased your license directly from cPanel, L.L.C., perform the following steps:<\/p>\n
              \n
            1. \n
              Log in to your cPanel Store account.<\/p>\n<\/li>\n
            2. \n
              Click My Account<\/em>. The My Account<\/em> interface will appear.<\/p>\n<\/li>\n
            3. \n
              Under Orders\/Licenses<\/em>, click View my licenses. The Manage Licenses<\/em> interface will appear.<\/p>\n<\/li>\n
            4. \n
              Select the checkbox for the license that you wish to transfer.<\/p>\n<\/li>\n
            5. \n
              Click Edit IP<\/em>. The Change IP Address<\/em> dialog box will appear.<\/p>\n<\/li>\n
            6. \n
              Enter the license\u2019s new IP address in the New IP Address<\/em> text box.<\/p>\n<\/li>\n
            7. \n
              Click Save Changes<\/em>.<\/p>\n<\/li>\n<\/ol>\n
              If you experience any issues with the transfer, open a support ticket.<\/p>\n
              How to transfer and restore multiple accounts<\/h2>\n
              Remote server information<\/h3>\n
              This section of the Transfer Tool<\/em> interface allows you to specify information about the remote server (the server from which to transfer accounts).<\/p>\n
                \n
              1. \n
                In the Remote Server Address<\/em> text box, enter an IP address or a Fully Qualified Domain Name (FQDN).<\/p>\n
                  \n
                • \n
                  IP address example<\/strong> \u2014 127.0.0.1<\/code><\/p>\n<\/li>\n
                • \n
                  FQDN example<\/strong> \u2014 host.example.com<\/code><\/p>\n
                  \n
                  Note:<\/div>\n
                  \n        In this case, the FQDN does not<\/strong> require the trailing dot.\n    <\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                • \n
                  In the Remote SSH port<\/em> text box, specify the port to use.<\/p>\n
                  \n
                  Note:<\/div>\n
                  \n
                  The default value for SSH is port 22<\/code>.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ol>\n
                  Authentication<\/h3>\n
                  In this section of the Transfer Tool<\/em> interface, specify the authentication method with which to log in to the remote server.<\/p>\n
                  To specify an authentication method, perform the following steps:<\/p>\n
                    \n
                  1. \n
                    Select whether to log in as the root<\/code> user or with a specific username.<\/p>\n
                    \n
                    Note:<\/div>\n
                    \n
                    If the PermitRootLogin<\/code> value equals no<\/code> in the sshd_config<\/code> file on the remote server, you must<\/strong> log in as a user other than the root<\/code> user and then escalate to the root<\/code> user.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                  2. \n
                    If you selected User for Login<\/em>, perform the following actions:<\/p>\n
                      \n
                    • Enter the remote account\u2019s username in the Username<\/em> text box.<\/li>\n
                    • Enter the remote account\u2019s password in the Password<\/em> text box.<\/li>\n<\/ul>\n<\/li>\n
                    • \n
                      Use the Authentication Method<\/em> menu to specify whether to use a password or an SSH key pair to authenticate to the remote server.<\/p>\n
                        \n
                      • \n
                        If you select Password<\/em>, enter the password for the account in the Password<\/em> text box.<\/p>\n<\/li>\n
                      • \n
                        If you select SSH Public Key<\/em>, select the key pair to use during authentication. Make certain that you installed the appropriate key pair in WHM\u2019s Manage root\u2019s SSH Keys<\/em> interface (WHM >> Home >> Security Center >> Manage root\u2019s SSH Keys<\/em>).<\/p>\n
                        \n
                        Note:<\/div>\n
                        \n
                          \n
                        • If you encrypted your account\u2019s SSH key pair, enter the SSH Key Passphrase<\/em>.<\/li>\n
                        • If you\u2019re experiencing firewall issues, use the Password<\/em> method instead.<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                        • \n
                          Optionally:<\/p>\n
                            \n
                          • \n
                            If you select User under Login<\/em>, select a root<\/code> escalation method under the Root Escalation Method<\/em> heading.<\/p>\n<\/li>\n
                          • \n
                            If you select su<\/em> for the Root Escalation Method<\/em>, enter the root<\/code> password in the Root Password<\/em> text box.<\/p>\n<\/li>\n
                          • \n
                            To bypass TLS verification, select the I understand the risks. Connect anyway.<\/em> checkbox and then click Continue<\/em>.<\/p>\n
                            \n
                            Warning:<\/div>\n
                            \n
                            We strongly<\/strong> recommend that you do not<\/strong> use this option. Only<\/strong> use this option if you can confirm the identity of the source server.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
                            Security<\/h3>\n
                            \n
                            Warning:<\/div>\n
                            \n
                            This feature is experimental<\/strong>. Do not<\/strong> consider it an effective security control. Exercise extreme<\/strong> caution when using the Restricted Restore<\/em> feature.<\/p>\n<\/p><\/div>\n<\/div>\n
                            In this section of the Transfer Tool<\/em> interface, select whether to use the Restricted Restore<\/em> feature or copy reseller privileges. The Restricted Restore<\/em> feature lets the system perform extra security checks on the archive file. If part of the file has a security issue, the system will not<\/strong> restore that part of the archive file. This helps mitigate the risk of transfers from unfamiliar sources. The system enables this feature by default.<\/p>\n
                            If you do not trust the source of the account backup with root<\/code> access to your server, use the Restricted Restore<\/em> feature to protect your server.<\/p>\n
                            Warnings about the Restricted Restore feature<\/h4>\n
                            If you use the Restricted Restore<\/em> feature, be advised that:<\/p>\n
                              \n
                            • When you restore an account with this feature, the system may leave behind unnecessary account data. This can cause conflicts and leave the account in a broken state. You must remove the account and then restore it without<\/strong> using the Restricted Restore<\/em> feature.<\/li>\n
                            • The Restricted Restore<\/em> feature will not<\/strong> restore reseller privileges. If you wish to add reseller privileges to a transfered account, use WHM\u2019s Reseller Center<\/em> interface (WHM >> Home >> Resellers >> Reseller Center<\/em>).<\/li>\n
                            • This feature will not<\/strong> restore parked (aliased) or addon domains.<\/li>\n
                            • This feature only<\/strong> allows restored accounts to use noshell<\/code> or jailshell<\/code> environments. If the restored account uses another shell, the system will set the account to use noshell<\/code> environment.<\/li>\n
                            • If you use this feature to restore an account that contains PostgreSQL\u00ae databases, the target server must<\/strong> use PostgreSQL version 8.4 or newer.<\/li>\n<\/ul>\n
                              Advanced<\/h3>\n
                              This section of the Transfer Tool<\/em> interface provides advanced settings for the transfer. Click Show<\/em> to display the list of settings.<\/p>\n
                              To select the advanced settings, perform the following steps:<\/p>\n
                                \n
                              1. \n
                                From the Remote Server Type<\/em> menu, select the web control panel that the remote server runs. Choose from the following settings:<\/p>\n
                                  \n
                                • \n
                                  Auto Detect<\/em><\/p>\n<\/li>\n
                                • \n
                                  cPanel & WHM<\/em><\/p>\n<\/li>\n
                                • \n
                                  DirectAdmin<\/em><\/p>\n<\/li>\n
                                • \n
                                  Ensim (Parallels Pro)<\/em><\/p>\n<\/li>\n
                                • \n
                                  Plesk<\/em><\/p>\n<\/li>\n<\/ul>\n<\/li>\n
                                • \n
                                  Select Unencrypted<\/em> to use an unencrypted session to transfer the files.<\/p>\n<\/li>\n
                                • \n
                                  Select Compressed Transfers<\/em> to compress the files during the rsync process when the remote server transfers the files between the remote and destination servers.<\/p>\n
                                  \n
                                  Note:<\/div>\n
                                  \n
                                  This setting does not<\/strong> affect the package account function, which creates a gzip<\/code> archive of the user\u2019s account on the remote server.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                • \n
                                  Select Low Priority<\/em> to use less CPU and input\/output (I\/O) on the remote server.<\/p>\n
                                  \n
                                  Note:<\/div>\n
                                  \n
                                  This setting reduces the impact on performance on the remote server, but increases the duration of the transfer session.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                • \n
                                  Select Use Incremental Backups speed-up<\/em> to decrease the amount of time that the system uses to package the account on the remote server. If a daily incremental backup exists, WHM uses that backup as a starting point. The system then updates the package before transfer.<\/p>\n<\/li>\n
                                • \n
                                  Select Use custom account packaging modules from \/var\/cpanel\/lib\/Whostmgr\/Pkgacct<\/em> to use packaging scripts in that directory.<\/p>\n
                                  \n
                                  Important:<\/div>\n
                                  \n
                                  The system does not<\/strong> create the \/var\/cpanel\/lib\/Whostmgr\/Pkgacct<\/code> directory by default. You must create the \/var\/cpanel\/lib\/Whostmgr\/Pkgacct<\/code> directory before<\/strong> you select this setting, if the directory does not already exist.<\/p>\n<\/p><\/div>\n<\/div>\n
                                  \n
                                  Note:<\/div>\n
                                  \n
                                  cPanel & WHM always prioritizes custom restore modules in the \/var\/cpanel\/perl\/Whostmgr\/Transfers\/Systems<\/code> directory over the cPanel-provided modules in the \/usr\/local\/cpanel\/Whostmgr\/Transfers\/Systems<\/code> directory.<\/p>\n
                                    \n
                                  • \n
                                    The \/var\/cpanel\/perl\/Whostmgr\/Transfers\/Systems<\/code> directory stores any custom modules that you create.<\/p>\n<\/li>\n
                                  • \n
                                    The \/usr\/local\/cpanel\/Whostmgr\/Transfers\/Systems<\/code> directory stores the modules that ship with cPanel & WHM.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
                                  • \n
                                    Specify the number of CPU processes (threads) for the transfer session in the Number of Transfer Threads<\/em> text box.<\/p>\n
                                    \n
                                    Note:<\/div>\n
                                    \n
                                    This setting defaults to a number of processes (threads) based on the available amount of memory and number of CPUs. You can specify a maximum value of five, but the system may still automatically reduce that number based on available resources.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                  • \n
                                    Specify the number of CPU processes (threads) for the restore session in the Number of Restore Threads<\/em> text box.<\/p>\n
                                    \n
                                    Note:<\/div>\n
                                    \n
                                    This setting defaults to a number of processes (threads) based on the available amount of memory and number of CPUs. You can specify a maximum value of five, but the system may still automatically reduce that number based on available resources.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                  • \n
                                    Enter the number of seconds that the transfer session remains open before it times out in the Transfer Session Timeout<\/em> text box.<\/p>\n
                                    \n
                                    Important:<\/div>\n
                                    \n
                                    If you change the default in the Transfer Session Timeout<\/em> text box, it will only apply to the current session. You must<\/strong> enter a new value each time that you run a transfer. You can permanently change the value in WHM\u2019s Tweak Settings<\/em> interface (WHM >> Home >> Server Configuration >> Tweak Settings<\/em>).<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                  • \n
                                    After you make your selections, click Scan Remote Server<\/em>. A new interface will appear.<\/p>\n<\/li>\n<\/ol>\n
                                    The Account List interface<\/h2>\n
                                    The top of the Account List<\/em> interface displays information about the source server. If any of this information appears incorrect, click Rescan Source Server<\/em>.<\/p>\n
                                    Below the source server information, the interface displays if any available IP addresses exist.<\/p>\n
                                    \n
                                    Warning:<\/div>\n
                                    \n
                                    If no available IP addresses exist on the target server, accounts on the source server that use a dedicated IP address will not<\/strong> transfer.<\/p>\n<\/p><\/div>\n<\/div>\n
                                    Accounts<\/h3>\n
                                    This tab allows you to transfer cPanel accounts to this server.<\/p>\n
                                    How to copy accounts<\/h4>\n
                                    To copy accounts, perform the following steps:<\/p>\n
                                      \n
                                    1. \n
                                      Select the checkbox for each cPanel account that you wish to transfer.<\/p>\n
                                        \n
                                      • \n
                                        To copy all of the accounts that the interface currently displays, select the checkbox at the top of the column in the table header.<\/p>\n<\/li>\n
                                      • \n
                                        Use the Search<\/em> text box to filter the list of accounts.<\/p>\n<\/li>\n
                                      • \n
                                        Click a column header to sort the accounts by that column.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
                                      • \n
                                        By default, the system adopts the username from the source server. To specify a new username, enter the new username in the User<\/em> text box.<\/p>\n
                                        \n
                                        Note:<\/div>\n
                                        \n
                                        The User<\/em> text boxes display the following colors as warning indicators:<\/p>\n
                                          \n
                                        • \n
                                          A red highlight indicates that the username or domain already exists on this server. The account will fail to transfer if you do not change the username, select Overwrite<\/em>, or select Overwrite with delete<\/em>. You cannot transfer an account that uses the same domain.<\/p>\n<\/li>\n
                                        • \n
                                          A green checkmark (\"checkmark\") indicates that the account does not already exist.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
                                        • \n
                                          Select the accounts to which the system will assign dedicated IP addresses under the Dedicated IP Address<\/em> heading. The interface will select the Dedicated IP checkbox for accounts that currently use a dedicated IP address.<\/p>\n
                                          \n
                                          Warning:<\/div>\n
                                          \n
                                          You can only<\/strong> assign available dedicated IP addresses from your server. If your server doesn\u2019t have the required number of available IP addresses, the transfer will fail.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                        • \n
                                          Click Default<\/em> to show the What to Transfer<\/em> section. The following settings will appear:<\/p>\n
                                            \n
                                          • \n
                                            Home Directory<\/em> \u2014 Transfer the account\u2019s home directory.<\/p>\n
                                            \n
                                            Note:<\/div>\n
                                            \n
                                            When you transfer the home directory, the system checks whether it can run the rsync<\/code> command. If the system does not find an error, it will rsync the home directory when the system completes the transfer.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                          • \n
                                            Reseller Privileges<\/em> \u2014 Retain the account\u2019s reseller privileges.<\/p>\n<\/li>\n
                                          • \n
                                            Databases<\/em> \u2014 Transfer the account\u2019s databases.<\/p>\n<\/li>\n
                                          • \n
                                            Bandwidth Data<\/em> \u2014 Transfer the account\u2019s bandwidth data.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
                                          • \n
                                            Click Default<\/em> to show the Live Transfer<\/em> section.<\/p>\n
                                            \n
                                            Note:<\/div>\n
                                            \n
                                              \n
                                            • \n
                                              For more information, read the Live transfer section below.<\/p>\n<\/li>\n
                                            • \n
                                              If your source server uses cPanel & WHM version 88 or earlier, you will see the Express Transfer<\/em> setting instead.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
                                            • \n
                                              If your server uses a linked node, click Default<\/em> to show the Linked Node Options<\/em> section. The following settings will appear:<\/p>\n
                                                \n
                                              • \n
                                                Use only this server. Transfer or restore locally.<\/em> \u2014 Transfer the account to the local server.<\/p>\n<\/li>\n
                                              • \n
                                                Use the cPanel account\u2019s package configuration.<\/em> \u2014 Attempt to use the source account\u2019s currently linked node. If that fails, or if the account does not<\/strong> use a linked node, the system will restore the account to the local server.<\/p>\n<\/li>\n
                                              • \n
                                                The alias and hostname of an existing cPanel & WHM server node. For example, mailserver (mailnode.example.com)<\/em>. \u2014 Transfer the account\u2019s mail services to the selected linked node.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
                                              • \n
                                                Click Apply<\/em> to save the What to Transfer<\/em> and Linked Node Options<\/em> settings for this account. You can click Apply to other selected accounts<\/em> to apply these settings to all currently selected accounts. To apply the default settings for this account, click Reset<\/em>.<\/p>\n<\/li>\n
                                              • \n
                                                The Overwrite<\/em> column displays a menu that allows you to overwrite local data for the transfer.<\/p>\n
                                                  \n
                                                • \n
                                                  Do Not Overwrite<\/em> \u2014 Do not<\/strong> perform an overwrite.<\/p>\n<\/li>\n
                                                • \n
                                                  Overwrite<\/em> \u2014 Overwrite the home directory on the destination server with the contents of the source server. Do not<\/strong> delete any other files or directories on the destination server.<\/p>\n<\/li>\n
                                                • \n
                                                  Overwrite with Delete<\/em> \u2014 Overwrite the home directory on the destination server with the contents of the source server. Delete<\/strong> all files and directories on the destination server that don\u2019t exist on the source server.<\/p>\n
                                                  \n
                                                  Warning:<\/div>\n
                                                  \n
                                                  This setting will overwrite or delete all<\/strong> files on the destination server for the cPanel account. You cannot<\/strong> reverse this action. We strongly<\/strong> recommend that you first create a backup of the account.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                                                • \n
                                                  Click Copy<\/em>. The Account Transfer<\/em> interface will appear.<\/p>\n<\/li>\n<\/ol>\n
                                                  SNI information<\/h5>\n
                                                  \n
                                                  Important:<\/div>\n
                                                  \n
                                                  To transfer SNI information, you must<\/strong> select the Home Directory<\/em> setting.<\/p>\n<\/p><\/div>\n<\/div>\n
                                                  If you do not<\/strong> select the Home Directory<\/em> setting, the system will not<\/strong> add the necessary SNI information to Dovecot\u2019s configuration files. To manually configure SNI information in Dovecot\u2019s configuration files after an alternative transfer of home directories, run the following command:<\/p>\n
                                                  \n
                                                  \/usr\/local\/cpanel\/scripts\/build_mail_sni --rebuild_dovecot_sni_conf --restartsrvs<\/code><\/pre>\n<\/div>\n
                                                  Accounts will retain their mailbox format settings from the source server. For example, if an account uses the maildir format on the source server, it will use the maildir format on the target server.<\/p>\n
                                                  Packages<\/h3>\n
                                                  In this section of the Account List<\/em> interface, select the packages on the remote server to copy to your local server.<\/p>\n
                                                  How to copy packages<\/h4>\n
                                                  \n
                                                  Note:<\/div>\n
                                                  \n
                                                  The Transfer Tool<\/em> feature transfers feature lists for the packages that you select.<\/p>\n<\/p><\/div>\n<\/div>\n
                                                  To copy a package, perform the following steps:<\/p>\n
                                                    \n
                                                  1. \n
                                                    Select the packages that you wish to copy.<\/p>\n
                                                      \n
                                                    • \n
                                                      Select the checkbox in the table header to select all of the packages from the remote server.<\/p>\n<\/li>\n
                                                    • \n
                                                      Use the Search<\/em> text box to filter the list of packages.<\/p>\n<\/li>\n
                                                    • \n
                                                      Use the navigation controls to page through the list of packages.<\/p>\n<\/li>\n
                                                    • \n
                                                      Click a column header to sort the packages by that column.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
                                                    • \n
                                                      Click Copy<\/em>.<\/p>\n
                                                      \n
                                                      Important:<\/div>\n
                                                      \n
                                                      This will also transfer any accounts that you select in the Accounts<\/em> tab.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ol>\n
                                                      \n
                                                      Warning:<\/div>\n
                                                      \n
                                                        \n
                                                      • The system will overwrite any packages or feature lists with the same name that exist on the destination server.<\/li>\n
                                                      • If the transfer fails to create a new package or feature list, it will assign the default package or feature list to the account.<\/li>\n<\/ul><\/div>\n<\/div>\n
                                                        Package and feature list naming<\/h4>\n
                                                        The transfer tool feature performs the following actions during package transfers:<\/p>\n
                                                          \n
                                                        • \n
                                                          The restore system attempts to extract the package information from the cpmove<\/code> file. If the package does not already exist on the target system, the system creates the package and assigns it to the account. If the system cannot create the package, the system assigns the default package to the account.<\/p>\n<\/li>\n
                                                        • \n
                                                          If the feature list for the account exists on the target system, the system assigns it to the account. If the feature list does not exist, the system assigns the default feature list to the account.<\/p>\n<\/li>\n
                                                        • \n
                                                          You can transfer a new package and feature list with the same name as a package that already exists on the target server. This package will override the previous package\u2019s settings.<\/p>\n<\/li>\n<\/ul>\n
                                                          Service Configurations<\/h3>\n
                                                          In this section of the Account List<\/em> interface, select the configuration settings on the remote server that you wish to copy to a destination server.<\/p>\n
                                                          You can transfer the following configurations:<\/p>\n
                                                            \n
                                                          • \n
                                                            AutoSSL Options<\/p>\n
                                                            \n
                                                            Note:<\/div>\n
                                                            \n
                                                            This module does not modify the SSL provider. To update your SSL provider, use WHM\u2019s Manage AutoSSL<\/em> interface (WHM >> Home >> SSL\/TLS >> Manage AutoSSL<\/em>).<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                                          • \n
                                                            Backups<\/p>\n<\/li>\n
                                                          • \n
                                                            cPanel & WHM (whmconf<\/code>)<\/p>\n
                                                            \n
                                                            Note:<\/div>\n
                                                            \n
                                                            This configuration includes WHM\u2019s common settings that aren\u2019t user-specific. For example, the settings from WHM\u2019s Tweak Settings<\/em> interface (WHM >> Home >> Server Configuration >> Tweak Settings<\/em>) and WHM\u2019s Basic WebHost Manager Setup<\/em> interface (WHM >> Home >> Server Configuration >> Basic WebHost Manager Setup<\/em>).<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                                          • \n
                                                            Database Server<\/p>\n
                                                            \n
                                                            Note:<\/div>\n
                                                            \n
                                                            When you transfer remote MySQL databases, the Transfer Tool<\/em> feature includes any comments associated with the remote MySQL server. For more information about remote MySQL comments, read our Remote MySQL documentation.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                                          • \n
                                                            EasyApache<\/p>\n<\/li>\n
                                                          • \n
                                                            Exim<\/p>\n<\/li>\n
                                                          • \n
                                                            GreyList<\/p>\n<\/li>\n
                                                          • \n
                                                            Hulk<\/p>\n
                                                            \n
                                                            Note:<\/div>\n
                                                            \n
                                                              \n
                                                            • The Transfer Tool feature does not<\/strong> copy history reports.<\/li>\n
                                                            • The Transfer Tool feature appends<\/strong> whitelist- and blacklist-management configuration settings. It does not replace these configuration settings.
                                                              \n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
                                                            • \n
                                                              ModSecurity\u00ae <\/p>\n
                                                              \n
                                                              Note:<\/div>\n
                                                              \n        The EasyApache<\/em> service configuration also contains some ModSecurity settings. Use the ModSecurity service configuration to affect only the ModSecurity settings.\n    <\/div>\n<\/div>\n<\/li>\n
                                                            • \n
                                                              User Interface Themes<\/p>\n<\/li>\n<\/ul>\n
                                                              For more information about the files that the system transfers for each configuration, read the cpconftool<\/code> script documentation.<\/p>\n
                                                              To select your desired configurations, perform the following steps:<\/p>\n
                                                                \n
                                                              1. \n
                                                                The Configuration Name<\/em> and Analysis<\/em> columns display the available configurations and versions. You may need to click Show<\/em> for the available configurations to appear.<\/p>\n<\/li>\n
                                                              2. \n
                                                                Select the configurations that you wish to transfer to your local server.<\/p>\n
                                                                \n
                                                                Note:<\/div>\n
                                                                \n
                                                                  \n
                                                                • The system displays warning messages in yellow and blocker messages in red text.<\/li>\n
                                                                • If you receive a blocker message, the system disables the EasyApache<\/em> setting.<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
                                                                • \n
                                                                  Click Copy<\/em>. The system will display the progress interface.<\/p>\n
                                                                  \n
                                                                  Important:<\/div>\n
                                                                  \n
                                                                  This will also transfer any accounts that you select in the Accounts<\/em> tab.<\/p>\n<\/p><\/div>\n<\/div>\n
                                                                  \n
                                                                  Note:<\/div>\n
                                                                  \n
                                                                    \n
                                                                  • You cannot<\/strong> click Copy<\/em> until you select a configuration to transfer.<\/li>\n
                                                                  • The Transfer<\/em> column displays the status of all configurations from the remote server.<\/li>\n
                                                                  • The Restore<\/em> column displays the status of all configurations to the destination server.<\/li>\n
                                                                  • The system displays any error messages in yellow and warning messages in red text.<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<\/ol>\n
                                                                    The summary bar displays the transferred or restored configurations.<\/p>\n
                                                                    Restore the PHP-FPM .yaml configuration file<\/h4>\n
                                                                    MultiPHP user\u2019s PHP-FPM settings do not<\/strong> transfer. The system transfers the PHP-FPM .yaml<\/code> configurations to the filename.php-fpm.transferred<\/code> file. The system does this action because it cannot determine the status of the PHP and FPM services.<\/p>\n
                                                                    To restore the PHP-FPM .yaml<\/code> configuration file manually, perform the following steps:<\/p>\n
                                                                      \n
                                                                    1. Rename the file to the filename.php-fpm.yaml<\/code> file.<\/li>\n<\/ol>\n
                                                                      \n
                                                                      \/scripts\/php_fpm_config --rebuild<\/code><\/pre>\n<\/div>\n
                                                                      The system restores your account\u2019s PHP-FPM .yaml<\/code> configuration file.<\/p>\n
                                                                      The transfer process<\/h2>\n
                                                                      \n
                                                                      Note:<\/div>\n
                                                                      \n
                                                                        \n
                                                                      • \n
                                                                        In the following steps, domain<\/code> represents the name of a domain that you transferred.<\/p>\n<\/li>\n
                                                                      • \n
                                                                        The system considers any two records with the same resource name and type to be duplicates.<\/p>\n<\/li>\n
                                                                      • \n
                                                                        MultiPHP user\u2019s PHP-FPM settings do not<\/strong> transfer. The system transfers the PHP-FPM .yaml<\/code> configurations to the filename.php-fpm.transferred<\/code> file. The system does this action because it cannot determine the status of the PHP and FPM services. To restore this file manually, read the Restore the PHP-FPM .yaml<\/code> configuration file section above.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n
                                                                        When you use the Transfer Tool<\/em> interface to transfer accounts, the system performs the following actions:<\/p>\n
                                                                          \n
                                                                        1. \n
                                                                          The system creates the account.<\/p>\n<\/li>\n
                                                                        2. \n
                                                                          The system compares the DNS zone file from the account\u2019s backup file with the template-generated zone file that the system generated during account creation.<\/p>\n
                                                                          \n
                                                                          Important:<\/div>\n
                                                                          \n
                                                                          The Transfer Tool feature does not<\/strong> transfer DNS zone templates. If custom DNS zone templates exist on the remote server, the system ignores these zone templates when it recreates the account on the destination server.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                                                        3. \n
                                                                          The system updates the SOA record to match the target server\u2019s zone templates and comments out the existing SOA record from the remote server.<\/p>\n<\/li>\n
                                                                        4. \n
                                                                          The system updates domain<\/code> NS records to match the target server\u2019s zone templates and comments out any duplicate domain<\/code> NS records from the remote server.<\/p>\n<\/li>\n
                                                                        5. \n
                                                                          The system updates ftp.domain<\/code> A, AAAA, and CNAME records to match the target server\u2019s DNS templates and comments out any identical ftp.domain records from the remote server.<\/p>\n
                                                                          \n
                                                                          Note:<\/div>\n
                                                                          \n
                                                                          cPanel & WHM uses the IP address in the destination server\u2019s standardvirtualftp<\/code> zone template (usually, the server\u2019s main IP address) for virtual FTP when the account exists on a shared IP address.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                                                        6. \n
                                                                          The system checks whether the template-generated zone file uses an MX preference of 0<\/code>, and then performs the following actions:<\/p>\n
                                                                            \n
                                                                          • \n
                                                                            If the zone file\u2019s MX preference is 0<\/code> and the MX record points to $PRIMARY_DOMAIN<\/code> or mail.$PRIMARY_DOMAIN<\/code>, the system does not<\/strong> merge in the generated templates and does not<\/strong> update the MX preference from the remote server.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            If the zone file\u2019s MX preference is 0<\/code> and the MX record does not<\/strong> point to $PRIMARY_DOMAIN<\/code> or mail.$PRIMARY_DOMAIN<\/code> (a non-standard mail configuration), the system merges the generated templates and comments out templates from the remote server.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            For example, when the zone template\u2019s MX record defines an external mail service, the system prefers that entry over the record in the backup.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
                                                                          • \n
                                                                            The system comments out duplicate records.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            The system comments out CNAME records that conflict with any other records. If two or more CNAME records conflict, the system comments out all but the first CNAME record.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            The system updates records that reference the old IP address to use the account\u2019s new IP address.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            The system increments the SOA serial number for the domain.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            The system removes comments that are older than 30 days.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            The system updates CalDAV and CardDAV records to match the target server\u2019s DNS template.<\/p>\n<\/li>\n
                                                                          • \n
                                                                            The system transfers any DNSSEC key information from the backup file to the new server.<\/p>\n
                                                                            \n
                                                                            Important:<\/div>\n
                                                                            \n
                                                                            If the destination server does not<\/strong> support DNSSEC, that system will not<\/strong> restore any DNSSEC keys in the backup file.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                                                          • \n
                                                                            If the zone file contains an $ORIGIN<\/code> directive for an additional domain, the system will not<\/strong> update that additional domain\u2019s records.<\/p>\n<\/li>\n<\/ol>\n
                                                                            Live Transfer<\/h3>\n
                                                                            \n
                                                                            Warning:<\/div>\n
                                                                            \n
                                                                              \n
                                                                            • \n
                                                                              You can only<\/strong> use the Live transfer<\/em> feature to transfer accounts between cPanel & WHM servers.<\/p>\n<\/li>\n
                                                                            • \n
                                                                              Only<\/strong> use the Live transfer<\/em> feature if the source server controls the authoritative name servers for the domain. If the source server does not control the authoritative nameservers for the domain and you use this feature, DNS will not<\/strong> resolve. This will cause your sites to experience downtime.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n
                                                                              \n
                                                                              Note:<\/div>\n
                                                                              \n
                                                                                \n
                                                                              • \n
                                                                                You cannot<\/strong> enable this setting if the destination server\u2019s hostname does not resolve. Run the \/usr\/local\/cpanel\/scripts\/ensure_hostname_resolves<\/code> script, or use WHM\u2019s Change Hostname<\/em> interface (WHM >> Home >> Networking Setup >> Change Hostname<\/em>) to fix your hostname resolution.<\/p>\n<\/li>\n
                                                                              • \n
                                                                                Source servers that run cPanel & WHM version 88 and earlier use the Express Transfer<\/em> setting.<\/p>\n<\/li>\n
                                                                              • \n
                                                                                This process only<\/strong> includes active PHP sessions from the user\u2019s home directory. Users may need to log in again for features such as WordPress\u00ae, phpMyAdmin, and Webmail.<\/p>\n<\/li>\n
                                                                              • \n
                                                                                The Live Transfer feature uses the Accept and queue messages<\/em> setting behavior for email delivery. For more information about this setting, read our What Happens When You Suspend an Account documentation.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n
                                                                                Use the Live Transfer<\/em> feature to reduce downtime during account transfers. The interface enables this feature by default. The Live Transfer<\/em> feature moves cPanel accounts to a new server and performs the following actions on the source server:<\/p>\n
                                                                                  \n
                                                                                1. \n
                                                                                  Updates the account\u2019s A record to point to the destination server.<\/p>\n<\/li>\n
                                                                                2. \n
                                                                                  Changes the domain\u2019s nameserver entries to point to the destination server.<\/p>\n<\/li>\n
                                                                                3. \n
                                                                                  Updates the email routing configuration\u2019s MX records so that mail arrives at the destination server.<\/p>\n<\/li>\n
                                                                                4. \n
                                                                                  Sends requests for certain services to the destination server. For example, the system can redirect web and mail traffic to the destination server.<\/p>\n
                                                                                  \n
                                                                                  Note:<\/div>\n
                                                                                  \n
                                                                                    \n
                                                                                  • \n
                                                                                    Mail services redirect to the child node, if applicable.<\/p>\n<\/li>\n
                                                                                  • \n
                                                                                    To disable service proxying, unsuspend the account on the source server.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
                                                                                  • \n
                                                                                    Copy the mailbox data from the source server again.<\/p>\n<\/li>\n
                                                                                  • \n
                                                                                    Suspends the transferred accounts on the source server. For more information, read our What Happens When You Suspend an Account documentation.
                                                                                    \nThe system performs changes on the source server in the \/usr\/local\/cpanel\/scripts\/xferpoint<\/code> directory.<\/p>\n
                                                                                    \n
                                                                                    Note:<\/div>\n
                                                                                    \n
                                                                                    If you do not<\/strong> want to use this feature, you can use the swapip script to update the transferred accounts\u2019 nameserver records.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ol><\/div>\n","protected":false},"excerpt":{"rendered":"
                                                                                    Valid for versions 94 through the latest version Version: 82 84 88 90 92 94 Overview This interface copies multiple accounts from a remote server to your cPanel & WHM server. To transfer accounts, you must obtain the following: root-level privileges with the su or sudo commands. Warning: Do not shut down or restart any …<\/p>\n","protected":false},"author":1,"featured_media":1091,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/1090"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=1090"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/1090\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/1091"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=1090"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=1090"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=1090"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}