• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Migration Manager (11 > 12.5) Not Seeing Mail-Only Domains

Enverex

Basic Pleskian
We've run into an issue with the migration manager when migrating a batch of sites from Plesk 11(.0.9) to Plesk 12.5. Basically everything is migrating over fine, except for a few domains which were set as Forwarding domains in Plesk (with Mailboxes).

These domains don't even show up in the list of Domains to Migrate in Plesk 12.5's migration manager, making it impossible to move them over.

We've tried the obvious of changing these domains to Hosted rather than Forwarding and then starting a new migration, but the domains still do not appear in the list of migratable domains.

The domains don't appear to be broken or incorrectly setup in Plesk on the old Plesk 11 server.

What's going on here?
 
Hello!

Is your Plesk 11.0 was previously upgraded from Plesk 9.x? Looks like an issue with converting of business model - process after upgrading from Plesk < 10.0 when domains become subscriptions. Plesk Migrator is able to see only subscriptions. We have an issue PMT-2867 to fix it in future Plesk Migrator release: after that all domains, even not properly converted into subscriptions for some reason, could be migrated.
 
Hi Aleksey, I spoke to your colleague Alexey Lapshin earlier and he's given me a hack to work around the issue for now. It has a rather severe side-effect, but I'll be getting back to him once we've fully tested it with the full results.
 
@Enverex,

As a work-around, create a subscription (on the source server) and assign the "forwarding domains (with mailboxes)" to that subscription and try to migrate.

If that does not work, just create the "forwarding domains (with mailboxes)" manually (on the target server) and use the Larch script to migrate all mail data.

Note that using Larch will work faster than a normal migration with the Plesk Migrator, so that will compensate the manual actions a bit or a lot.

Regards..........

PS If you have a couple of forwarding domains, the above will work quite easily. However, with a considerable number of mailboxes and/or domains, the Larch method will be cumbersome. In that case, just try to make a full backup, migrate the backup (via rsync) to the target server and try to restore the backup.
 
Back
Top