Upgrade MailWizz Safely to the latest version ensures better performance, security improvements, bug fixes, and access to new features. However, a careless upgrade can break your installation or corrupt data.
In this guide, we’ll walk through:
- Pre-upgrade preparation
- Step-by-step web upgrade process
- Command-line upgrade for large databases
- Post-upgrade checklist
Before You Start: Critical Preparation Steps
1. Backup Everything (Mandatory)
Before performing any upgrade:
- Backup your database
- Backup all application files
- Backup any custom modifications
Never skip this step. If something goes wrong, your backup is the only recovery option.
2. Upgrading from MailWizz 1.x to 2.x?
If you’re upgrading from MailWizz 1.x to 2.x, you must first read the official migration notes for that version jump. Major version upgrades often include structural changes that require special handling. Once reviewed, return here to follow the regular upgrade process.
Upgrade Process – Web Interface Method
Step 1: Download the Correct Version
Download the latest version of MailWizz. MailWizz archives are named like:
mailwizz-X.Y.Z.zip
Example:
mailwizz-2.1.12.zip
Make sure:
- You are not reusing old files
- The version number matches your intended upgrade target
Step 2: Extract the Archive
After extracting the ZIP file, you will see two folders:
- update
- latest
You only need the update folder for upgrading.
Step 3: Pause Running Campaigns
Before proceeding:
- Pause all running campaigns
- Ensure no active sending process is running
This prevents database inconsistencies during the upgrade.
Step 4: Put Application in Offline Mode
From your MailWizz backend:
Backend → Settings → Common
Enable offline mode. This prevents users or customers from interacting with the system during the upgrade.
Step 5: Upload Update Files
Upload the contents of the update folder to your server.
Important:
- Upload to your existing MailWizz installation directory
- Overwrite files
- Do NOT delete the installation folder
- Do NOT replace the whole folder
- Only overwrite existing files
This keeps your configuration and assets intact.
Step 6: Run the Update Wizard
Open your browser and visit:
https://yourdomain.com/backend/index.php/update
Then:
- Follow the on-screen update wizard
- Click through the steps
- Let the database migrations complete
Step 7: Verify Folder Permissions
After the upgrade finishes: Ensure required folders are still writable by the web server.
Typically writable folders include:
- apps/common/runtime
- apps/frontend/runtime
- apps/backend/runtime
- assets
- uploads
If permissions were changed during upload, fix them.
Example (Linux):
chmod -R 775 foldername
chown -R www-data:www-data foldername
Adjust according to your server user (Apache, nginx, etc.).
Updating MailWizz from Command Line
If your database is large, running the upgrade from the web interface may:
- Timeout
- Crash
- Fail during migration
In that case, use CLI (Command Line Interface) instead.
When to Use CLI Upgrade
Use this method if:
- Your database is very large
- You experience browser timeouts
- You are running on VPS or dedicated server
- You want a more stable upgrade process
CLI Upgrade Steps
Follow the same steps as above until you reach:
https://yourdomain.com/backend/index.php/update
When you reach the update screen: Do NOT click the Submit button.
Instead, read the first paragraph on that page. It will give you the exact command to run.
The command will look like this:
/usr/bin/php -q /var/www/html/apps/console/console.php update
Your path will likely differ. For example:
/usr/bin/php -q /home/user/public_html/apps/console/console.php update
How to Run It
SSH into your server:
ssh user@yourserverip
Navigate to your MailWizz root directory:
cd /path/to/mailwizz
Run the update command:
/usr/bin/php -q apps/console/console.php update
Wait for completion.
Once done:
- Refresh the update page
- Confirm upgrade success
Post-Upgrade Checklist
After the upgrade:
- Disable offline mode
- Resume paused campaigns
- Test sending a campaign
- Test cron jobs
- Verify customer login works
- Confirm payment gateways function correctly
Conclusion
Upgrading MailWizz is straightforward if done properly. The key points are:
- Backup everything
- Use the correct update folder
- Overwrite files carefully
- Use CLI for large databases
- Verify permissions afterward
By following this process, you ensure a smooth, safe, and reliable MailWizz upgrade without downtime surprises.
Upgrading applications like MailWizz requires careful planning, backups, and proper server configuration to avoid downtime or data loss. If you’re unsure about the process or want zero-risk execution, our experts are here to help. With professional cpanel server management services, we ensure seamless updates, secure configurations, and smooth performance optimization.
Need hands-on assistance beyond this Upgrade MailWizz Safely: Step-by-Step Guide? Contact our support team today and let our server specialists handle the upgrade for you—quickly, securely, and without disruption.