Duplicate Views After Solution Import

Hello guys,

Recently the company that I worked for encountered a problem when deploying a new solution version. Some entities has two views of the same name. After a bit of investigation, turned out that the view has different guid between the old solution version and the new solution version. Now the goal is to match the guid so there won't be any duplicates upon importing.

These are what I've tried so far:

1. [On new version solution] Create new unmanaged solution > add the problem views > edit the guid from xml > Import back the edited solution > found out that there are now sets of 2 of the problem views.
2. [On old version solution] Create new unmanaged solution > add the problem views > import to new solution > found out that there are now sets of 2 of the problem views, but the newly imported are not included in the metadata.
3. [On old version solution] Create new unmanaged solution > add the whole entities that have the problem views > delete the entities in the new solution > delete prevented by dependencies checker.

Is there any ways to make the new version guid to match the old version guid? Any supported or unsupported suggestion are welcome.

Thank you.