{"id":22569,"date":"2026-08-28T12:23:38","date_gmt":"2026-08-28T10:23:38","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22569"},"modified":"2026-08-28T12:23:39","modified_gmt":"2026-08-28T10:23:39","password":"","slug":"export-phpmyadmin-database","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/webhosting-cpanel\/phpmyadmin-datenbank-exportieren\/","title":{"rendered":"Export database with phpMyAdmin"},"content":{"rendered":"<p class=\"wp-block-paragraph\">With phpMyAdmin, you can export a database of your CURIAWEB web hosting as a file. Such an export is useful, for example, before making changes to a live database, manually migrating a website, or creating an additional backup of the database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For typical website databases, this is suitable for <strong>SQL format<\/strong>. The exported SQL file contains the database structure and \u2013 depending on the selected settings \u2013 the saved data and can later be imported back into a database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we will show you step by step how to select the correct database in phpMyAdmin, create an export, and then check whether the backup file was actually downloaded.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> A phpMyAdmin export backs up the database, but not automatically your website files, emails, or the entire hosting account. For a complete manual website backup, database-driven websites typically require both the website files and the database.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">When is a database export useful?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An export is particularly useful if you want to back up a database before modifying it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical use cases are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>before manual changes with phpMyAdmin<\/li>\n\n\n\n<li>before major changes to a website<\/li>\n\n\n\n<li>prior to manual database cleanup<\/li>\n\n\n\n<li>during a website migration<\/li>\n\n\n\n<li>before importing other data<\/li>\n\n\n\n<li>for an additional local backup of the database<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Basic rule:<\/strong> With a production database, the rule is: export first, then modify.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What does an SQL export contain?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A SQL file contains statements that can be used to restore the structure and data of a database or to import them into another database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the export options, this may include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Table structures<\/li>\n\n\n\n<li>Table contents<\/li>\n\n\n\n<li>Indices<\/li>\n\n\n\n<li>additional SQL statements required for the exported database objects<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a typical export file might be named:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>kunde_wordpress.sql<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You do not need to manually edit the SQL file for a regular backup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Log in to cPanel<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Log in to your CURIAWEB cPanel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Databases \u2192 phpMyAdmin<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">phpMyAdmin is being opened for your hosting account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find a general introduction to the user interface under <a href=\"\/en\/help\/web-hosting-cpanel\/phpmyadmin-verwenden\/\">Use phpMyAdmin in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Select correct database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the left navigation of phpMyAdmin, select the database you want to export.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the full name carefully.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a database name can look like this:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>WordPress customer<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If there are multiple websites in your hosting account, a corresponding number of databases may be displayed.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Do not rely on guesswork when dealing with multiple similarly named databases. First, check which database is actually being used by the website in question.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">How do I find the database of my WordPress website?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In WordPress, the used database name is usually in the file:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-config.php<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">on file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The relevant entry is:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>DB_NAME<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The value stored there should correspond to the database name you select in phpMyAdmin.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Safety:<\/strong> <code>wp-config.php<\/code> contains sensitive information in addition to the database name. Do not publish its complete contents.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">3. Check if the correct database is open<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After selecting the database, phpMyAdmin displays its tables.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the database name again and verify whether the existing tables match the expected application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, in WordPress, tables such as:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>wp_posts\nwp_options\nwp_users\nwp_postmeta<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">to exist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, the table prefix is not required <code>wp_<\/code> loud. A WordPress installation can use a different prefix.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Open export function<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When the correct database is selected, open the section at the top of phpMyAdmin:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Export<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">phpMyAdmin will then show you the available export methods and the export format.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5. Choose Fast or Custom<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">phpMyAdmin typically offers two export methods:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Fast<\/strong> and <strong>Adapted<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Which variant makes sense depends on what you plan to do with the export.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Fast<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The method <strong>Fast<\/strong> uses the intended default options and is often sufficient for an uncomplicated export of a normal database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you simply want to export a complete database and have no special requirements, this method is a good starting point.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Adapted<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">With <strong>Adapted<\/strong> you get access to additional export options.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can use this, for example, to specify more precisely which tables are exported or how the SQL file should be generated.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> Do not automatically use the customized export just because more options are available there. For a normal backup, a simple full export is often the better and less error-prone choice.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">6. Select SQL as format<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a normal backup or migration of a MySQL-compatible website database, choose the format:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>SQL<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">SQL is suitable for later importing the database structure and the stored data back into a MySQL-compatible database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Other export formats can be useful for special tasks, but are usually not the first choice for a classic database backup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Start export<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Check again:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>correct database<\/li>\n\n\n\n<li>desired export method<\/li>\n\n\n\n<li>Format <strong>SQL<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Then start the export.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your browser should download the generated export file.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">8. Actually check download<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Do not assume the export was successful just because you clicked the export button.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then check in the download folder or in your browser's download display to see if the file is actually there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a file could be named like this:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>kunde_wordpress.sql<\/code><\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> A clicked export is not yet a verified backup. Check whether the file was actually downloaded.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">9. Check file size<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Additionally, check the size of the downloaded file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Size alone does not prove that a backup is complete and error-free, but it can make obvious problems visible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you receive an unexpectedly tiny file for a large production database, for example, you should verify the export before relying on that backup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A small SQL file is not automatically faulty<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The size of a database depends heavily on the application and the stored content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A small website can have a correspondingly small database.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, do not judge an export solely by its file size.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Name the SQL file meaningfully<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For later backups, it can be helpful to add a date to the filename.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>kunde_wordpress_2026-08-28.sql<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This makes it easier for you to distinguish between several backup states.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not use database passwords or other confidential access credentials in the filename.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">11. Keep SQL file safe<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A database backup may contain confidential content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the website, this may include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>User information<\/li>\n\n\n\n<li>Email addresses<\/li>\n\n\n\n<li>Order details<\/li>\n\n\n\n<li>Website settings<\/li>\n\n\n\n<li>internal application data<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">be saved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, do not treat an SQL backup like a publicly accessible file.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Safety:<\/strong> Do not upload database backups to a publicly accessible website directory. A backup file does not belong unprotected in <code>public_html<\/code>.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Do not leave backups publicly accessible on the webspace<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When you need to transfer an SQL file to the server for a migration, it should not remain unnecessarily long in a publicly accessible directory.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Remove no longer needed temporary backup files after completing the work.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">12. Use custom export<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you the method <strong>Adapted<\/strong> you select, phpMyAdmin provides additional options.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This method is useful, for example, if you only want to export certain tables or have special requirements for the export file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When performing a full website database backup, you should make sure not to accidentally exclude required tables.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Include all tables on a website<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A web application can have significantly more tables than the obvious core tables.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, WordPress plugins can create additional tables.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you need a complete database backup, you should not exclude such tables just because you do not know their names.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> An export of only the known WordPress core tables is not automatically a complete backup of the entire WordPress database. Plugins may use their own tables.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Export only specific tables<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you intentionally need only individual tables, you can select them during the customized export.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can be useful, for example, for a targeted analysis or transfer of individual data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, such a partial export should be clearly distinguished from a complete database backup.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Use compressed export<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the phpMyAdmin configuration, compression options may be offered for customized exports.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compression can reduce the size of the downloaded backup file, especially for larger databases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Which options are actually available depends on the server and phpMyAdmin configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">SQL file or compressed file?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the selected export option, the result can be a normal SQL file or a compressed backup file, for example.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>database.sql\ndatabase.sql.gz\ndatabase.sql.zip<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Which variant you use depends, among other things, on the database size and the later import procedure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">DROP statements in custom export<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">During a customized SQL export, options can be offered that, before creating tables, corresponding <code>DROP<\/code>- Include instructions in the export file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Such instructions can initially remove existing objects with the same name during a later restoration.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Options with <code>DROP<\/code> you should not activate this thoughtlessly. During a later import, this could cause existing tables to be removed before they are recreated from the backup.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding CREATE TABLE and INSERT<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A typical SQL backup can contain different types of statements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>CREATE TABLE\n\u2192 creates a table structure\n\nINSERT\n\u2192 inserts stored records<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For a complete recovery, normally both the required structure and the data are needed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not \u201eclean up\u201c the export manually\u201c<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Do not open a SQL backup file with just any text editor and delete sections in it on suspicion just because they seem unfamiliar to you.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can make the backup incomplete or unusable during a later import.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Can I open the SQL file?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An uncompressed SQL file is fundamentally a text file and can be viewed with suitable tools.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, with large databases, it can be very extensive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To check a normal backup, it is not necessary to manually read through all SQL statements.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Export before a change with phpMyAdmin<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When planning a manual change to a production database, the following procedure is recommended:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open phpMyAdmin.<\/li>\n\n\n\n<li>W\u00e4hle die richtige Datenbank.<\/li>\n\n\n\n<li>Exportiere die Datenbank.<\/li>\n\n\n\n<li>Kontrolliere den erfolgreichen Download.<\/li>\n\n\n\n<li>Bewahre die Sicherung sicher auf.<\/li>\n\n\n\n<li>F\u00fchre erst danach die geplante \u00c4nderung durch.<\/li>\n\n\n\n<li>Teste die Website unmittelbar nach der \u00c4nderung.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Wie du mit Tabellen und Datens\u00e4tzen arbeitest, erkl\u00e4ren wir unter <a href=\"\/en\/help\/web-hosting-cpanel\/phpmyadmin-verwenden\/\">Use phpMyAdmin in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Export f\u00fcr eine Website-Migration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bei einer manuellen Migration einer datenbankbasierten Website ben\u00f6tigst du normalerweise mindestens zwei Bestandteile:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Website-Dateien\n        +\nDatenbank\n        =\nwesentliche Bestandteile der Website<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Die Website-Dateien kannst du beispielsweise \u00fcber den cPanel-Dateimanager oder FTP \u00fcbertragen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Die Datenbank exportierst du \u00fcber phpMyAdmin und importierst sie anschlie\u00dfend in die Datenbank der neuen Hosting-Umgebung.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wie du Dateien \u00fcber cPanel herunterl\u00e4dst, erkl\u00e4ren wir unter <a href=\"\/en\/help\/web-hosting-cpanel\/upload-download-edit-files\/\">Upload, download, and edit files in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Neue Datenbank am Ziel erstellen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bei einer manuellen Migration muss am Ziel gegebenenfalls zun\u00e4chst eine neue Datenbank eingerichtet werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find the procedure under <a href=\"\/en\/help\/web-hosting-cpanel\/create-mysql-database\/\">Create MySQL database in cPanel<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Zus\u00e4tzlich ben\u00f6tigt die Anwendung normalerweise einen Datenbankbenutzer mit den erforderlichen Berechtigungen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Diesen Schritt erkl\u00e4ren wir unter <a href=\"\/en\/help\/web-hosting-cpanel\/create-and-assign-mysql-user\/\">Create MySQL user and assign to a database<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Export anschlie\u00dfend importieren<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Die erzeugte SQL-Datei kannst du anschlie\u00dfend in eine geeignete Zieldatenbank importieren.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The complete instructions will follow below <a href=\"\/en\/help\/web-hosting-cpanel\/import-phpmyadmin-database\/\">Importing a database with phpMyAdmin<\/a>.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> Pr\u00fcfe vor dem Import immer die ausgew\u00e4hlte Zieldatenbank. Eine SQL-Datei kann abh\u00e4ngig von ihrem Inhalt vorhandene Daten und Tabellen ver\u00e4ndern.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Export ist kein automatischer Umzug<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn du eine Datenbank exportierst, wird die Website dadurch nicht automatisch auf einen anderen Server \u00fcbertragen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei einer manuellen Migration m\u00fcssen unter anderem die Website-Dateien \u00fcbertragen, die Datenbank am Ziel eingerichtet beziehungsweise importiert und die Anwendung mit den neuen Datenbankzug\u00e4ngen verbunden werden.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress nach einer Datenbankmigration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn sich Datenbankname, Datenbankbenutzer, Passwort oder Datenbankhost am neuen Standort \u00e4ndern, muss die WordPress-Konfiguration entsprechend angepasst werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Die relevanten Werte befinden sich normalerweise in:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>wp-config.php<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These include:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>DB_NAME\nDB_USER\nDB_PASSWORD\nDB_HOST<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c4ndere diese Werte nur entsprechend den tats\u00e4chlich eingerichteten Datenbankzug\u00e4ngen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Export ist nicht dasselbe wie Backup des gesamten Hosting-Accounts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ein phpMyAdmin-Export umfasst nur die ausgew\u00e4hlte Datenbank beziehungsweise die ausgew\u00e4hlten Datenbankobjekte.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Er sichert nicht automatisch:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Website files<\/li>\n\n\n\n<li>Bilder und Uploads im Dateisystem<\/li>\n\n\n\n<li>Plugins und Themes als Dateien<\/li>\n\n\n\n<li>E-Mail-Postf\u00e4cher<\/li>\n\n\n\n<li>FTP-Konten<\/li>\n\n\n\n<li>cPanel-Einstellungen<\/li>\n\n\n\n<li>den gesamten Hosting-Account<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Bezeichne einen einzelnen SQL-Export deshalb nicht als vollst\u00e4ndige Sicherung des gesamten Webhostings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress-Datenbankexport sichert keine Mediendateien<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress speichert Informationen \u00fcber Medien in der Datenbank, die eigentlichen hochgeladenen Bild-, PDF- oder anderen Mediendateien befinden sich jedoch normalerweise im Dateisystem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ein reiner Datenbankexport reicht deshalb nicht aus, um eine WordPress-Website vollst\u00e4ndig wiederherzustellen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Export nach gr\u00f6\u00dferen \u00c4nderungen erneut erstellen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eine SQL-Sicherung ist immer nur ein Abbild des Datenbankzustands zum Zeitpunkt des Exports.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn sich die Website danach weiter ver\u00e4ndert, enth\u00e4lt die \u00e4ltere Sicherung diese neuen Daten nicht.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei dynamischen Websites k\u00f6nnen beispielsweise neue Bestellungen, Benutzer, Kommentare oder Einstellungen hinzukommen.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> Bei einer aktiven Website kann eine Datenbanksicherung schnell veralten. F\u00fcr eine Migration sollte deshalb der Zeitpunkt des finalen Exports sorgf\u00e4ltig gew\u00e4hlt werden.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Besonderheit bei Onlineshops und stark dynamischen Websites<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bei einem Onlineshop oder einer Website mit laufenden Benutzeraktivit\u00e4ten k\u00f6nnen sich Daten w\u00e4hrend einer Migration weiter ver\u00e4ndern.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn nach deinem Export neue Bestellungen oder andere Datens\u00e4tze entstehen, befinden sich diese nicht in der bereits exportierten SQL-Datei.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Eine Migration solcher Systeme ben\u00f6tigt deshalb eine abgestimmte Vorgehensweise, damit zwischen Export und Umschaltung keine relevanten Daten verloren gehen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Exportdatei enth\u00e4lt sensible Daten<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eine SQL-Sicherung kann wesentlich sensibler sein, als ihr Dateiname vermuten l\u00e4sst.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Abh\u00e4ngig von der Anwendung kann sie personenbezogene und gesch\u00e4ftliche Daten enthalten.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Speichere und \u00fcbertrage solche Dateien entsprechend gesch\u00fctzt und l\u00f6sche nicht mehr ben\u00f6tigte tempor\u00e4re Kopien.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Exportdatei nicht per \u00f6ffentlichem Link versenden<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Lege eine SQL-Datei nicht in ein \u00f6ffentlich zug\u00e4ngliches Verzeichnis und verschicke anschlie\u00dfend einfach deren URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn eine Datenbanksicherung \u00fcbertragen werden muss, verwende einen daf\u00fcr geeigneten gesch\u00fctzten \u00dcbertragungsweg.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Export funktioniert nicht<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn beim Export keine Datei heruntergeladen wird, pr\u00fcfe zun\u00e4chst:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ob die richtige Datenbank ausgew\u00e4hlt wurde<\/li>\n\n\n\n<li>ob dein Browser einen Download blockiert oder an anderer Stelle gespeichert hat<\/li>\n\n\n\n<li>ob phpMyAdmin eine Fehlermeldung anzeigt<\/li>\n\n\n\n<li>ob die Datenbank beziehungsweise der Export ungew\u00f6hnlich gro\u00df ist<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Notiere eine angezeigte Fehlermeldung vollst\u00e4ndig, bevor du Einstellungen auf Verdacht ver\u00e4nderst.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Gro\u00dfe Datenbank exportieren<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bei sehr gro\u00dfen Datenbanken kann ein browserbasierter Export \u00fcber phpMyAdmin je nach Umgebung an praktische oder technische Grenzen sto\u00dfen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In solchen F\u00e4llen sollte zuerst gepr\u00fcft werden, wie gro\u00df die Datenbank tats\u00e4chlich ist und an welcher Stelle der Export scheitert.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ver\u00e4ndere PHP-Limits nicht wahllos, ohne die konkrete Ursache zu kennen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Export erfolgreich \u2013 ist die Sicherung damit garantiert wiederherstellbar?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ein erfolgreicher Download ist ein wichtiger erster Schritt, beweist aber nicht vollst\u00e4ndig, dass sich die Sicherung sp\u00e4ter unter allen Umst\u00e4nden problemlos wiederherstellen l\u00e4sst.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Eine belastbare Backup-Strategie ber\u00fccksichtigt deshalb auch die Wiederherstellbarkeit der Sicherungen.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> Eine Sicherung ist besonders wertvoll, wenn nicht nur ihre Existenz, sondern auch das vorgesehene Wiederherstellungsverfahren bekannt ist.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">SQL-Datei nicht nach dem Export l\u00f6schen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn du den Export ausdr\u00fccklich als Sicherung vor einer \u00c4nderung erstellt hast, behalte ihn mindestens so lange, bis die \u00c4nderung erfolgreich abgeschlossen und die Website \u00fcberpr\u00fcft wurde.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Andernfalls entfernst du m\u00f6glicherweise genau die R\u00fcckfallebene, die du vor der \u00c4nderung geschaffen hast.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Mehrere Sicherungsst\u00e4nde auseinanderhalten<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn du mehrere Exporte erstellst, verwende eindeutige Dateinamen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>kunde_wordpress_vor-update_2026-08-28.sql\nkunde_wordpress_vor-migration_2026-08-28.sql<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">So kannst du sp\u00e4ter besser nachvollziehen, zu welchem Zeitpunkt und Zweck eine Sicherung erstellt wurde.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Empfohlener Ablauf f\u00fcr einen normalen Datenbankexport<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Log in to cPanel.<\/li>\n\n\n\n<li>Open <strong>Databases \u2192 phpMyAdmin<\/strong>.<\/li>\n\n\n\n<li>W\u00e4hle links die richtige Datenbank.<\/li>\n\n\n\n<li>Kontrolliere Datenbankname und Tabellen.<\/li>\n\n\n\n<li>Open <strong>Export<\/strong>.<\/li>\n\n\n\n<li>W\u00e4hle f\u00fcr einen normalen vollst\u00e4ndigen Export <strong>Fast<\/strong>.<\/li>\n\n\n\n<li>Choose <strong>SQL<\/strong> als Format.<\/li>\n\n\n\n<li>Starte den Export.<\/li>\n\n\n\n<li>Kontrolliere, ob die Datei heruntergeladen wurde.<\/li>\n\n\n\n<li>Pr\u00fcfe Dateiname und Plausibilit\u00e4t der Dateigr\u00f6\u00dfe.<\/li>\n\n\n\n<li>Bewahre die Datei sicher auf.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Empfohlener Ablauf vor einer Datenbank\u00e4nderung<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Identifiziere die richtige produktive Datenbank.<\/li>\n\n\n\n<li>Erstelle einen aktuellen SQL-Export.<\/li>\n\n\n\n<li>Kontrolliere den Download.<\/li>\n\n\n\n<li>Bewahre die unver\u00e4nderte Exportdatei auf.<\/li>\n\n\n\n<li>F\u00fchre die geplante \u00c4nderung durch.<\/li>\n\n\n\n<li>Test the website immediately afterwards.<\/li>\n\n\n\n<li>Behalte die Sicherung, bis du sicher bist, dass die \u00c4nderung korrekt funktioniert.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">When should you contact support?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn ein Export nicht funktioniert oder du bei einer produktiven Datenbank nicht sicher bist, welche Datenbank beziehungsweise Tabellen gesichert werden m\u00fcssen, solltest du nicht auf Verdacht \u00c4nderungen durchf\u00fchren.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For an analysis, the following information is particularly helpful:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>affected domain or application<\/li>\n\n\n\n<li>full database name<\/li>\n\n\n\n<li>ungef\u00e4hre Datenbankgr\u00f6\u00dfe, sofern bekannt<\/li>\n\n\n\n<li>gew\u00e4hlte Exportmethode<\/li>\n\n\n\n<li>gew\u00e4hltes Exportformat<\/li>\n\n\n\n<li>exact error message<\/li>\n\n\n\n<li>ob \u00fcberhaupt eine Datei heruntergeladen wird<\/li>\n\n\n\n<li>ob der Export f\u00fcr eine Sicherung, Migration oder andere Aufgabe ben\u00f6tigt wird<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u00dcbermittle keine Datenbankpassw\u00f6rter und stelle SQL-Sicherungen mit sensiblen Inhalten nicht \u00f6ffentlich bereit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eine Datenbank exportierst du im CURIAWEB-cPanel \u00fcber <strong>Databases \u2192 phpMyAdmin<\/strong>. W\u00e4hle zuerst die richtige Datenbank und \u00f6ffne anschlie\u00dfend den Bereich <strong>Export<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">F\u00fcr einen normalen vollst\u00e4ndigen Export ist die Methode <strong>Fast<\/strong> mit dem Format <strong>SQL<\/strong> h\u00e4ufig ausreichend. Wenn du bestimmte Tabellen oder zus\u00e4tzliche Exportoptionen ben\u00f6tigst, kannst du stattdessen <strong>Adapted<\/strong> use.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kontrolliere nach dem Export, ob die Sicherungsdatei tats\u00e4chlich heruntergeladen wurde, und bewahre sie gesch\u00fctzt auf. SQL-Dateien k\u00f6nnen sensible Website- und Benutzerdaten enthalten und geh\u00f6ren nicht in \u00f6ffentlich erreichbare Verzeichnisse.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Beachte au\u00dferdem, dass ein phpMyAdmin-Export ausschlie\u00dflich die Datenbank sichert. F\u00fcr eine vollst\u00e4ndige manuelle Sicherung oder Migration einer datenbankbasierten Website ben\u00f6tigst du zus\u00e4tzlich die zugeh\u00f6rigen Website-Dateien.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Vor manuellen \u00c4nderungen an einer produktiven Datenbank gilt deshalb: <strong>richtige Datenbank pr\u00fcfen, exportieren, Download kontrollieren und erst danach \u00c4nderungen durchf\u00fchren.<\/strong><\/p>","protected":false},"excerpt":{"rendered":"<p>Mit phpMyAdmin kannst du eine Datenbank deines CURIAWEB-Webhostings als Datei exportieren. Ein solcher Export ist beispielsweise sinnvoll, bevor du \u00c4nderungen an einer produktiven Datenbank vornimmst, eine Website manuell migrierst oder eine zus\u00e4tzliche Sicherung der Datenbank erstellen m\u00f6chtest. F\u00fcr typische Website-Datenbanken eignet sich daf\u00fcr das SQL-Format. Die exportierte SQL-Datei enth\u00e4lt die Datenbankstruktur und \u2013 abh\u00e4ngig von [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[78],"doc_tag":[],"class_list":["post-22569","docs","type-docs","status-publish","hentry","doc_category-webhosting-cpanel"],"year_month":"2026-09","word_count":2861,"total_views":"5","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"Webhosting &amp; cPanel","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/webhosting-cpanel\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22569","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22569"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22569\/revisions"}],"predecessor-version":[{"id":22571,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22569\/revisions\/22571"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22569"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22569"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22569"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}