Protractor E2E Test Cases migration from Angular 2+ application to React

If your tests were written correctly - then you'll have to replace your infrastructure layer with another module that would support React. You can estimate that task depending on the size and complexity of your existing module.

By "correctly" I mean the architectural separation between test definition layer and test adaptation/infrastructure (Protractor) layer.

Another point that you need to consider - is rewriting the angular specific locators (finding elements by ng-something), to more generic, that would suit the React UI as well.

In other words, as long as your test code/page objects do not contain plain calls to Protractor, and you are accessing it via your custom wrapper - you would only have to replace the content of the wrapper, without affecting the client code.