Pages and assets
Open representative pages and confirm images, styles and downloads.
Website migration support
The migration route
Confirm the source platform, selected KingHost plan and requested components.
Retain the old service, create a current backup and agree the validation window.
Copy the supported website files, databases and agreed configuration.
Check pages, forms, application access and other items recorded in the scope.
Update DNS during the agreed window, monitor propagation and complete handover.
Scope before access
Before changing DNS
Open representative pages and confirm images, styles and downloads.
Check sign-in, recent records and the workflows included in the scope.
Test forms and confirm where notifications should be delivered.
Record existing DNS, confirm TTLs and retain the old service during propagation.
Migration FAQ
Migration support may be included with an eligible KingHost hosting plan. KingHost confirms eligibility and any charge after reviewing the source account and requested scope.
The normal approach is to keep the old service active while the supported copy is transferred and checked. DNS propagation and application behaviour vary, so uninterrupted service cannot be guaranteed.
There is no fixed completion time. Access, data size, platform compatibility, transfer speed, validation and DNS propagation all affect timing.
KingHost can review common environments such as cPanel, DirectAdmin and Plesk. Custom or restricted environments require an access and compatibility check.
Email migration is not assumed. Mailbox data, forwarders, calendars and DNS records must be listed and confirmed separately before work begins.
The required access depends on the source environment. Share credentials only through the authenticated support process and rotate temporary credentials after handover.
Yes. Create and retain an independent current backup before migration, and keep the old service available until you approve the new copy.
DNS is changed after the agreed validation checks pass and you approve the cutover. Existing TTL values influence how quickly resolvers see the update.
The cutover is paused, the failed check is documented and the next step is agreed with you. The source service should remain available during investigation.
Choose an appropriate KingHost plan, then open a migration request with the source platform, website size, required components and preferred change window.
Ready to scope the move?