@VIGNESHWARAN M The object guid as source anchor for migration scenarios are not considered very reliable as that might change with the migration resulting in other problem with syncing. Changing it to ms-DS-Consistency to make sure it remains immutable through out would be a good path to follow.
One important point to mention here is :
For any given on-premises AD User object whose ms-DS-ConsistencyGuid attribute isn't populated, Azure AD Connect writes its objectGUID value back to the ms-DS-ConsistencyGuid attribute in on-premises Active Directory. After the ms-DS-ConsistencyGuid attribute is populated, Azure AD Connect then exports the object to Azure AD
=============================================================================
If the suggested response helped you resolve your issue, please do not forget to accept the response as Answer and "Up-Vote" for the answer that helped you for benefit of the community.