Email & SMTP
MailWizz Migration to New Server
Move an existing MailWizz installation — lists, campaigns, templates and settings — to a new server.
The Problem
You're changing hosting or VPS provider and need MailWizz, with all its history and subscriber lists, working identically on the new box without losing data or breaking sending.
About this problem
Moving MailWizz to a new server means transferring not just files and a database, but every subscriber list, campaign history, and template — and getting any part of that wrong risks losing real data or breaking sending at the worst possible time, right after a server switch.
This typically comes up when changing hosting or VPS providers for cost, performance, or reliability reasons, independent of anything being wrong with MailWizz itself.
What's Included
- Full backup and transfer of the MailWizz database and files
- Reinstalling MailWizz on the new server with matching configuration
- Re-pointing DNS/sending server connections as needed
- Verifying lists, campaigns and templates all transferred intact
What's NOT Included
- Purchasing or provisioning the new server itself
- Upgrading MailWizz to a newer version as part of the move (can be scoped separately)
- Downtime beyond what's unavoidable during cutover
How It Works
- Take a full backup of the MailWizz database and all application files on the current server.
- Install and configure MailWizz on the new server to match the existing environment and settings.
- Restore the database and files, preserving subscriber lists, campaigns, and templates intact.
- Re-point DNS and sending server connections to work correctly from the new server.
- Verify lists, past campaigns, and templates all transferred correctly before decommissioning the old server.
In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.
Frequently Asked Questions
- Will I lose my subscriber lists when migrating MailWizz to a new server?
- Not if the migration is done properly with a full database backup and restore — lists, campaign history, and templates all live in the database and transfer along with it.
- How much downtime does a MailWizz server migration cause?
- With careful planning, minimal — the old server can usually stay live until the new one is fully verified, avoiding any gap in sending capability.
- Can I upgrade MailWizz to a newer version during the migration?
- It's possible to combine both, but it's generally safer to migrate first and upgrade separately afterwards, so any issues can be isolated to one change at a time.
- Do I need to reconfigure my sending servers after migrating?
- Yes, sending server connections (SMTP/API) typically need to be re-verified or reconfigured to work correctly from the new server's IP and environment.
- What should I check after a MailWizz migration to confirm it worked?
- That all subscriber lists and counts match, past campaigns and their stats are intact, templates render correctly, and a new test campaign sends successfully.
- Who provides the new server for a MailWizz migration?
- That's arranged separately by you — this service handles the migration itself, not sourcing or paying for the new hosting.