Skip to content 
I'll show you how to create a webhosting termination and complete it without any downtime. These instructions will guide you step by step through the termination, data backup, domain transfer and transfer to a new host - practical, secure and up-to-date for 2025.
Key points
- Deadlines Check and record the termination date
- Backups of files, databases and e-mails
- Termination Submit correctly and secure confirmation
- Domain Transfer or delete via Authcode
- Migration test and avoid downtime
Contracts and deadlines: a safe start
Before I give notice, I check the Minimum term and the contractual notice periods in the customer account. Many tariffs require 1 to 3 months' notice, so I immediately enter the last possible date in my calendar and prevent automatic renewals. I look up the customer number, contract ID and tariff name so that I can enter all the details correctly in the termination letter later. If I'm unsure, I clarify the exact end of the contract in the support chat and document the answer as proof. For additional guidance, I use additional Cancellation tips and compare them with my documents.
I also check possible Special termination rightsfor example in the event of price increases, serious changes to services or persistent disruptions. In such cases, I formulate the termination with reference to the specific reason and the corresponding contractual clause. Important: Hosting contract and Domains are often separate services. I decide whether I only want to cancel the web hosting and transfer the domain - or whether I want to cancel both. I cancel additional packages such as SSL certificates, backups, licenses or mail extensions specifically so that no unnecessary costs continue.
For international domains I pay attention to the Transfer lock after owner changes: gTLDs (e.g. .com, .net) can be blocked for transfers for 60 days after a data change if no opt-out has been set. I therefore only change WHOIS data after the successful transfer and check whether domain privacy services are transferred correctly. Different rules apply to .de domains, but I still adhere to best practices and document every step.
Data backup: complete backups without gaps
I first secure all Website files via FTP or file manager, including media, themes, plugins and configurations. I then export the databases via phpMyAdmin or the console so that the new server receives identical content. With WordPress, I also pack an archive with a migration plugin such as Duplicator to make the move faster. I export email inboxes via an IMAP client or back them up in archive formats before I set up the inboxes with the new provider. Finally, I create a list of the active domains, subdomains and DNS entries so that I don't forget anything later and the DNS zones correctly.
I check the Backups randomly: open database archive, count tables, randomly check contents. If necessary, I split large dumps into several files so that the import runs smoothly. Hidden files such as .htaccess, .user.ini, .env, composer.json and robots.txt as they often contain security and performance-critical settings. I check file permissions and owners after copying so that the target system can read and write the files correctly.
At CMS I also deliberately don't migrate cache and upload directories if they can be rebuilt quickly - this saves time and avoids legacy issues. With WordPress, I plan a Search & Replace for absolute URLs (e.g. from http to https or for changed paths). For stores, I import separately Media and generate new preview images. If the old provider provides groupware, I export Calendar (CalDAV) and Contacts (CardDAV) separately so that no appointments are lost.
Domains and emails: plan your transfer properly
For the domain I need the Authcode (EPP), which I call up in the customer area or receive from support. I start the transfer with the target provider, confirm the e-mails from the registry and wait for the transfer, which usually takes place within a few days. If necessary, I can send .de domains to a transit if I have not yet specified a target provider. During the changeover, I keep the TTL of the DNS entries low so that changes take effect more quickly and emails don't accidentally go nowhere. Before the final switchover, I test new mailboxes, SPF, DKIM and DMARC so that the Deliverability right.
Before the change, I reduce the TTL important records (A/AAAA, MX, CNAME) to 300 seconds, for example. This allows me to roll out changes in just a few minutes. I make a conscious decision between Name server change and zone-by-zone customization: When the new hosting provides the name servers, I export the old zone and import it cleanly - including subdomains, TXT records, SPF, DKIM, DMARC and any CAA-entries. With active DNSSEC I plan the change: DS entries must match the new signing key at the registrar, otherwise there will be resolution errors.
For the E-mail relocation I set up all mailboxes, aliases and forwarding with the target provider in advance and test access and sending. For a seamless migration, I use IMAP synchronization if possible (second account in the mail client or migration tools) so that new messages from both worlds come together during the changeover phase. I leave the old mailboxes active for a few more days, check Spam filter and quarantine and check whether signatures and out-of-office notes have been accepted. In the case of dedicated IPs, I clarify the Reverse DNS-entry so that your reputation does not suffer.
Termination letter: clear, complete, binding
In my letter I put complete Names, address, customer number, tariff name and the desired contract end date or "as soon as possible". I formulate concisely: I terminate the web hosting contract on time and request a written confirmation stating the specific end date. If I send it by post, I sign it; if I send it by email, I ask for a read receipt and save the message as a PDF. I assign unique file names to each attachment so that I can find them quickly later. I archive the notice of termination, the proof of dispatch and the subsequent Confirmation together.
In addition, I record which Services are also terminated (domains, SSL, add-ons). Formulations for Data deletion after the end of the contract and refer to the deletion of personal data in accordance with the GDPR as soon as statutory retention periods have expired. I revoke SEPA direct debits on the end date, provided there are no outstanding items. If I put the domain in transit, I will state this explicitly to avoid any misunderstandings.
Transmission channels: post, e-mail, customer area, fax
I submit the notice of termination via the official Customer area if the provider offers a button or wizard there. Alternatively, I send them to the official support address and activate a read confirmation so that I have proof. I use registered mail if I prefer a confirmation of receipt, fax only with a qualified transmission report. It remains important: I keep every proof, every ticket and every e-mail in case of queries. If you cancel online, you can follow the procedure, as I did with the cancel with IONOS describe.
Some providers require a Confirmation of identity (e.g. copy of an ID card or callback). I prepare these documents so that deadlines do not expire. If there is a dedicated termination form, I fill it out completely and upload my own letter in addition. If there are several contracts in the customer account, I clearly specify which tariff is affected and rule out any confusion.
Choose a new provider: Criteria 2025
When changing, I pay attention to Performanceavailability, backup functions, security features and support quality in German. Transparent limits are important to me, for example for CPU, RAM, inodes and simultaneous processes. I also check whether the provider offers free SSL certificates, staging environments, automatic updates and one-click restores. A good migration service saves time, but I always check the details before I sign. The following overview shows a compact Comparison selected providers.
| Rank | Hosting provider | Performance | Support | Price/performance |
|---|---|---|---|---|
| 1 | webhoster.de | Very good | Very good | Very good |
| 2 | Strato | Good | Good | Good |
| 3 | IONOS | Good | Good | Satisfactory |
I also take into account Location and data protection (data centers in the EU), the availability of an order processing contract, SLA transparency and functions such as HTTP/2/3, Brotli, NVMe storage, Redis object cache, WAF and DDoS protection. For managed tariffs, I clarify which updates and Security patches the provider takes over and what remains my responsibility. A clear cost structure without hidden upgrades, meaningful limits and fair tariff switching options give me planning security.
Migration: Plan, check and activate the move
I set up the target hosting completely before I start the DNS PHP version, databases, users, SSL, cronjobs. I then upload files, import the database and adjust configurations such as wp-config.php or .env. With WordPress, I use staging to test the new environment without visitor load. Once everything is running, I switch DNS, monitor logs and correct error messages immediately. At the same time, the old tariff remains active until the end of the contract so that I can switch back at short notice in the event of problems and thus minimize the Downtime minimize.
Before the go-live, I check Absolute pathsfile uploads, e-mail dispatch (SMTP instead of PHP mail), caching mechanisms and sessions. For CMS I use a Search-and-replace-routine for URLs and clear application and server caches. For stores, I test checkout, payment methods, tax rates, shipping rules, PDFs and search functions. If the platform allows it, I rely on Blue-Green or staging-to-production with a minimal switching window. A look at error logs and PHP/web server settings (memory_limit, max_execution_time, FPM process manager) prevents nasty surprises.
DNS, SSL and security: avoiding stumbling blocks
Before switching, I reduce the TTL of the relevant records (A, AAAA, CNAME, MX) so that changes take effect quickly. I make sure that Let's-Encrypt or other certificates can be issued on the target system and renew certificates after the transfer. I also forward old URLs correctly, only set HSTS if I can guarantee secure HTTPS delivery and check mixed content warnings. For email, I activate SPF, DKIM and DMARC at an early stage so that the reputation remains stable. Finally, I check security headers, file permissions and backup plans to ensure the Risk to reduce.
At CAA-records, I allow the desired certification authority so that certificate issuance is not blocked. If I use DNSSEC, I plan the sequence: deactivate or adapt DS, change name server, sign new zone, update DS - always with a sufficient buffer. I keep a rollback ready (old zone/old IP) as long as the TTLs are still short. For API integrations, I renew API keys and webhooks and enter new callback URLs in third-party dashboards.
Invoices, direct debits and confirmation: finalize cleanly
After the termination, I never rely on mere Silencebut actively request a written confirmation of the end date. I save PDF invoices, ticket numbers and transmission logs in one place. If a direct debit is planned after the end of the contract, I cancel it in good time and back it up with my documents. If anything is unclear, I keep queries brief, factual and refer to the available evidence. For special cases, I get additional help, for example from providers with special features or if I need to make a decision, as in the case of Cancel 1blu special steps must be observed.
I clarify whether it is Pro rata refunds if there is an annual advance payment or whether remaining terms expire. I will export all tax-relevant documents before the end of the contract. After the confirmation I ask - as far as permissible - for Deletion of personal data and close open support tickets. If domains continue to run separately, I check their new billing cycles so that there are no duplicate costs.
Checklist 2025: step by step without gaps
I start with the Contract data and mark the latest termination date so that nothing overflows. I then back up files, databases and emails completely and randomly check whether the backups can be opened. I send the termination letter via a traceable channel and save the confirmation. I transfer domains with Authcode, adjust DNS and test the new environment. Only when everything is running smoothly do I let the old tariff expire and save all Receipts on.
I also set myself these interim goals: Lower TTL, define nameserver strategy, prepare SSL/CAA/DNSSEC plan, mirror mailboxes and aliases, test staging, redirects and SEO-signals (sitemaps, canonicals), set up cron jobs and background processes, empty caches, activate monitoring and have a rollback option ready. In this way, the move remains controlled and reversible.
Professional tips for backups and relocation
I rely on automated Backup plans at the new host, ideally daily with storage over several generations. I also keep an offsite backup in the cloud or locally in order to be independent in an emergency. For CMS, I check plugin and theme compatibility and test updates in staging. For large projects, I use temporary maintenance pages with 503 headers so that crawlers react correctly. After the go-live, I monitor error logs, 404 statistics and loading times in order to find hidden Problems early on.
I activate Monitoring (HTTP, TLS, DNS, SMTP) and notifications so that I can react immediately in the event of failures. For performance, I test TTFB, caching, database latencies and simulate load peaks. In the event of heavy bot traffic, I set rate limits and WAF rules to protect resources. On the SEO side, I check redirects (301 instead of 302), canonical tags, hreflang, sitemaps and submit the new property to Webmaster Tools when changing domains. After the switch, I delete old, sensitive data from the old provider or encrypt it until the contractual deletion is confirmed.
Summary: clear steps, secure termination
You give structured notice, ensure Data completely and plan the transfer without rushing. Keep outages to a minimum with authcode, clean DNS conversion and staging tests. Legally compliant termination with confirmation and complete documentation protects you from disputes. A modern host with solid backup and security functions makes the switch worthwhile. How to cancel your web hosting in 2025 quickly, reliably and with good Feeling.
