Bobcares

How we manually migrate non-cPanel server to CWP and solve errors

by | Oct 30, 2019

Migrating from a control panel based server to a CWP server is comparatively easy.

However, migrating a non-cPanel server to CWP requires some expertise in server migration. Because it needs to be performed manually.

No migration tool is available to move accounts from plain server to CWP.

At Bobcares, we often get requests from our customers to migrate non-cPanel server to CWP as part of our Server Migration Services.

Today, we’ll see how our Migration Engineers migrate non-cPanel server to CWP manually and fix related errors.

How we manually migrate non-cPanel server to CWP

Unfortunately, there is no such migration tool to move accounts from plain server to CWP. So we have to migrate the website files, database, and emails manually.

Now, let’s see how our Support Engineers migrate websites from non-cPanel based server to CWP.

For that, we follow the given steps.

1.  Initially, we create all accounts on CWP first.

2. Then, we move all files from an old server to a new server either using rsync or scp.

3. Next, we create a database,database-user.

4. After that, we modify the config files accordingly on a new server.

5. We migrate emails as well. So we use imapsync method.

At last, we test the site on CWP by force host file lookup or with temp link.

 

How we fixed error while migrating non-cPanel server to CWP

From our experience in managing servers, we’ve seen customers facing problems while migrating cPanel accounts to CWP.

Now let’s see how our Migration Engineers fix the top errors.

 

1. File permission

Usually, customers may experience website errors when migrating from an old server to the new server. Mainly, this may happen due to incorrect permission and ownership of directories or files that set up in the destination server.

So, our Migration Engineers make sure that the given file permission and ownership are correct.

If not, the website will definitely show an error.

To solve the error, we log into the main admin CW Panel and click on User Accounts > Fix Permissions.

Then, we select the user account and click the Fix Selected Issues button. This updates all the files and folder permissions/ownership.

 

2. Large Mailboxes

Similarly, when migrating large mailboxes customers may face problems like timeout errors. By default, imapsync often causes timeouts when the migration process continues for a longer period.

To avoid these timeout errors, our Migration Experts switch off the computation of statistics using the following commands.

--nofoldersizes --skipsize --fast

 

After this migration of mails worked successfully.

 

[Having difficulty in migrating websites to CWP? We’ll fix it for you.] 

 

Conclusion

In short, migrate non-cPanel servers to CWP has to be performed manually. Today, we saw how our Migration Engineers did CWP migration without website downtime and fix related errors.

Migrate cPanel to a new platform!

Looking for changing infrastructure of your server? Let us help you.

Our migration experts can migrate all your accounts to a new platform without data loss.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF