This article provides general preparation guidance. Final service recommendations depend on the actual software, data, licensing, integrations, and operating requirements involved.
Choose nameservers or individual DNS records
A domain can use the hosting account nameservers or keep DNS elsewhere and point the required records manually. The right option depends on who should manage email, subdomains, and other services.
Confirm the website destination
For manual DNS, the root domain normally uses an A record and the www host commonly uses a CNAME or matching A record. The exact values should come from the active hosting service details.
Do not forget email records
Changing nameservers can also change mail routing. Preserve or recreate MX, SPF, DKIM, and verification records before switching DNS when email is already in use.
Allow time for DNS changes
Updates can appear quickly but may remain cached by networks and devices. Keep the previous service available during the transition whenever possible.
Never place passwords, private tokens, recovery codes, API keys, database credentials, or license keys into a public form or unverified message.