• 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 New Plesk migrator doesn't (always) preserve original setup date

mr-wolf

Silver Pleskian
Plesk Guru
I have modern Plesk servers containing domains that have a setup date that goes back to 2007.
These accounts must have been on several different Plesk servers in the past.

I like it a lot that Plesk over the years has preserved the original setup date.
This somehow isn't the case anymore using the new Plesk migrator.

I'm now noticing a lot of migrated accounts that have a setup date of the day of the migration.

I hope this will get fixed as I am migrating a lot of accounts in the upcoming month and I would love to keep that original date as a reference.
 
All these subscription have their "Setup Date" changed to the migration date.
It doesn't happen to all subscriptions though.
All the migrations I did today (about 5) have their "Setup Date" preserved, which is good.

With one exceptions all the ones that have lost the original "Setup Date" didn't have webhosting configured (only mail).
The exception was a subscription with hosting on a subdomain.

All domains that also had a website configured maintained their original "Setup Date"
The "No Hosting" and "Forwarding" ones got a new "Setup Date" on the new server.



upload_2017-4-8_10-39-0.png
 
Last edited:
Hello! Thank you for your feedback. I`ve reported a bug (PMT-3620) to our developers, it is going to be fixed in further Plesk Migrator updates.
 
Back
Top