Problems after migrating a resource from Notes to M365 when rescheduling an appointment

We experienced a similar issue after migrating our room resource from HCL Notes to M365. The duplication of appointments in the room calendar, showing both old and rescheduled times, usually results from how Notes handles legacy appointments during coexistence. Even though the appointment appears moved, Notes metadata can remain and cause conflicts. A practical fix is to recreate recurring meetings directly in M365 and remove any remaining legacy entries. Also, ensure that all users have fully transitioned to M365 to avoid sync issues. This problem often occurs in partial coexistence environments. For a better understanding of how online scheduling systems work and manage appointments effectively, you can look here for a streamlined example.

We experienced a similar issue after migrating our room resource from HCL Notes to M365. The duplication of appointments in the room calendar, showing both old and rescheduled times, usually results from how Notes handles legacy appointments during coexistence. Even though the appointment appears moved, Notes metadata can remain and cause conflicts. A practical fix is to recreate recurring meetings directly in M365 and remove any remaining legacy entries. Also, ensure that all users have fully transitioned to M365 to avoid sync issues. This problem often occurs in partial coexistence environments. For a better understanding of how online scheduling systems work and manage appointments effectively, you can look here for a streamlined example.