On this page
For a free cPanel migration, open a support ticket and send the old cPanel URL, username, and password. We use that login to copy the full account. A WordPress admin login is not enough, because it cannot reach mail, cron, or addon domains the way cPanel can.
After we finish the copy, you preview the site on our servers. When the preview looks correct, you update nameservers at your registrar. We do not need your registrar login, and we do not change DNS for you.
What to put in the first ticket
Include everything we need to reach and copy the account so we do not have to chase details later. Send the old cPanel login URL, the cPanel username, and the password. List the domains involved and say whether email should move with the account.
- A normal cPanel user login is enough for a single account.
- A WHM reseller login works when several accounts need to move together.
- A WordPress admin login helps after the move, but it cannot drive the copy itself.
If two-factor authentication is enabled, temporarily disable it or provide a way for us to complete a session. If the old host blocks remote access, you can send a full cpmove file or a files-plus-SQL package instead. Tell us which method you are using. If the old panel is Plesk or you only have FTP, say so up front. The free cPanel pull does not apply in those cases, but we can still help with a files and database transfer.
How the migration loop works
We copy the account, you preview it, and you switch nameservers when you are ready. Only you can judge whether checkout, forms, and mail feel right in production. Preview first, then change DNS at your registrar when the preview matches what you expect.
Our nameservers are ns1.logicweb.com and ns2.logicweb.com. You make that change when the preview is acceptable. If the preview returns a 404, the document root or path needs attention before any nameserver change.
What we will not do unless you ask
We will not switch DNS at your registrar as a courtesy. The registrar account stays under your control. We also will not treat a missing or broken preview as a reason to flip nameservers early.
After the copy, use response headers and the steps in tell old host from new to confirm traffic is landing on the new server. A temporary 2FA disable for the copy is fine; leaving it off afterward is not. Rotate the password you shared once we confirm the account is on our side.
Tagged
Was this article helpful?
Be the first to rate this article.



