upgrade path from 8.x-2.x to 3.0.0

Hi @earthangelconsulting,
The biggest breaking change was introduced in 8.x-2.x-beta17.
In 3.0.0-beta2 there was some refactor and the notification sub-system was moved to the separate module.
It can cause problems with private_message_update_8007. I wasn't able to reproduce the problem but please let me know if it happens to you.
(As a workaround you can try skipping that update entirely by placing the return; statement as the first line of private_message_update_8007)

If you already have the 8.x-2.x-beta17 version then it should be pretty safe to upgrade.
But obviously it is recommended to create the database dump before procceeding and running the update on the dev environment first.

*running the update.php or drush updb is thre required step to update*

If you have the version before beta17 then the process may be more complicated. The update hooks should do all the needed changes, however the time of update depends on your database size. You may need to check what goes in private_message_update_8005() before running the update.

Hope that helps, thanks.

Please feel free to re-open if you face any issues during the update.

@artem_sylchuk - thank you for this detailed reply!

the client is still deliberating as to whether they use this module enough to spend the time upgrading it for D10, so i might not be able to provide you any useful feedback.

if i do end up proceeding with this, i will definitely let you know what i find!

Automatically closed - issue fixed for 2 weeks with no activity.