How to Get a Website Archive and Database Dump from Beget for Hosting Migration

Migrating your website to a new hosting provider is one of the most critical operations you'll perform as a site owner or systems administrator. Done correctly, it results in zero data loss and minimal downtime. Done poorly, it can mean corrupted databases, broken configurations, and hours of troubleshooting.

This step-by-step guide walks you through the complete process of exporting your website files and database from Beget, and successfully importing everything to a new hosting environment — whether you're moving to a VPS Hosting plan, a Dedicated Server, or a Shared Web Hosting package.

Why Proper Migration Planning Matters

Before touching a single file, understand what a complete website migration involves:

• Website files — all PHP scripts, HTML, CSS, JavaScript, images, uploads, and theme/plugin directories
• Database dump — a full SQL export of your MySQL or MariaDB database containing all your content, user data, and settings
• Configuration files — environment-specific settings that connect your application to the database
• DNS records — pointing your domain to the new server after migration is complete

Skipping any of these steps is the most common cause of broken migrations. Follow this guide in order, and you'll have a clean, complete copy of your site ready to deploy.

Step 1: Download Your Website Files from Beget

You have two reliable methods for extracting your website files from Beget. Choose the one that best suits your technical comfort level and the size of your site.

Method 1: Using the Beget File Manager (Browser-Based)

This is the fastest approach for small-to-medium websites and requires no additional software.

1. Log in to your Beget control panel at beget.com.
2. Navigate to File Manager from the main dashboard.
3. Locate your website's root directory — this is typically found under the public_html folder or a subdirectory named after your domain.
4. Select all files and folders within your website's directory.
5. Right-click and choose Compress or Archive to package everything into a single .zip file.
6. Once the archive is created, click Download to save the .zip file to your local machine.

> Pro Tip: For large websites (over 500 MB), the File Manager may time out during compression. In that case, use Method 2 below or compress via SSH if you have shell access.

Method 2: Using an FTP Client (FileZilla or Similar)

FTP is the preferred method for large websites, as it handles transfers more reliably and gives you full control over the process.

1. Download and install FileZilla (free, cross-platform) from filezilla-project.org.
2. Log in to your Beget account and navigate to Settings → FTP Settings to retrieve your FTP credentials:

• Host: your server hostname or IP address
• Username: your FTP username
• Password: your FTP password
• Port: 21 (standard FTP) or 22 (SFTP, recommended for security)

