Separate the three components
Modern secure connections use TLS; hosting services often retain the term SSL. It encrypts data in transit and helps authenticate the server. A certificate does not fix application bugs or create backups.
- Domain — the address you register and renew. The business owner needs access to the registrar account.
- Hosting — the environment serving your website files and, where needed, its database and server processes.
- SSL/TLS — connection protection through HTTPS. The certificate must cover the main domain and any subdomains you use.
Official source: Cloudflare · SSL/TLS
Choose hosting around the website architecture
Static HTML pages need file delivery. A PHP website with a database needs a compatible server environment. Uploading a Bitrix archive to static hosting will not make its forms and administration panel work.
Before choosing a provider, list the CMS, file and database sizes, inquiry processing, integrations and editing requirements. Check who updates the system, backup retention, restoration and support. Ask whether email is included: web hosting and email hosting may be separate services.
Migrate in stages
- Save the files, database and complete DNS record list. Check that the backup can be restored.
- Prepare the new environment and test through a preview address. Check every page, image, form and redirect.
- Configure HTTPS for the required hostnames. Check HTTP links and resource loading.
- Switch website records after testing. If you change nameservers, copy all necessary records, including the existing mail records.
- After the switch, check the site from another network and test inbound and outbound mail. Retire the previous hosting after verification and backup retention.
Why website migration involves email records
MX directs incoming email. TXT records may hold SPF, DKIM, DMARC and service verification data. Names such as mail and autodiscover may also be in use. Changing the website address alone does not require moving mailboxes; replacing the DNS zone requires retaining its working records.
If email stays with the existing provider, make that requirement explicit. Do not remove a record just because it resembles the old hosting address: establish what it does first.
What to receive at handover
- Owner access to the domain, hosting and content management system.
- A list of services, renewal dates and annual costs.
- A backup policy and a tested restoration procedure.
- Documentation for inquiry handling, support and website outages.
Discuss your project
Tell us your goal, languages and required functions. We will agree on the scope and next steps.