{"id":12525,"date":"2025-09-17T08:39:52","date_gmt":"2025-09-17T06:39:52","guid":{"rendered":"https:\/\/webhosting.de\/webhosting-kuendigen-daten-sichern-schritt-anleitung-profi-migration-office\/"},"modified":"2025-09-17T08:39:52","modified_gmt":"2025-09-17T06:39:52","slug":"webhosting-termination-data-backup-step-by-step-instructions-profi-migration-office","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/webhosting-kuendigen-daten-sichern-schritt-anleitung-profi-migration-office\/","title":{"rendered":"Cancel web hosting and back up data - step-by-step guide 2025"},"content":{"rendered":"<p>I'll show you how to create a <strong>webhosting termination<\/strong> 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.<\/p>\n\n<h2>Key points<\/h2>\n\n<ul>\n  <li><strong>Deadlines<\/strong> Check and record the termination date<\/li>\n  <li><strong>Backups<\/strong> of files, databases and e-mails<\/li>\n  <li><strong>Termination<\/strong> Submit correctly and secure confirmation<\/li>\n  <li><strong>Domain<\/strong> Transfer or delete via Authcode<\/li>\n  <li><strong>Migration<\/strong> test and avoid downtime<\/li>\n<\/ul>\n\n<h2>Contracts and deadlines: a safe start<\/h2>\n\n<p>Before I give notice, I check the <strong>Minimum term<\/strong> 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 <a href=\"https:\/\/webhosting.de\/en\/webhosting-cancel-contract-tips-change-provider-data-backup-brand-new\/\">Cancellation tips<\/a> and compare them with my documents.<\/p>\n\n<p>I also check possible <strong>Special termination rights<\/strong>for 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 <strong>Domains<\/strong> 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.<\/p>\n\n<p>For international domains I pay attention to the <strong>Transfer lock<\/strong> 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.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img fetchpriority=\"high\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/webhosting-datensicherung-8452.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Data backup: complete backups without gaps<\/h2>\n\n<p>I first secure all <strong>Website files<\/strong> 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 <strong>DNS zones<\/strong> correctly.<\/p>\n\n<p>I check the <strong>Backups<\/strong> 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 <code>.htaccess<\/code>, <code>.user.ini<\/code>, <code>.env<\/code>, <code>composer.json<\/code> and <code>robots.txt<\/code> 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.<\/p>\n\n<p>At <strong>CMS<\/strong> 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 <em>Search &amp; Replace<\/em> for absolute URLs (e.g. from http to https or for changed paths). For stores, I import separately <strong>Media<\/strong> and generate new preview images. If the old provider provides groupware, I export <strong>Calendar<\/strong> (CalDAV) and <strong>Contacts<\/strong> (CardDAV) separately so that no appointments are lost.<\/p>\n\n<h2>Domains and emails: plan your transfer properly<\/h2>\n\n<p>For the domain I need the <strong>Authcode<\/strong> (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 <strong>Deliverability<\/strong> right.<\/p>\n\n<p>Before the change, I reduce the <strong>TTL<\/strong> 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 <strong>Name server change<\/strong> 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 <strong>CAA<\/strong>-entries. With active <strong>DNSSEC<\/strong> I plan the change: DS entries must match the new signing key at the registrar, otherwise there will be resolution errors.<\/p>\n\n<p>For the <strong>E-mail relocation<\/strong> 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 <strong>Spam filter<\/strong> and quarantine and check whether signatures and out-of-office notes have been accepted. In the case of dedicated IPs, I clarify the <strong>Reverse DNS<\/strong>-entry so that your reputation does not suffer.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/webhosting-kuendigen-guide-2025-4812.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Termination letter: clear, complete, binding<\/h2>\n\n<p>In my letter I put complete <strong>Names<\/strong>, 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 <strong>Confirmation<\/strong> together.<\/p>\n\n<p>In addition, I record which <strong>Services<\/strong> are also terminated (domains, SSL, add-ons). Formulations for <strong>Data deletion<\/strong> 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.<\/p>\n\n<h2>Transmission channels: post, e-mail, customer area, fax<\/h2>\n\n<p>I submit the notice of termination via the official <strong>Customer area<\/strong> 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 <a href=\"https:\/\/webhosting.de\/en\/ionos-hosting-cancel-domain-contract-online-hosting-change\/\">cancel with IONOS<\/a> describe.<\/p>\n\n<p>Some providers require a <strong>Confirmation of identity<\/strong> (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.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/webhosting-kuendigen-datensicherung-4739.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Choose a new provider: Criteria 2025<\/h2>\n\n<p>When changing, I pay attention to <strong>Performance<\/strong>availability, 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 <strong>Comparison<\/strong> selected providers.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Rank<\/th>\n      <th>Hosting provider<\/th>\n      <th>Performance<\/th>\n      <th>Support<\/th>\n      <th>Price\/performance<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>1<\/td>\n      <td>webhoster.de<\/td>\n      <td>Very good<\/td>\n      <td>Very good<\/td>\n      <td>Very good<\/td>\n    <\/tr>\n    <tr>\n      <td>2<\/td>\n      <td>Strato<\/td>\n      <td>Good<\/td>\n      <td>Good<\/td>\n      <td>Good<\/td>\n    <\/tr>\n    <tr>\n      <td>3<\/td>\n      <td>IONOS<\/td>\n      <td>Good<\/td>\n      <td>Good<\/td>\n      <td>Satisfactory<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<p>I also take into account <strong>Location<\/strong> 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 <strong>Security patches<\/strong> 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.<\/p>\n\n<h2>Migration: Plan, check and activate the move<\/h2>\n\n<p>I set up the target hosting completely before I start the <strong>DNS<\/strong> 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 <strong>Downtime<\/strong> minimize.<\/p>\n\n<p>Before the go-live, I check <strong>Absolute paths<\/strong>file uploads, e-mail dispatch (SMTP instead of PHP mail), caching mechanisms and sessions. For CMS I use a <em>Search-and-replace<\/em>-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 <strong>Blue-Green<\/strong> 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.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/webhosting_kuendigung_2025_4912.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>DNS, SSL and security: avoiding stumbling blocks<\/h2>\n\n<p>Before switching, I reduce the <strong>TTL<\/strong> 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 <strong>Risk<\/strong> to reduce.<\/p>\n\n<p>At <strong>CAA<\/strong>-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 <strong>API keys<\/strong> and webhooks and enter new callback URLs in third-party dashboards.<\/p>\n\n<h2>Invoices, direct debits and confirmation: finalize cleanly<\/h2>\n\n<p>After the termination, I never rely on mere <strong>Silence<\/strong>but 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 <a href=\"https:\/\/webhosting.de\/en\/1blu-terminate-complete-instructions-for-contract-termination-2025\/\">Cancel 1blu<\/a> special steps must be observed.<\/p>\n\n<p>I clarify whether it is <strong>Pro rata refunds<\/strong> 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 <strong>Deletion of personal data<\/strong> and close open support tickets. If domains continue to run separately, I check their new billing cycles so that there are no duplicate costs.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/webhosting-kuendigen-2025-4837.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Checklist 2025: step by step without gaps<\/h2>\n\n<p>I start with the <strong>Contract data<\/strong> 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 <strong>Receipts<\/strong> on.<\/p>\n\n<p>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 <strong>SEO<\/strong>-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.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/webhosting-kuendigen-4217.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Professional tips for backups and relocation<\/h2>\n\n<p>I rely on automated <strong>Backup plans<\/strong> 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 <strong>Problems<\/strong> early on.<\/p>\n\n<p>I activate <strong>Monitoring<\/strong> (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.<\/p>\n\n<h2>Summary: clear steps, secure termination<\/h2>\n\n<p>You give structured notice, ensure <strong>Data<\/strong> 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 <strong>Feeling<\/strong>.<\/p>","protected":false},"excerpt":{"rendered":"<p>Secure web hosting termination made easy: deadlines, backups &amp; changing provider to webhoster.de at a glance.<\/p>","protected":false},"author":1,"featured_media":12518,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[995],"tags":[],"class_list":["post-12525","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hilfe"],"acf":[],"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/12525","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/comments?post=12525"}],"version-history":[{"count":1,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/12525\/revisions"}],"predecessor-version":[{"id":12575,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/12525\/revisions\/12575"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/12518"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=12525"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=12525"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=12525"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}