1. Open FileZilla and enter your credentials in the Quickconnect bar at the top.
2. Once connected, navigate to the public_html directory (or your site's root folder) in the right-hand panel.
3. Select all files and folders, right-click, and choose Download.
4. FileZilla will transfer all files to the local directory shown in the left-hand panel.

> Security Note: Always prefer SFTP (port 22) over plain FTP when available. SFTP encrypts your credentials and file transfers, preventing interception.

Step 2: Export Your Database from Beget via phpMyAdmin

Your database contains everything that makes your website dynamic — posts, pages, user accounts, orders, settings, and more. A missing or corrupted database export will break your site completely.

1. Log in to your Beget control panel and navigate to Databases.
2. Locate the database associated with your website and click phpMyAdmin to open the database management interface.
3. In the left-hand panel of phpMyAdmin, click on your database name to select it. Ensure you've selected the correct database — you should see all your tables listed.
4. Click the Export tab in the top navigation menu.
5. Choose your export method:

• Quick Export — Exports the entire database as a .sql file using default settings. Suitable for most migrations.
• Custom Export — Gives you control over which tables to include, the output format (SQL, CSV, XML), and compression options (gzip or zip). Recommended for large databases or when you need a compressed file.

1. For the Format, ensure SQL is selected.
2. If using Custom export, enable gzip compression under the Output section to reduce file size.
3. Click Go to generate and download the .sql (or .sql.gz) dump file to your computer.

> Important: Keep this .sql file safe. It is the complete snapshot of your website's data. Store a backup copy in a separate location before proceeding.

Step 3: Upload Files and Import the Database to Your New Host

With your files and database dump in hand, you're ready to set up your website on the new server.

3a: Upload Website Files to the New Host

Via FTP/SFTP:

1. Connect to your new hosting server using FileZilla with the FTP/SFTP credentials provided by your new host.
2. Navigate to the web root directory of your new account — typically public_html, www, or htdocs.
3. Upload all files from your local backup to this directory.

Via the New Host's File Manager:

1. Log in to your new hosting control panel (cPanel, DirectAdmin, or a custom panel).
2. Open the File Manager, navigate to public_html, and use the Upload function.
3. Upload your .zip archive and then extract it directly on the server.

> If you're migrating to a VPS with cPanel, the cPanel File Manager provides a straightforward upload-and-extract workflow that works well for most website sizes.

3b: Create a New Database and Import the Dump

1. In your new hosting control panel, navigate to MySQL Databases (or equivalent).
2. Create a new database — note down the database name.
3. Create a new database user with a strong password.
4. Assign the user to the database with full privileges.
5. Open phpMyAdmin for the new database.
6. Click the Import tab.
7. Click Choose File and select your .sql (or .sql.gz) dump file.
8. Leave the default settings and click Go.
9. Wait for the import to complete — large databases may take several minutes.

> Troubleshooting: If you receive a "max upload size" error during import, you can import via the command line using: mysql -u username -p database_name < your_dump.sql

Step 4: Update Your Website Configuration Files

This is the step most beginners forget — and it's the one that causes the most post-migration errors. Your website's configuration file contains the database connection details (hostname, database name, username, and password) from your old hosting environment. These must be updated to match your new hosting environment.

WordPress (wp-config.php)

Open wp-config.php in your website's root directory and update the following lines:

define( 'DB_NAME', 'your_new_database_name' );
define( 'DB_USER', 'your_new_database_user' );
define( 'DB_PASSWORD', 'your_new_database_password' );
define( 'DB_HOST', 'localhost' );

Joomla (configuration.php)

public $host = 'localhost';
public $db = 'your_new_database_name';
public $user = 'your_new_database_user';
public $password = 'your_new_database_password';

Custom PHP Applications (config.php or .env)

Update the database constants or environment variables to reflect the new credentials. If your application uses a .env file (common in Laravel, Symfony, etc.), update the DB_* variables accordingly.

> After updating configuration files, clear any application cache to prevent stale data from causing errors.

Step 5: Test Your Website Before Updating DNS

Before pointing your domain to the new server, verify that everything works correctly. Switching DNS before testing is a common mistake that causes visible downtime for your visitors.

Testing methods:

• Hosts file modification — Temporarily edit your local /etc/hosts (Linux/macOS) or C:WindowsSystem32driversetchosts (Windows) file to point your domain to the new server's IP address. This lets you preview the site on the new server without affecting live visitors.
• Temporary URL — Many hosting providers offer a temporary subdomain or IP-based URL to test your site before DNS propagation.
• Check all functionality — Test login, forms, checkout processes, media loading, and any dynamic features.

Step 6: Update DNS and Finalize the Migration

Once you've confirmed the site works correctly on the new server:

1. Log in to your domain registrar or DNS management panel.
2. Update the A record to point to your new server's IP address.
3. If using nameservers, update them to those provided by your new host.
4. DNS propagation typically takes 24–48 hours, though it's often much faster.

> If you registered your domain through AlexHost, you can manage DNS records directly from the Domain Registration dashboard — making the cutover process straightforward and centralized.

Step 7: Post-Migration Checklist

Run through this checklist after your migration is complete:

• [ ] All website files uploaded and accessible
• [ ] Database imported successfully with no errors
• [ ] Configuration files updated with new database credentials
• [ ] Website tested and functioning on the new server
• [ ] DNS updated and propagated
• [ ] SSL certificate installed and HTTPS working
• [ ] Email accounts recreated or migrated (if applicable)
• [ ] Old hosting account kept active for at least 48–72 hours as a fallback

> SSL Note: After migration, ensure your SSL certificate is active on the new host. AlexHost offers SSL Certificates that can be quickly provisioned for your domain, ensuring your site remains secure and trusted by browsers from day one.

Common Migration Mistakes to Avoid

Final Thoughts

Migrating a website from Beget to a new hosting provider is a methodical process that rewards careful preparation. By following the steps in this guide — downloading your files, exporting your database, uploading to the new server, updating configuration files, and testing before DNS cutover — you can execute a seamless migration with zero data loss and minimal downtime.

Whether you're upgrading to a high-performance VPS Hosting plan for better speed and control, or scaling up to a Dedicated Server for maximum resources, AlexHost provides the infrastructure and support to make your migration as smooth as possible.

If you have questions about your specific setup or need assistance with the migration process, don't hesitate to reach out to the AlexHost support team — we're here to help.