{"id":17356,"date":"2026-02-12T18:50:13","date_gmt":"2026-02-12T13:20:13","guid":{"rendered":"https:\/\/www.skynats.com\/?p=17356"},"modified":"2026-02-12T18:50:16","modified_gmt":"2026-02-12T13:20:16","slug":"how-to-upgrade-mailwizz-safely","status":"publish","type":"post","link":"https:\/\/www.skynats.com\/blog\/how-to-upgrade-mailwizz-safely\/","title":{"rendered":"How to Upgrade MailWizz Safely"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Upgrade <a href=\"https:\/\/www.mailwizz.com\/\" type=\"link\" id=\"https:\/\/www.mailwizz.com\/\" target=\"_blank\" rel=\"noopener\"><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-secondary-color\">MailWizz<\/mark><\/a><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-secondary-color\"> <\/mark>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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we\u2019ll walk through:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pre-upgrade preparation<\/li>\n\n\n\n<li>Step-by-step web upgrade process<\/li>\n\n\n\n<li>Command-line upgrade for large databases<\/li>\n\n\n\n<li>Post-upgrade checklist<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\" id=\"h-before-you-start-critical-preparation-steps\"><strong>Before You Start: Critical Preparation Steps<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\" id=\"h-1-backup-everything-mandatory\"><strong>1. Backup Everything (Mandatory)<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Before performing any upgrade:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Backup your <strong>database<\/strong><\/li>\n\n\n\n<li>Backup all <strong>application files<\/strong><\/li>\n\n\n\n<li>Backup any custom modifications<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Never skip this step. If something goes wrong, your backup is the only recovery option.<\/p>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>2. Upgrading from MailWizz 1.x to 2.x?<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019re upgrading from <strong>MailWizz 1.x to 2.x<\/strong>, 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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Upgrade Process &#8211; Web Interface Method<\/strong><\/h3>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Step 1: Download the Correct Version<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Download the latest version of MailWizz. MailWizz archives are named like:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mailwizz-X.Y.Z.zip<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mailwizz-2.1.12.zip<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Make sure:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You are not reusing old files<\/li>\n\n\n\n<li>The version number matches your intended upgrade target<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>Step 2: Extract the Archive<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After extracting the ZIP file, you will see two folders:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>update<\/li>\n\n\n\n<li>latest<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">You only need the <strong>update<\/strong> folder for upgrading.<\/p>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\" id=\"h-step-3-pause-running-campaigns\"><strong>Step 3: Pause Running Campaigns<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Before proceeding:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pause all running campaigns<\/li>\n\n\n\n<li>Ensure no active sending process is running<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This prevents database inconsistencies during the upgrade.<\/p>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Step 4: Put Application in Offline Mode<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">From your MailWizz backend:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Backend \u2192 Settings \u2192 Common<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Enable offline mode. This prevents users or customers from interacting with the system during the upgrade.<\/p>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Step 5: Upload Update Files<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Upload the contents of the <strong>update<\/strong> folder to your server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Important:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Upload to your existing MailWizz installation directory<\/li>\n\n\n\n<li><strong>Overwrite files<\/strong><\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do NOT delete the installation folder<\/li>\n\n\n\n<li>Do NOT replace the whole folder<\/li>\n\n\n\n<li>Only overwrite existing files<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This keeps your configuration and assets intact.<\/p>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>Step 6: Run the Update Wizard<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Open your browser and visit:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>https:&#47;&#47;yourdomain.com\/backend\/index.php\/update<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Follow the on-screen update wizard<\/li>\n\n\n\n<li>Click through the steps<\/li>\n\n\n\n<li>Let the database migrations complete<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>Step 7: Verify Folder Permissions<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After the upgrade finishes: Ensure required folders are still writable by the web server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typically writable folders include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>apps\/common\/runtime<\/li>\n\n\n\n<li>apps\/frontend\/runtime<\/li>\n\n\n\n<li>apps\/backend\/runtime<\/li>\n\n\n\n<li>assets<\/li>\n\n\n\n<li>uploads<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If permissions were changed during upload, fix them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example (Linux):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>chmod -R 775 foldername\nchown -R www-data:www-data foldername<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Adjust according to your server user (Apache, nginx, etc.).<\/p>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>Updating MailWizz from Command Line<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If your database is large, running the upgrade from the web interface may:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Timeout<\/li>\n\n\n\n<li>Crash<\/li>\n\n\n\n<li>Fail during migration<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In that case, use CLI (Command Line Interface) instead.<\/p>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>When to Use CLI Upgrade<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Use this method if:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your database is very large<\/li>\n\n\n\n<li>You experience browser timeouts<\/li>\n\n\n\n<li>You are running on VPS or dedicated server<\/li>\n\n\n\n<li>You want a more stable upgrade process<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\"><strong>CLI Upgrade Steps<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Follow the same steps as above until you reach:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>https:&#47;&#47;yourdomain.com\/backend\/index.php\/update<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When you reach the update screen: Do NOT click the Submit button.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, read the first paragraph on that page. It will give you the exact command to run.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The command will look like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/usr\/bin\/php -q \/var\/www\/html\/apps\/console\/console.php update<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Your path will likely differ. For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/usr\/bin\/php -q \/home\/user\/public_html\/apps\/console\/console.php update<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>How to Run It<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">SSH into your server:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh user@yourserverip<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Navigate to your MailWizz root directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/path\/to\/mailwizz<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Run the update command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/usr\/bin\/php -q apps\/console\/console.php update<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Wait for completion.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once done:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Refresh the update page<\/li>\n\n\n\n<li>Confirm upgrade success<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Post-Upgrade Checklist<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">After the upgrade:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Disable offline mode<\/li>\n\n\n\n<li>Resume paused campaigns<\/li>\n\n\n\n<li>Test sending a campaign<\/li>\n\n\n\n<li>Test cron jobs<\/li>\n\n\n\n<li>Verify customer login works<\/li>\n\n\n\n<li>Confirm payment gateways function correctly<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\"><strong>Conclusion<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Upgrading MailWizz is straightforward if done properly. The key points are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Backup everything<\/li>\n\n\n\n<li>Use the correct update folder<\/li>\n\n\n\n<li>Overwrite files carefully<\/li>\n\n\n\n<li>Use CLI for large databases<\/li>\n\n\n\n<li>Verify permissions afterward<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">By following this process, you ensure a smooth, safe, and reliable MailWizz upgrade without downtime surprises.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Upgrading applications like MailWizz requires careful planning, backups, and proper server configuration to avoid downtime or data loss. If you\u2019re unsure about the process or want zero-risk execution, our experts are here to help. With professional <a href=\"https:\/\/www.skynats.com\/cpanel-server-management\/\" type=\"link\" id=\"https:\/\/www.skynats.com\/blog\/cpanel-server-management\/\">cpanel server management services<\/a>, we ensure seamless updates, secure configurations, and smooth performance optimization.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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\u2014quickly, securely, and without disruption.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>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\u2019ll walk through: Before You Start: Critical Preparation Steps 1. Backup Everything (Mandatory) Before performing any upgrade: Never skip this step. If [&hellip;]<\/p>\n","protected":false},"author":14,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[18,1207,1236],"class_list":["post-17356","post","type-post","status-publish","format-standard","hentry","category-blog","tag-cpanel","tag-mailwizz","tag-mailwizz-1-x-to-2-x"],"_links":{"self":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/17356","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/comments?post=17356"}],"version-history":[{"count":2,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/17356\/revisions"}],"predecessor-version":[{"id":17359,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/17356\/revisions\/17359"}],"wp:attachment":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/media?parent=17356"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/categories?post=17356"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/tags?post=17356"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}