Preventive Maintenance now Maintenance - OK but there are major changes

Moved from 13001 to 14006 -

I am not understanding why PM schedules were auto changed from monthly to yearly just because of the change to a maintenance module?

Also, why can I not change them if I am not in the same time zone as the server? This also needs to be fixed asap.

Behavior Changes in Migration:

Created By field will not hold any value for preventive maintenance tasks created before migration.
The Title field, which is a newly introduced unique field, will have the value as PMTASK_<ID> post-migration. Users can change it as per their requirements.
Periodic schedules will be migrated as Daily schedules.
Monthly schedules will be migrated as Yearly schedules.
Migration will fail if the SDMaintenanceManager role is created before migration.
Future events rendering will be improper for the preventive maintenance tasks created before migration and are running on the last day of the month.
Technicians having access to preventive maintenance tasks before migration will not be able to create/update maintenance post migration if their machine's time zone/personalized time zone/department site's time zone is different from the server time zone.