The PMv2 upgrade is a user initiated data migration required of every user, even those without PM. For users who have never had PM, the upgrade only touches bookings.
Here are some queries to assist with monitoring the progress of migrations across all users:
For questions regarding what is changing in this upgrade or why some bookings reappear on new statements, please refer to our public support doc: PMv2 Upgrade
Known Migration Issues
These are known data issues that may be encountered during PMv2 Migrations, along with possible solution steps. Note: All issues must be resolved before a user can complete the migration and issue new statements.
Bookings
Total Amount cannot be less than 0
This is issue occurs when a booking has charges that sum up to less than 0. This has never been supported, but some historical bookings got into this state for unknown reasons.
Solution: The only solution here is to adjust the charges on the booking until the sum is greater or equal to 0. The User can do this themselves, or Staff can assist. After adjusting charges, staff should use the "Try Upgrade to PMv2" button on the booking PM tab to upgrade the booking.
Statement Total no longer equal to subtotals
This issue occurs when we detect that the booking upgrade would result in a statement total difference from what was stated on the owner statements in v1.
Solution: This problem requires sysops interference. Sysops will monitor for these problems and correct as quickly as possible. If the user opens a ticket, escalate to T4 and @Joel.
Rounding error while distributing the expenses to owner statements
This issue occurs when we detect that the booking upgrade has a rounding error because the booking has only been partially remitted.
Solution: This problem requires sysops interference. Sysops will monitor for these problems and correct as quickly as possible. If the user opens a ticket, escalate to T4 and @Joel.
New expense not fully spread across owner statements
...
Solution: ...
Owner Statements
Unable to render HTML. ABCChrome page load timed out.
This issue occurs on large owner statements when rendering the statement to PDF takes too long and our service gives up on waiting.
Solution: The user may attempt to download the PDF copy of the statement first if they wish to keep a v1 copy. This may not work since the statement is so large. Either way, OR Staff should navigate to the statement and click the "Upgrade To V2 (skip PDF snapshot)" button to upgrade the statement without a v1 PDF copy.
PM Statements
Unable to render HTML. ABCChrome page load timed out.
This issue occurs on large PM statements when rendering the statement to PDF takes too long and our service gives up on waiting.
Solution: The user may attempt to download the PDF copy of the statement first if they wish to keep a v1 copy. This may not work since the statement is so large. Either way, OR Staff should navigate to the statement and click the "Upgrade To V2 (skip PDF snapshot)" button to upgrade the statement without a v1 PDF copy.