Plesk Server Migration: Final Verification Window Before Old System Shutdown

If you're managing a custom domain with website, email, or DNS hosting on Plesk servers, this update directly affects you. The old server infrastructure is being permanently decommissioned, and there's a narrow window left to catch any migration issues before it's too late.

The Clock Is Ticking: One Week Until Access Ends

The old Plesk server environment will be completely shut down around November 4, 2025—roughly seven days from now. Once that deadline passes, any data or configurations still residing on the old system become permanently inaccessible. This isn't a soft deadline or a gradual phase-out; it's a hard cutoff.

For most users, the migration completed smoothly. But "most" isn't "all," and that's why this final verification matters.

A Critical Issue Has Surfaced: Email Forwarding Problems

Here's something that demands immediate attention: email forwarding addresses and aliases didn't always transfer correctly. At least one customer reported missing or misconfigured forwarding rules after the migration, and investigation traced the problem back to the Plesk migration tool itself.

This appears to be an edge case rather than a widespread failure, but edge cases have a way of affecting the people who least expect them. If your domain uses email forwarding—routing messages from one address to another, or creating aliases that multiple people monitor—you need to verify those settings right now.

Check every forwarding rule. Test each alias by sending actual emails and confirming they arrive at the intended destinations. Don't assume everything transferred perfectly just because your primary inbox still receives mail.

Who Needs to Act on This

This announcement targets anyone hosting a custom domain name through Plesk servers—specifically domains where the hosting provider manages:

• Website hosting

• Email services

• DNS configuration

If your domain follows the pattern www.your-domain.com or you send email from user@your-domain.com, and these services run on Plesk infrastructure, you're in scope.

If you don't have a custom domain being hosted through these Plesk servers, you can disregard this notice entirely.

Managing DNS During Critical Migrations

When server migrations involve DNS hosting, the stakes get higher. DNS is the foundational layer that routes all internet traffic to your domain, and even small misconfigurations can cascade into major outages. If you're evaluating more robust DNS management solutions for future migrations or infrastructure changes, 👉 exploring managed DNS services with guaranteed uptime and migration support can eliminate the anxiety around these transitions.

Reliable DNS infrastructure means you can migrate hosting environments, switch servers, or update configurations without gambling on whether your domain will remain accessible throughout the process.

What to Do Before November 4

Verify your email forwarding settings immediately. Log into your Plesk control panel and review every forwarding rule and alias configured for your domain. Send test emails to each forwarding address and confirm they reach their destinations.

Alert your technical team. If you work with an IT department, support company, or webmaster, forward this information to them now. They may have additional checks to run or backup procedures to execute before the old server goes offline.

Request data retrieval if needed. If you discover missing configurations, data, or settings that didn't migrate properly, contact your hosting provider immediately. They have roughly one week to access the old server and retrieve whatever's needed. After that, it's gone.

The Reality of Migration Deadlines

Server migrations always carry risk, no matter how carefully planned. The Plesk migration tool automated most of the heavy lifting, but automation can't catch every edge case—especially with complex email configurations involving forwarding rules, aliases, and custom routing.

The seven-day window before permanent shutdown isn't arbitrary. It's the final safety net, the last chance to catch what the automated tools missed. After November 4, whatever remains on the old server disappears permanently, along with any hope of recovering it.

Don't wait until day six to start checking. Verify your settings today, escalate any issues immediately, and make sure everyone who touches your domain infrastructure knows about this deadline.