A hosting move is more than copying the visible pages. A website can rely on a database, scheduled tasks, configuration secrets, uploads and email records. Before changing anything, list what the existing account actually provides. This planning checklist is for a small site; a transactional application may need a specialist migration procedure.
Inventory the current account
Record the website files, database names, runtime versions, scheduled jobs and any external services. Note whether email is hosted in the same account or elsewhere. Export the current DNS zone or save a record of it. In particular, preserve the mail-related records required by the actual email provider. A nameserver change replaces the authoritative DNS location and can affect more than the website.
Create a recovery point first
Save both files and database content where applicable. Keep the backup outside the account being changed and confirm you can read it. Record the current working configuration without placing passwords in a public document. Define a rollback decision: what failure would make you return to the old service, and how would you handle any new content created after the move?
Test the destination before switching
Use a supported preview method or a safe staging address. Check the important pages, forms, uploads, redirects and scheduled work. Prevent the test copy from sending duplicate notifications or processing real transactions. Compare runtime requirements with the destination rather than assuming all shared hosting is interchangeable.
Plan for changing content
A site receiving orders, messages or edits can diverge while the files are copied. Arrange an appropriate write freeze or final data synchronisation. A brochure site with occasional edits is simpler, but contact submissions can still arrive during the transition. Keep both environments available while you verify the cutover and avoid deleting the old database immediately.
Verify the public result
After the DNS change, test the preferred domain and HTTPS from more than one connection if possible. Check inbound and outbound email independently. Confirm that the new cron jobs and backups run, and that sensitive files are not public. Keep the old hosting until the new service is verified and the overlap period is sufficient for your circumstances.
Close the old account deliberately
Take a final backup and retain invoices or records you need. Only then cancel the old service according to its terms. Remove obsolete access and document the new hosting details. Migration is complete when the new site is working and recoverable, not merely when the homepage appears.