Migrate a Website from HostingRaja
Migrate from HostingRaja by identifying the actual panel, application stack, database and mail provider, then taking an independent recoverable backup. Copy and test the destination through authorised access before changing DNS. Mail and database recovery need separate checks; a fixed one-week overlap or a five-minute TTL does not guarantee safe rollback of newly created data.
For HostingRaja account owners moving services elsewhere, with panel-independent inventory, secure mailbox copying and transaction-aware cutover rather than assumed provider defaults.
knowledge
- Read time
- 6 min
- Sections
- 9
- Updated
- 14 Nov 2026
- Written by
- WebJi® team
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Which panel you are leaving, cPanel or Plesk
Moving a site off HostingRaja starts with a backup you own, taken from cPanel or Plesk. Copy the files and databases, recreate the mailboxes, test on the new IP, then change nameservers. Keep the HostingRaja plan paid for a week so the old copy is still there to roll back to.
Inspect the actual control panel, website root, database engine and mail provider before copying. A plan name or login URL alone does not prove the entire stack. Plesk can manage Linux or Windows deployments, and provider product offerings may change.
| Task | cPanel account | Plesk account |
|---|---|---|
| Website root | public_html | httpdocs |
| Backup menu | Files, then Backup | Tools & Settings, then Backup Manager |
| Database tool | phpMyAdmin | Databases, then phpMyAdmin |
| Mailboxes | Email Accounts | Mail, then Create Email Address |
| DNS zone | Zone Editor | DNS Settings |
Identify the database engine from the application configuration. SQL Server backup/restore differs from a MySQL dump; Windows hosting is not the only possible SQL Server environment, and not every Plesk site uses the same engine.
Take the backup before anyone gets a password
HostingRaja's transfer service asks for FTP or SSH details and the database credentials, and its own page says it is not liable for data loss caused by wrong credentials or network limits.[1] Take your own copy first, then decide who does the move.
- Full account archive: contains the home directory and MySQL databases, and is the fastest restore.
- A full account or subscription backup may include mail when selected and supported; a website-files archive does not. Inspect the actual backup scope and verify mailbox recovery separately.
- DNS: screenshot the zone, and write down NS, A, MX and TXT values in a text file.
- Do not hand over a root password for a VPS. A temporary sudo user or a panel login is enough.
A provider’s inbound transfer queue is not a measured duration for this outbound migration. Rehearse the copy and validation, and agree an overlap and rollback plan before closing any account.
Move the files from cPanel or Plesk
The file move is the same idea in both panels: compress the website root, download the archive, upload it to WebJi, extract it, then fix ownership. Only the menu names and the folder name change.
- cPanel: open Files, then File Manager, select the contents of public_html, and compress them into site.zip.
- Plesk: open Files, go to httpdocs, select all, and use the archive command to make site.zip.
- Download the archive, then upload it to the WebJi account home and extract it into public_html.
- If using rsync, use authorised source and destination accounts and verified paths. Do not assume a root SSH login is available or necessary on the destination.
- Set the owner to the account user, folders to 755 and files to 644. Files owned by root break uploads and plugin updates.
Check that .htaccess or the Plesk web.config file came across. Without it, permalinks and redirects fail while the home page still loads.
Move the databases and fix the configuration
Export, create, import, then point the application at the new database. On MySQL that is three commands or three screens; on MS SQL it is a backup and restore, followed by a connection-string edit.
- Export MySQL from phpMyAdmin, or run
mysqldump --single-transaction --routines --triggers -u USER -p DBNAME > DBNAME.sql - On WebJi open MySQL Databases, create the database and a user, and grant all privileges on it.
- Import the .sql file, then compare the table count with the old server before you change any setting.
- Edit wp-config.php, or the application config, with the new DB_NAME, DB_USER, DB_PASSWORD and DB_HOST.
- For MS SQL, restore the .bak into a new database in SSMS and update the connection string in web.config.
If the database user in Plesk was separate from the subscription user, recreate that split on WebJi. A single user with all privileges is simpler, but it changes who owns the tables.
Rebuild the mailboxes and cut MX last
Mail sits on the mail server, so it does not travel with the website files. Create the same addresses first, copy the old messages, and change MX only after an outside test message arrives.
- cPanel: open Email Accounts and create each address, alias and forwarder. Plesk: open Mail, then Create Email Address.
- Create mailboxes through the provider’s supported secure management route. Do not place real mailbox passwords in command arguments or send root credentials in an ordinary email.
- Use the actual provider-supplied IMAP endpoints. With no password arguments, imapsync prompts instead of exposing secrets:
Verify TLS and mapping, then perform authorised copy passes and inspect mailbox content.imapsync --host1 OLD_IMAP_HOST --user1 you@example.com --ssl1 --sslargs1 SSL_verify_mode=1 --host2 NEW_IMAP_HOST --user2 you@example.com --ssl2 --sslargs2 SSL_verify_mode=1 --automap --dry - Run it twice without --dry, compare folder counts, then send a test from an outside address and reply.
- Change MX and add the new server to SPF in the same edit. Keep the old MX value written down.
You know mail moved when each folder shows the same message count on both servers and an outside sender reaches the new inbox.
Test the copy before nameservers change
Send one machine to the new server while the domain still resolves to HostingRaja. A hosts-file entry does it for the whole browser session, and curl does it for a single request.
- macOS or Linux: add
203.0.113.10 example.com www.example.comto /etc/hosts. - Windows: the same line in C:\Windows\System32\drivers\etc\hosts, opened as administrator.
- No edit:
curl -I --resolve example.com:443:203.0.113.10 https://example.com/
Check the home page, an inner permalink, an image, the stylesheet, a form submission and the admin login. You know it worked when all of them load over HTTPS with no mixed-content warning and the headers name the new server.
Remove the hosts entry afterwards, or your browser keeps showing you the new site after a failed cutover.
DNS cutover and the rollback list
Write the rollback values down before the change, not after. Three commands capture everything you need to put the domain back where it was.
- Record the current answers:
dig +short NS example.com,dig +short A example.comanddig +short MX example.com. - Lower record TTLs in advance where appropriate and wait for earlier cached values. A-record TTL changes do not control cached nameserver delegation or guarantee a five-minute rollback.
- If the domain uses HostingRaja's DNS, you can edit just the A and MX records in their zone. If it uses their nameservers from another registrar, switch the nameservers to WebJi's.
- Verify from two resolvers:
dig +short example.com @1.1.1.1anddig +short example.com @8.8.8.8. - Before reverting traffic or closing the old service, preserve and reconcile newer orders, submissions and mail. Recorded DNS values help restore routing but do not merge data between writable copies.
The nameserver guide covers registrars that are not HostingRaja. Cached answers live for the old TTL, so some visitors still reach the old server after the change.
What the move costs on both sides
WebJi®’s published migration reference is ₹700 one-time before 18% GST for one domain, FTP files and up to five MySQL databases within the stated 5 GB scope. Confirm current checkout and eligibility; this is not the same product as a provider’s inbound transfer service.
| Route | Reference | Limit to verify |
|---|---|---|
| WebJi® one-domain migration | ₹700 one-time | FTP files and up to 5 MySQL databases within the stated 5 GB allowance |
| Self-managed copy | No service price quoted here | Access, compatible runtime, data protection and validation remain required |
Choose the destination by runtime and database support, not panel name alone. Shared hosting and Plesk hosting have different published plan scopes. Confirm the migration service separately, especially for Windows applications, SQL Server and mail.
References
- HostingRaja (https://www.hostingraja.in/website-transfer/) — website transfer page. Read on 29 October 2026.
Figures about other companies on this page were read from the sources above on the dates shown; those pages change without notice. WebJi® is not affiliated with, and is not the support desk of, any company named on this page.
Frequently asked questions
Is HostingRaja cPanel or Plesk?
Check the account’s actual panel and application stack rather than assuming one panel for an entire provider or OS. cPanel and Plesk use different menus; Plesk can manage Linux or Windows. Identify database, mail and document-root settings from the real account before migration.
Can I keep my domain at HostingRaja?
Yes. Changing nameservers or the A record moves the hosting and leaves the registration alone. If the domain uses HostingRaja's DNS, you can edit only the A and MX records and keep their nameservers.
Can HostingRaja's free transfer move my site away?
No. That service moves sites onto HostingRaja. Leaving is a manual copy or a paid move by the new host. Their page also asks for up to a week and disclaims liability for data loss, so keep your own backup.
How do I move mail out of Plesk?
Create the same addresses on WebJi under Mail, copy each mailbox with imapsync twice, compare folder counts, then change MX. Plesk mail is separate from the website files, so it needs its own test.
How long does the DNS switch take?
It depends on previous record and delegation caches, not one universal TTL. A 300-second A-record setting does not change every resolver instantly or shorten parent nameserver caching. Compare authoritative and recursive answers and keep the old service recoverable during the agreed overlap.
How do I roll back if the new server fails?
Preserve both environments and identify the authoritative data before reverting routing. DNS values can redirect traffic, but cannot reconcile orders, submissions or email created after cutover. Use a reviewed recovery plan and avoid leaving both old and new applications accepting writes.
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.